No more typing reviews! Try our Samantha, our new voice AI agent.

AWS Lake Formation vs Amazon EMR comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 18, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Amazon EMR
Ranking in Cloud Data Warehouse
13th
Average Rating
7.8
Reviews Sentiment
7.0
Number of Reviews
25
Ranking in other categories
Hadoop (3rd)
AWS Lake Formation
Ranking in Cloud Data Warehouse
8th
Average Rating
8.0
Reviews Sentiment
5.7
Number of Reviews
21
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of June 2026, in the Cloud Data Warehouse category, the mindshare of Amazon EMR is 3.8%, up from 3.3% compared to the previous year. The mindshare of AWS Lake Formation is 3.8%, down from 5.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Cloud Data Warehouse Mindshare Distribution
ProductMindshare (%)
AWS Lake Formation3.8%
Amazon EMR3.8%
Other92.4%
Cloud Data Warehouse
 

Featured Reviews

reviewer1343079 - PeerSpot reviewer
Senior Chief Engineer (Enterprise System Presales/Postsales) at a tech vendor with 10,001+ employees
Has simplified ETL workflows with on-demand processing but needs improved cost efficiency and visibility
I have used AWS Glue with S3 for making tables and databases, but regarding Amazon EMR, I do not remember much as we are currently using it very minimally. This is my observation: In EKS, we have had to deploy by ourselves because EKS does not provide the Hadoop framework, Spark, Hive, and everything, but we have completed all the deployment ourselves. Whereas Amazon EMR provides all these things. The cost factor differs significantly. When you run Spark application on EKS, you run at the pod level, so you can control the compute cost. But in Amazon EMR, when you have to run one application, you have to launch the entire EC2. In Qubole, the interface was very good. I could see many details because in Amazon EMR console, very few details are available. In Qubole, at one link, you can get all the details of what is happening, how the processes are running, and the cost decreased by using Qubole. I found Qubole more user-friendly and cost-effective. From the security point of view, we had to open some access rights to Qubole, which might be a drawback in comparison to Amazon EMR which is native to AWS.
Ciro Baldim Guerra - PeerSpot reviewer
Sr Analytics Engineer at Itau Unibanco S.A.
Has improved data governance by enabling clear ownership and structured access across teams
In my company, Itaú, we don't utilize all AWS offerings due to rigorous security measures. We operate approximately six to eight months behind other available services. I'm uncertain if gaps exist because of this limitation, though the system functions effectively for us. AWS Lake Formation offers column-level access control for databases, but we haven't implemented this feature either because it hasn't been approved by our compliance, governance, or security areas. In our current setup, everyone from my business unit uses the same consumer account. When access is requested for a table, everyone using that business unit account receives access. This could present a security concern, though it benefits new team members who automatically receive all necessary access permissions. However, I struggle to identify specific improvements needed in AWS Lake Formation.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"Amazon makes it about as easy as it can be to dip a toe in those waters."
"The ability to resize the cluster is what really makes it stand out over other Hadoop and big data solutions."
"This tool is simple to use and it's really accessible to many dev teams."
"Amazon EMR is a good solution that can be used to manage big data."
"It has a variety of options and support systems."
"It allows users to access the data through a web interface."
"It's helped to automate processes."
"One of the valuable features about this solution is that it's managed services, so it's pretty stable, and scalable as much as you wish. It has all the necessary distributions. With some additional work, it's also possible to change to a Spark version with the latest version of EMR. It also has Hudi, so we are leveraging Apache Hudi on EMR for change data capture, so then it comes out-of-the-box in EMR."
"It is seamlessly integrated within the AWS ecosystem, making it straightforward to manage access patterns for AWS-native services."
"The solution has many features that are applicable to events such as audits."
"The most valuable features of AWS Lake Formation were the access model itself, as it allows implementation of filters, Blueprints, and row-level and column-level security to mask data that shouldn't be accessed by certain entities, enabling granular control without exposing PII data."
"We have observed measurable benefits in terms of cost savings, time savings, resource savings, and efficiency improvements in our workflows."
"Every solution has its pros and cons, however, for our purposes, this solution works quite well for us."
"AWS Lake Formation significantly improves the structure of the data mesh, making it superior to previous structures we used."
"The main benefits that I have seen from using AWS Lake Formation are related to FinOps because you have control of your data and can track your costs since AWS Lake Formation is integrated into a unique platform, which is AWS Cloud Service."
"A favorite feature of AWS Lake Formation is that it provides us with visibility into who has access to a particular table or database in Glue."
 

