Try our new research platform with insights from 80,000+ expert users

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 March 2026, in the Cloud Data Warehouse category, the mindshare of Amazon EMR is 3.8%, up from 3.1% compared to the previous year. The mindshare of AWS Lake Formation is 4.7%, down from 5.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Cloud Data Warehouse Mindshare Distribution
ProductMindshare (%)
AWS Lake Formation4.7%
Amazon EMR3.8%
Other91.5%
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

"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."
"We are using Amazon EMR to clean the data and transform the data in such a way that the end-user can get the insights faster."
"Less expensive than in-house hosting, much more scalable when needed to process larger volumes of data."
"Amazon EMR has multiple connectors that can connect to various data sources."
"The solution is pretty simple to set up."
"It allows users to access the data through a web interface."
"Amazon EMR is a good solution that can be used to manage big data."
"It's helped to automate processes."
"We use this to reduce latency from minutes to seconds, as we aim for real-time visibility into patient healthcare monitoring."
"The solution is quite good at handling analytics. It's done a good job at helping us centralize them."
"We use AWS Lake Formation typically for the data warehouse."
"The integration of AWS Lake Formation with the IAM for authentication and authorization is very good; I didn't have any problems in the setup and thought it was simple."
"There is no doubt that this place exceeded my expectations with its incredible ambiance, attentive service, and mouthwatering menu."
"AWS Lake Formation lets you see all your data and tables on one screen."
"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."
"AWS Lake Formation significantly improves the structure of the data mesh, making it superior to previous structures we used."
 

Cons

"The dashboard management could be better. Right now, it's lacking a bit."
"The web interface for managing all your cloud services is a bit patchy and needs improvement."
"One of the lacking features is good web support."
"Amazon EMR is continuously improving, but maybe something like CI/CD out-of-the-box or integration with Prometheus Grafana."
"The most complicated thing is configuring to the cluster and ensure it's running correctly."
"There is no need to pay extra for third-party software."
"There is room for improvement in pricing."
"The legacy versions of the solution are not supported in the new versions."
"Lake Formation could enhance its capabilities in audit logs, real-time monitoring, and advanced data governance."
"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."
"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."
"It falls short when it comes to more granular access control, such as cell-level or row-level entitlements which is a significant drawback for organizations that require precise control over who can access specific rows of data."
"The initial onboarding process is challenging because creating a plan takes a month to a month and a half to build out."
"The main challenge we faced with AWS Lake Formation was related to cross-account sharing. Granting access to other AWS accounts for tables or databases in a different AWS account was somewhat difficult."
"Athena can be a bit clunky when writing queries, indicating a potential enhancement point for easier user interaction with query tools such as DataGrip using provided driver JARs."
"For the end-users, it's not as user-friendly as it could be."
 

Pricing and Cost Advice

"The price of the solution is expensive."
"Amazon EMR's price is reasonable."
"Amazon EMR is not very expensive."
"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."
"There is no need to pay extra for third-party software."
"There is a small fee for the EMR system, but major cost components are the underlying infrastructure resources which we actually use."
"The cost of Amazon EMR is very high."
"The product is not cheap, but it is not 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.
884,933 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
20%
Healthcare Company
10%
Manufacturing Company
7%
Computer Software Company
7%
Financial Services Firm
23%
Manufacturing Company
8%
Retailer
7%
Computer Software 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: March 2026.
884,933 professionals have used our research since 2012.