Full Data Engineer at a financial services firm with 10,001+ employees
Real User
Top 20
2025-08-29T11:50:23Z
Aug 29, 2025
I develop ETL when information is in the Serverless environment on the physical computer; you change the space and democratization, but I don't work with machine learning. My review rating for AWS Lake Formation is 10 out of 10.
We are customers of Amazon and use it as a product. At Apple, we utilize S3 for storage and Redshift for analysis, along with CloudWatch for monitoring, IAM, and security access management. The overall rating for this solution is 8 out of 10.
Based on the values that AWS Lake Formation has for us, I think it is fair enough. I would rate AWS Lake Formation nine out of ten based on everything we have discussed. I am the Data Engineering Manager at UOL Edtech. I will be able to manage my review, and it is acceptable for me to make my review public.
AWS Data Engineer at a healthcare company with 10,001+ employees
Real User
Top 20
2025-08-05T15:31:00Z
Aug 5, 2025
I have recent experience with AWS Lake Formation and have worked with its centralized repository. The integration experience with S3, Glue services, and IAM has been noteworthy. The overall rating for AWS Lake Formation is 4 out of 10.
VP- Cloud Data/ Solution Architect at a financial services firm with 10,001+ employees
Real User
Top 5
2023-10-09T14:32:27Z
Oct 9, 2023
While AWS Lake Formation may have certain drawbacks, especially when it comes to integration with external systems and cell-level entitlements, it can still be a valuable choice if your use case is entirely AWS-native. In such cases, it's recommended to leverage the native AWS services available for managing data access and governance. However, if you're operating in a multi-cloud environment with Azure in the mix, it might be more beneficial to explore alternative solutions that offer better integration and more extensive access control capabilities. Overall, I would rate it six out of ten.
My advice to users is that they first need to know what they want to achieve out of AWS Lake Formation. They need to have a clear-cut expectation from the solution, and they should involve a knowledgeable partner. Overall, I rate AWS Lake Formation an eight out of ten.
Technical Head & Director - Data , AI & Robotics at a financial services firm with 10,001+ employees
Real User
2020-12-30T06:26:15Z
Dec 30, 2020
We're strictly customers of AWS. We're end-users. I'm not sure which version of the solution we're using. My advice to other organizations would be to not think of this solution as a one-time activity. It's an ongoing thing. It's a big change and there will new services and therefore it's constantly changing. You have to make sure that it's part and parcel of your everyday operations. The solution is pretty stable, or stable in the long run. However, every single day there is a need to grow the infrastructure, or there are new services being added externally and internally. You deploy more applications. You deploy more code. You deploy new libraries. You'll have to stay on top of everything to make sure it stays aligned with changes. Overall, I would rate the solution at a seven out of ten.
Head of Business Intelligence, Analytics and Big Data Service Line at NTT DATA
Real User
2020-11-02T17:15:00Z
Nov 2, 2020
On a scale of one to ten, I would give AWS Lake Formation a nine. In our experience, this AWS solution is one of the main players now on the market in this field. Additionally, because they can connect the offer in terms of infrastructure and software, sometimes you can combine the price and discount of infrastructure and software. This could be an advantage for clients.
Vice President Application Security North America at BNP Paribas
Real User
Top 20
2020-09-23T06:10:02Z
Sep 23, 2020
Our company does not have a business relationship with AWS. We're just a customer. I'm not sure which version of the solution we're using. The thing is that we are not forcing the end-user or the project team to deploy the application. They have the liberty to choose their own platform. Either they can go with AWS or they can go with Azure. Most of the projects which are deployed on non-Windows OS tend to go for AWS. My area of expertise is more in the auditing of the security standards and maintaining the security requirements as per the industry standard. I'm more in a security architect kind of role. Every solution has its pros and cons, however, for our purposes, this solution works quite well for us. I'd rate it overall at eight out of ten.
AWS Lake Formation is a service that makes it easy to set up a secure data lake in days. A data lake is a centralized, curated, and secured repository that stores all your data, both in its original form and prepared for analysis.
I develop ETL when information is in the Serverless environment on the physical computer; you change the space and democratization, but I don't work with machine learning. My review rating for AWS Lake Formation is 10 out of 10.
We are customers of Amazon and use it as a product. At Apple, we utilize S3 for storage and Redshift for analysis, along with CloudWatch for monitoring, IAM, and security access management. The overall rating for this solution is 8 out of 10.
Based on the values that AWS Lake Formation has for us, I think it is fair enough. I would rate AWS Lake Formation nine out of ten based on everything we have discussed. I am the Data Engineering Manager at UOL Edtech. I will be able to manage my review, and it is acceptable for me to make my review public.
I have recent experience with AWS Lake Formation and have worked with its centralized repository. The integration experience with S3, Glue services, and IAM has been noteworthy. The overall rating for AWS Lake Formation is 4 out of 10.
I would not recommend AWS Lake Formation to others as it gives me an advantage. I'd rate the solution seven out of ten.
I would recommend the solution to other users. Overall, I rate the solution a nine out of ten.
While AWS Lake Formation may have certain drawbacks, especially when it comes to integration with external systems and cell-level entitlements, it can still be a valuable choice if your use case is entirely AWS-native. In such cases, it's recommended to leverage the native AWS services available for managing data access and governance. However, if you're operating in a multi-cloud environment with Azure in the mix, it might be more beneficial to explore alternative solutions that offer better integration and more extensive access control capabilities. Overall, I would rate it six out of ten.
My advice to users is that they first need to know what they want to achieve out of AWS Lake Formation. They need to have a clear-cut expectation from the solution, and they should involve a knowledgeable partner. Overall, I rate AWS Lake Formation an eight out of ten.
We're strictly customers of AWS. We're end-users. I'm not sure which version of the solution we're using. My advice to other organizations would be to not think of this solution as a one-time activity. It's an ongoing thing. It's a big change and there will new services and therefore it's constantly changing. You have to make sure that it's part and parcel of your everyday operations. The solution is pretty stable, or stable in the long run. However, every single day there is a need to grow the infrastructure, or there are new services being added externally and internally. You deploy more applications. You deploy more code. You deploy new libraries. You'll have to stay on top of everything to make sure it stays aligned with changes. Overall, I would rate the solution at a seven out of ten.
On a scale of one to ten, I would give AWS Lake Formation a nine. In our experience, this AWS solution is one of the main players now on the market in this field. Additionally, because they can connect the offer in terms of infrastructure and software, sometimes you can combine the price and discount of infrastructure and software. This could be an advantage for clients.
Our company does not have a business relationship with AWS. We're just a customer. I'm not sure which version of the solution we're using. The thing is that we are not forcing the end-user or the project team to deploy the application. They have the liberty to choose their own platform. Either they can go with AWS or they can go with Azure. Most of the projects which are deployed on non-Windows OS tend to go for AWS. My area of expertise is more in the auditing of the security standards and maintaining the security requirements as per the industry standard. I'm more in a security architect kind of role. Every solution has its pros and cons, however, for our purposes, this solution works quite well for us. I'd rate it overall at eight out of ten.