What's new with the console? - Amazon EMR
What console am I in?Opt-in to the new consoleSummary of differences
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

What's new with the console?

Amazon EMR has migrated to a new experience. The new console offers an updated interface that provides you with an intuitive way to manage your Amazon EMR environment and gives you convenient access to documentation, product information, and other resources. This page describes important differences between the old console experience and the new Amazon Web Services Management Console for Amazon EMR.

What console am I in?

To determine the Amazon EMR console that you currently use, view the URL for the console page in your browser:

Note

If you have opted in to the new Amazon EMR console experience, old console links (https://console.amazonaws.cn/elasticmapreduce/) will redirect you to the new console (https://console.amazonaws.cn/emr/). If you ever want to go back to the old console experience, select Switch to the old console from the banner at the top of the console screen. For more information , see Opt-in to the new console.

The Amazon EMR console functionality is migrating to the new experience in phases. The following table lists the main Amazon EMR console components and their console migration status.

Amazon EMR console component New console Old console

EMR Studio1

✔

✔

Create and manage clusters

✔

✔

Block public access

✔

✔

Monitor Amazon CloudWatch Events

✔

✔

Security configurations

 ✔ ✔

Virtual clusters (Amazon EMR on EKS)

✔

✔
View and manage your Amazon Virtual Private Cloud subnets2 ✔ ✔

Notebooks3

 ✔ ✔

1 EMR Studio uses the new interface experience in both the new and old consoles.

2 In the new console, you can view and manage your Amazon VPC subnets within the Networking section when you create a cluster. In the old console, use the link in the left-hand navigation bar to access the list of Amazon VPC subnets.

3 EMR Notebooks will be available as EMR Studio Workspaces in the new console by February 8, 2023. You’ll still be able to use your existing notebooks in the old console, but on March 10, 2023, we’ll turn off the Create notebook button. The Create Workspace button in the new console will replace this functionality. To access or create Workspaces, EMR Notebooks users will need additional IAM role permissions. For more information, see Amazon EMR Notebooks are Amazon EMR Studio Workspaces in new console and What's new in the console?

Opt-in to the new console

When you are ready to opt-in to the new Amazon EMR console experience, you can navigate directly to https://console.amazonaws.cn/emr/ or select Switch to the new console from the info banner in the old console. Once you have switched to the new console, all old console links will redirect to the new console automatically. If you want to opt-out of the new console and go back to using the old Amazon EMR console, select Switch to the old console from the info banner in the new console to opt-out of the new experience.

Note

The new Amazon EMR console will become the default console on or after March 27, 2023. If you've already opted in to the new console, you can continue to use it without interruption. If you're still using the old console, the new console will launch automatically on your first login after the changeover. If you want to, you can switch back to the old console to opt-out of the new console experience.

Summary of differences

This section outlines the differences between the old Amazon EMR console and the new Amazon EMR console experiences. The differences fall into the following categories:

Cluster compatibility between old and new console

In some cases, a cluster that you created in the old Amazon EMR console might not be compatible with the new console. The following list describes compatibility requirements for the new Amazon EMR console.

  • The new console supports clusters created in Amazon EMR releases 5.20.1 and later.

  • You can clone clusters that use automatic scaling in the new console, but you can only create new clusters if you want to manually scale them or use managed scaling.

To create and work with clusters that are not compatible with the new console, you can use the Amazon Command Line Interface (Amazon CLI), the Amazon SDK, or the old console.

Differences when you create clusters

The following table highlights the differences that you can expect when you create clusters with the new Amazon EMR console as opposed to the old Amazon EMR console.

Capability New console Old console

Terminology: Amazon EMR cluster node types

Primary, core, task

Master, core, task

Amazon EMR supported releases1

Amazon EMR release 5.20.1 and later

All Amazon EMR releases

Quickly launching a cluster

Use the Create cluster button under the Summary panel

Use the Create cluster - Quick Options page

Configuring a Spot provisioning timeout

Define a timeout period for provisioning instances for each fleet in your cluster.

You can't customize a provisioning timeout when you create a cluster.

Service roles and Amazon EC2 instance profile role

The new console does not create default roles; you must create roles with the IAM Console or select an already-created IAM role

 Supports default role creation with v1 and v2 policies, or you can select an already-created IAM role

Cluster visibility

 From within the Amazon EMR console, you can't make a cluster visible to all a users; your IAM policy determines cluster access

From within the Amazon EMR console, you can make a cluster visible to all a users if you use the deprecated v1 role-creation policies

Networking - configure private subnets

 You must configure Amazon S3 endpoints and NAT gateways from their respective Amazon S3 and Amazon VPC consoles

You can configure Amazon S3 endpoints and NAT gateways directly from the Create cluster workflow in the old console

EMR File System consistent view (EMRFS CV)

With the release of Amazon S3 strong read-after-write consistency on December 1, 2020, you don't need to use EMRFS CV with your EMR clusters

EMRFS CV is enabled, but you can turn off EMRFS CV and delete the Amazon DynamoDB database that it uses; see Consistent view for more information

Debugging

 You can debug jobs using the Application UI interface on the cluster details page

You can use a debugger tool (step 3 in advanced options) to debug jobs for clusters that run on Amazon EMR releases 4.1.0 through 5.27.0

1 You can't create or edit clusters using releases earlier than Amazon EMR 5.20.1 in the new console, but any existing clusters created using releases earlier than 5.20.1 will continue to work. To create and edit clusters with Amazon EMR releases earlier than 5.20.1, use the API or CLI, or switch back to the old console.

Differences when you list and search for clusters

The following table highlights the differences that you can expect when you view and search for clusters in the list view with the new Amazon EMR console as opposed to the old Amazon EMR console.

Note

For both the old and new consoles, when you apply a data filter to the cluster list, it queries the entire database. But when you enter a text string into the search box, the search only applies to the results that the list has loaded client side.

Capability New console Old console

Viewing cluster details

You can select the Cluster ID to view exhaustive cluster details like configuration options, persistent application UIs, and logs.

You can expand and collapse each cluster row to view information like configuration details and to access links for cluster monitoring and logs.

Searching for clusters

Use a single search field to enter text search queries and to create and apply data filters like "Status = Any active status".

Use a dropdown to refine the state of the clusters (Active, Terminated, Failed) and a separate field to enter a text search query.

Finding failed clusters

To search for failed clusters, apply the filter Status = Terminated with errors.

To search for failed clusters, apply the filter Failed clusters.

Differences when you view or edit cluster details

The following table highlights the differences that you can expect when you view or edit the details for an existing cluster with the new Amazon EMR console as opposed to the old Amazon EMR console.

Capability New console Old console

Viewing app UIs, logs, and configurations

(Apache Spark UI, Spark History service, Apache Tez UI, YARN timeline server)

View cluster configurations in the Configurations tab. Launch a live, persistent, application UI to see the logs for an application from the Applications tab.

View cluster configurations in the Configurations tab. Launch a live, persistent, application UI to see the logs for an application from the Applications user interfaces tab. As of January 23, 2023, high-level application history is no longer available.

Exporting a cluster to CLI

Option available from cluster detail and list view Actions menus as "View command for cloning cluster"

Option available from cluster list view Actions menus as "Amazon CLI Export"

Differences when you work with security configurations

The following table highlights the differences that you can expect when you configure security options with the new Amazon EMR console as opposed to the old Amazon EMR console.

Capability New console Old console

Cloning security configurations

✔

Federated governance using Trino and Apache Ranger

✔

Using a runtime role to submit work to a cluster1

✔

Authorizing access to EMR File System (EMRFS) data

Amazon S3 access points

Amazon Identity and Access Management (IAM) roles

Amazon Lake Formation access controls

Runtime roles

SAML federation

1 To pass a role during step submission, your cluster must use a security configuration with an IAM permissions policy attached so that the a user can pass only the approved roles and your jobs can access Amazon EMR resources. For more information, see Runtime roles for Amazon EMR steps.