Cons

"The product's features for storing data in static clusters could be better."
"The legacy versions of the solution are not supported in the new versions."
"We don't have much control. If we have multiple users, if they want to scale up, the cost will go and increase and we don't know how we can restrict that price part."
"In Qubole, the interface was very good. I could see many details because in Amazon EMR console, very few details are available."
"Amazon EMR can improve by adding some features, such as megastore services and HiveServer2. Additionally, the user interface could be better, similar to what Apache service provides, cross-platform services."
"Amazon EMR is continuously improving, but maybe something like CI/CD out-of-the-box or integration with Prometheus Grafana."
"The web interface for managing all your cloud services is a bit patchy and needs improvement."
"I feel some lack of functionality in Amazon EMR."
"The solution could make improvements around orchestration and doing some automation stuff on AWS front automation. It would be useful if we could use automation to build images and use hardened images which are CIS compliant."
"Rather than creating an additional hundred tools, optimizing a tool to have a centralized location to do governance would be beneficial."
"I think AWS Lake Formation could improve by enforcing the least privilege by design, moving from ad hoc grants to role-based access controls."
"AWS Lake Formation's pricing could be cheaper."
"In our experience what could be improved are not the support, performance or monitoring, but at a managerial level, the very expensive professional services of AWS. This could be an area of improvement for them. It's too expensive to acquire their support."
"If I could improve AWS Lake Formation, I would add more integrations with SageMaker."
"You need to have data experience to use the product."
"Lake Formation could enhance its capabilities in audit logs, real-time monitoring, and advanced data governance."
 

Pricing and Cost Advice

"Amazon EMR's price is reasonable."
"The cost of Amazon EMR is very high."
"The product is not cheap, but it is not expensive."
"There is no need to pay extra for third-party software."
"The price of the solution is expensive."
"There is a small fee for the EMR system, but major cost components are the underlying infrastructure resources which we actually use."
"You don't need to pay for licensing on a yearly or monthly basis, you only pay for what you use, in terms of underlying instances."
"Amazon EMR is not very expensive."
"AWS Lake Formation is a bit expensive."
report
Use our free recommendation engine to learn which Cloud Data Warehouse solutions are best for your needs.
900,747 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
19%
Manufacturing Company
10%
Construction Company
9%
Healthcare Company
8%
Financial Services Firm
21%
Manufacturing Company
7%
Retailer
6%
Construction Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business6
Midsize Enterprise5
Large Enterprise12
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise2
Large Enterprise15
 

Questions from the Community

What is your experience regarding pricing and costs for Amazon EMR?
I would rate the price for Amazon EMR, where one is high and ten is low, as a good one.
What needs improvement with Amazon EMR?
I feel some lack of functionality in Amazon EMR. I have thoughts on what would be great to see in the product, such as AI/ML features or additional options.
What advice do you have for others considering Amazon EMR?
I find it easy to integrate Amazon EMR with other AWS services like S3 or EC2 for data processing needs. I would rate this review as eight out of ten.
What is your experience regarding pricing and costs for AWS Lake Formation?
I don't understand much about the pricing of AWS Lake Formation, but I know how to search for the cost of Glue jobs, and I use the calculator in Amazon. I use a tool to preview the cost based on th...
What needs improvement with AWS Lake Formation?
Regarding areas of AWS Lake Formation that could be improved or enhanced, I prefer not to answer, mainly because I do not believe that I would be the most valuable person to ask, as I have not used...
What is your primary use case for AWS Lake Formation?
My usual use cases for AWS Lake Formation involved securing and governing the data resources that we configured in AWS, but we did not use the analytics or machine learning capabilities specificall...
 

Also Known As

Amazon Elastic MapReduce
No data available
 

Overview

 

Sample Customers

Yelp
bp, Cerner, Expedia, Finra, HESS, intuit, Kellog's, Philips, TIME, workday
Find out what your peers are saying about AWS Lake Formation vs. Amazon EMR and other solutions. Updated: June 2026.
900,747 professionals have used our research since 2012.