Amazon EMR pricing

This pricing is for Amazon EMR applications running on Amazon EMR clusters with Amazon EC2 instances.

The Amazon EMR price is in addition to the Amazon EC2 price (the price for the underlying servers) and Amazon EBS price (if attaching Amazon EBS volumes). These are also billed per-second, with a one-minute minimum. There are a variety of Amazon EC2 pricing options you can choose from, including On-Demand (shown below), 1 year & 3 year Reserved Instances, Capacity Savings Plans, and Spot instances. Spot Instances are spare Amazon EC2 capacity available at up to a 90% discount compared to On-Demand prices. See Spot Instance price savings vs On-Demand by filtering for “Instance types supported by EMR” on the Spot Instance Advisor page.

You can estimate your bill using the AWS Pricing Calculator.

This pricing is for Amazon EMR on Amazon EKS clusters.

The Amazon EMR price is in addition to the Amazon EKS pricing or any other services used with Amazon EKS. You can run EKS on AWS using either EC2 or AWS Fargate. If you are using Amazon EC2 (including with EKS managed node groups), you pay for AWS resources (e.g. EC2 instances or EBS volumes) you create to run your Kubernetes worker nodes. See detailed pricing information on the Amazon EC2 pricing page. If you are using AWS Fargate, pricing is calculated based on the vCPU and memory resources used from the time you start to download your container image until the Amazon EKS pod terminates, rounded up to the nearest second. A minimum charge of 1 minute applies. See detailed pricing information on the AWS Fargate pricing page.

Amazon EMR pricing on EKS is calculated based on the vCPU and memory resources used from the time you start to download your EMR application image until the Amazon EKS Pod terminates, rounded up to the nearest second. Pricing is based on requested vCPU and memory resources for the Task or Pod.

Pricing Example

Pricing based on US-East-1 pricing.

Suppose you are running an EMR-Spark application deployed on Amazon EKS. In this case, EKS gets its compute capacity using r5.2xlarge EC2 instances (8 vCPU, 64 GB RAM). Let’s assume that the EKS cluster has 100 nodes, totaling 800 vCPU, and 6400GB of total memory. Let’s assume that that application utilizes 100 VCPUs and 300GB of memory for 30 minutes.

Total EMR uplift charges for the job:

• Total Uplift on vCPU = (100 * $0.01012 * 0.5) = (number of vCPU * per vCPU-hours rate * job runtime in hour) = $0.506
• Total Uplift on memory = ( 300 * $0.00111125 *0.5) = (amount of memory used * per GB-hours rate * job runtime in hour) = $0.1667
• Total EMR Uplift for the EMR job = $0.6727

Additional Costs

You pay $0.10 per hour for each Amazon EKS cluster that you create. You can use a single Amazon EKS cluster to run multiple applications by taking advantage of Kubernetes namespaces and IAM security policies. You can run EKS on AWS using either Amazon EC2 or AWS Fargate.

If you are using EC2 (including with EKS managed node groups), you pay for AWS resources (e.g. EC2 instances or EBS volumes) you create to run your Kubernetes worker nodes. You only pay for what you use, as you use it. There are no minimum fees and no upfront commitments. See detailed pricing information on the Amazon EC2 pricing page.

If you are using AWS Fargate, pricing is calculated based on the vCPU and memory resources used from the time you start to download your container image until the Amazon EKS pod terminates, rounded up to the nearest second. A minimum charge of 1 minute applies. See detailed pricing information on the AWS Fargate pricing page.

Amazon EMR on AWS Outposts pricing is simple and the EMR pricing is the same as in the cloud. Please refer to AWS Outposts pricing page for details on AWS Outposts pricing.