Amazon Elastic MapReduce Pricing

With Amazon EMR you only pay for what you use. Amazon EMR pricing is in addition to pricing for EC2 and S3. We charge less where our costs are less, and your cost will depend on the number and type of Amazon EC2 Instances in your job flow and the amount of time it is running.

You are charged per-second from the time your cluster starts until it is terminated, with a one-minute minimum.

Amazon S3 is billed separately. (Many customers store their input and output data in S3; others store all of the data locally on HDFS.) The more data you store, the lower the monthly price per GB.

With Amazon EMR you only pay for what you use. Amazon EMR pricing is in addition to pricing for EC2 and S3. We charge less where our costs are less, and your cost will depend on the number and type of Amazon EC2 Instances in your job flow and the amount of time it is running.

You are charged per-second from the time your cluster starts until it is terminated, with a one-minute minimum.

Amazon S3 is billed separately. (Many customers store their input and output data in S3; others store all of the data locally on HDFS.) The more data you store, the lower the monthly price per GB.

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 Amazon Web Services using either EC2 or Amazon Fargate. If you are using Amazon EC2 (including with EKS managed node groups), you pay for Amazon Web Services resources (e.g., EC2 instances or Amazon EBS volumes) you create to run your Kubernetes worker nodes. See detailed pricing information on the Amazon EC2 pricing page. If you are using Amazon 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 Amazon 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 China (Beijing) Region 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.0902975 * 0.5) = (number of vCPU * per vCPU-hours rate * job runtime in hour) = ¥4.51
• Total Uplift on memory = (300 * ¥0.00995675 * 0.5) = (amount of memory used * per GB-hours rate * job runtime in hour) = ¥1.49
• Total EMR Uplift for the EMR job = ¥6.01

Additional Costs

You pay ¥0.688 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 Amazon Web Services using either Amazon EC2 or Amazon Fargate.

If you are using EC2 (including with EKS managed node groups), you pay for Amazon Web Services 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 Amazon 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 Amazon Fargate pricing page. 

This pricing is for EMR Serverless. 

With EMR Serverless, there are no upfront costs, and you pay for only the resources you use. You pay for the amount of vCPU, memory, and storage resources consumed by your applications.

With EMR Serverless, you create an application using an open-source framework version and then submit jobs to the application. As part of the job specification, you can provide the minimum and maximum number of concurrent workers, as well as the vCPU, memory, and storage for each worker. EMR automatically adds and removes workers based on what the job requires within your specified limits. The three dimensions of compute, memory, and storage for workers can be independently configured. You can choose from 1 vCPU, 2 vCPU, 4 vCPU, 8 vCPU, to 16 vCPU per worker, memory from 2 GB to 120 GB per worker in 1 GB to 8 GB increments, and storage from 20 GB to 200 GB.

You are charged for aggregate vCPU, memory, and storage resources used from the time workers are ready to run your workload until the time they stop, rounded up to the nearest second with a 1-minute minimum. If you set up your application to start workers at application startup, the requested workers will start when you start your application and end when you stop the application, or when the application remains idle.

Pricing details (compute and memory)

Pricing is based on vCPU, memory, and storage resources used by workers, aggregated across all workers.

Pricing details (ephemeral storage)

20 GB of ephemeral storage is available for all workers by default—you pay only for any additional storage that you configure per worker.

Supported worker configurations

Duration

Duration is calculated from the time a worker is ready to run your workload until the time it stops, rounded up to the nearest second with a 1-minute minimum.

Additional charges

You may incur additional charges if your applications use other services of Amazon Web Services. For example, if your application uses Amazon Simple Storage Service (S3) to store and process data, then you will be charged standard Amazon S3 rates. If you move data from sources such as Amazon S3, Amazon Relational Database Service (RDS), or Amazon Redshift, you are charged standard request and data transfer rates. If you use Amazon CloudWatch, you are charged standard rates for CloudWatch logs and CloudWatch events.

Pricing Examples

Suppose you submit a Spark job to EMR Serverless. Let’s assume that the job is configured to use a minimum of 25 workers and a maximum of 75 workers, each configured with 4VCPU and 30GB of memory. Consider that no additional ephemeral storage was configured. If your job runs for 30 minutes using 25 workers (or 100 vCPU) and was automatically scaled to add 50 more workers (200 more vCPU) for 15 minutes:

Total vCPU-hours cost = (100 * ¥ 0.0902975 * 0.5) + (200 * ¥ 0.0902975 * 0.25) = (number of vCPU * per vCPU-hours rate * job runtime in hour) = ¥ 9.02975

Total GB-hours = (750 * ¥ 0.00995675 * 0.5) + (1500 * ¥ 0.00995675 * 0.25) = (Total GB of memory configured * per GB-hours rate * job runtime in hour) = ¥ 7.4675625

Total EMR Serverless Charges = ¥ 9.02975 + ¥ 7.4675625 = ¥ 16.4973125

Additional Charges: If your application uses other services of Amazon Web Services such as Amazon S3, you are charged standard S3 rates.