Still offered as the performance-optimized Amazon EMR runtime for Apache Spark. AWS pages describe it as 100% API compatible with open source Spark and available on EMR on EC2, EMR on EKS and EMR Serverless.
Read
10 Nov 2026
What it does well
AWS describes the runtime as 100% API compatible with open source Spark, so Spark jobs need no code changes.
AWS publishes aws-samples/emr-spark-benchmark, a TPC-DS harness for a 3 TB Parquet dataset with steps for OSS Spark, EMR on EC2 and EMR Serverless.
Where it is limited
The runtime is proprietary to AWS and available only where EMR, EMR on EKS and EMR Serverless are, so jobs on other Spark hosts must migrate first.
AWS's up to 4.5x figure names no TPC-DS scale or cluster, and the benchmark repository gives commands and configs but no results.
Published speed results
Fact
Source type
Source, read
AWS says the performance-optimized runtime executes up to 4.5x faster than open-source equivalents while delivering 2.7x faster Iceberg write performance. The page does not state the TPC-DS scale or cluster for these figures.
EMR on EC2 price is added to the EC2 and EBS price. EMR on EKS is charged per vCPU-hour and GB-hour requested, from image download until pod end, rounded to the second, with a one-minute minimum, plus EKS and EC2 or Fargate cost. EMR Serverless is also available. Exact rates are region-specific and loaded by script on the page.
Runtime is described as 100% API compatible with open source Spark, so Spark jobs need no code changes, but jobs must run on EMR (a migration if currently on other Spark hosts).
The EMR docs list optimizations such as adaptive query execution, dynamic partition pruning, Bloom filter join and optimized join reorder. AQE-related features are on by default; some can be tuned with Spark properties.
AWS publishes aws-samples/emr-spark-benchmark with steps to run TPC-DS on OSS Spark (EC2 via Flintrock), EMR on EC2, EMR Serverless and a link to EMR on EKS. It uses a 3 TB TPC-DS Parquet dataset in a public S3 bucket, 3 iterations, and 104 queries with a pre-built spark-benchmark-assembly-3.3.0.jar. The repo gives commands and configs; it does not state results.
The repo README notes that on OSS Spark query q95 did not complete, so it was rerun alone and merged, and says this was not an issue on EMR. This shows the OSS baseline needed manual handling.
A companion repo aws-samples/emr-on-eks-benchmark has the EMR on EKS TPC-DS benchmark with 3 TB examples and notes scale factor and executor config must change for 100 GB or 1 TB.
The runtime is proprietary to AWS and is a tuned build of Apache Spark, not a native C++ replacement. The benchmark harness is open sample code on GitHub.
Jobs must run on EMR (EC2, EKS or Serverless); a team on other Spark hosts migrates first. AQE-related features are on by default, and some can be tuned with Spark properties.
AWS Big Data blog post with TPC-DS 3 TB per-version results (EMR runtime vs OSS Spark) and cost-for-same-work figures (searched: aws.amazon.com/blogs/big-data/amazon-emr-on-eks-widens-the-performance-g, aws.amazon.com/blogs/big-data/category/analytics/amazon-emr/ (category p, github.com/aws-samples/emr-spark-benchmark)
Published cost-for-the-same-work result for EMR runtime vs OSS Spark (searched: aws.amazon.com/emr/pricing, aws.amazon.com/emr/features/spark, github.com/aws-samples/emr-spark-benchmark)
Amazon EMR runtime for Apache Spark side by side with each other option