Cloud Renames Contribute
RenamedData & BIAWS

Amazon Elastic MapReduce Amazon EMR

Managed big data cluster and serverless platform for running Apache Spark, Apache Hadoop, Apache HBase, Trino, Presto, and Apache Flink on AWS.

Naming timeline

  1. Amazon Elastic MapReduce

    · Initial Launch

    Launched in April 2009 to run managed Apache Hadoop MapReduce clusters on Amazon EC2 and Amazon S3.

  2. Amazon EMRCurrent name

    · Product Rebrand

    Officially shortened to Amazon EMR with the EMR 5.0 release cycle to reflect multi-framework support beyond MapReduce while retaining elasticmapreduce:* IAM actions.

What is Amazon Elastic MapReduce called now?

Amazon Elastic MapReduce is now called Amazon EMR, with the latest change in August 2016 (Product Rebrand). Managed big data cluster and serverless platform for running Apache Spark, Apache Hadoop, Apache HBase, Trino, Presto, and Apache Flink on AWS. Only the customer-facing name changed; the underlying technical identifiers remain backward compatible.

Also known as

  • EMR
  • Elastic MapReduce

Technical identifiers

Technical identifiers unchanged. Only the customer-facing product name changed; the APIs, CLI commands, IAM roles and Terraform resources below keep their legacy identifiers for backward compatibility.

AWS Service APIs / SDKselasticmapreduce emr-serverless emr-containers
AWS CLI Commandsaws emr aws emr-serverless aws emr-containers
IAM Actions & Policieselasticmapreduce:* emr-serverless:* emr-containers:*
Terraform Resources (aws_*)aws_emr_cluster aws_emr_instance_group aws_emrserverless_application

Core cluster APIs and IAM action prefixes retain the legacy elasticmapreduce namespace (elasticmapreduce:*), while CLI commands use aws emr and Terraform resources use aws_emr_*.

Notes & disambiguation

  • Originally launched in April 2009 as Amazon Elastic MapReduce when Hadoop MapReduce was its primary engine, AWS officially shortened the service name to the acronym Amazon EMR in 2016 as Apache Spark, Presto, and HBase became primary workloads.
  • Underlying IAM actions and service endpoints for EC2 cluster management retain the original elasticmapreduce:* namespace (such as elasticmapreduce:RunJobFlow and elasticmapreduce:DescribeCluster).
  • AWS CLI uses aws emr (alongside aws emr-containers for EMR on EKS and aws emr-serverless for EMR Serverless), and Terraform uses aws_emr_cluster.

Sources & official documentation

Catalog last updated . Spotted an error? Suggest an edit