All Products
Search

This Product

    E-MapReduce:Add services

    Document Center

    E-MapReduce:Add services

    Last Updated:Mar 26, 2026

    When your workload requirements change, you can extend a running E-MapReduce (EMR) cluster by adding services without rebuilding it. This topic describes how to add services to an existing cluster in the EMR console.

    Prerequisites

    Before you begin, ensure that:

    • The cluster is in the Running state. To create a cluster, see Create a cluster.

    • All nodes in the cluster are in the Running state and the services already deployed work as expected.

    Limitations

    • You can add services only in the scenarios described in the following table. The services that you can add to an existing cluster vary based on the version of EMR. The actual list of available services is displayed in the EMR console.

    • If you turned on Kerberos Authentication when creating the cluster, Knox and Kudu cannot be added after the cluster is created.

    Cluster type Services you can add
    DataLake clusters (EMR V3.43.0, EMR V5.9.0, and their later minor versions) Knox (depending on OpenLDAP), OpenLDAP, Ranger (depending on Ranger-plugin and Hadoop-Common), Iceberg, Hudi, JindoData (a minor version earlier than EMR V5.15.X or EMR V3.49.X), JindoCache (EMR V5.15.X or a later minor version or EMR V3.49.X or a later minor version), Presto/Trino (depending on Hadoop-Common), DLF-Auth, Tez (depending on YARN), Flume (depending on Hadoop-Common), RSS/Celeborn, Sqoop (depending on YARN), Kyuubi (depending on Spark 3 and ZooKeeper), Paimon, ZooKeeper
    Dataflow clusters (EMR V3.43.0, EMR V5.9.0, and their later minor versions) Flink (depending on YARN and OpenLDAP), OpenLDAP, Knox (depending on OpenLDAP), Paimon, ZooKeeper
    DataServing clusters (EMR V3.43.0, EMR V5.9.0, and their later minor versions) HBase (depending on ZooKeeper and HDFS or OSS-HDFS), Phoenix (depending on HBase), JindoData (a minor version earlier than EMR V5.15.X or EMR V3.49.X), JindoCache (EMR V5.15.X or a later minor version or EMR V3.49.X or a later minor version)
    OLAP (EMR V3.43.0, EMR V5.9.0 and their later minor versions) None
    Custom (EMR V3.43.0, EMR V5.9.0 and their later minor versions) Knox (depending on OpenLDAP), OpenLDAP, Ranger (depending on Ranger-plugin and Hadoop-Common), Iceberg, Hudi, JindoData (a minor version earlier than EMR V5.15.X or EMR V3.49.X), JindoCache (EMR V5.15.X or a later minor version or EMR V3.49.X or a later minor version), Presto (depending on Hadoop-Common), DLF-Auth, Tez (depending on YARN), Flume (depending on Hadoop-Common), RSS/Celeborn, Flink (depending on YARN and OpenLDAP), HBase (depending on ZooKeeper and HDFS or OSS-HDFS), Phoenix (depending on HBase)
    Hadoop (available only for existing users) Impala, Presto, Oozie, ZooKeeper, HBase, Zeppelin, Storm, Ranger, Superset, Livy, Flume, Kudu, ESS or RSS

    Usage notes

    • After adding services, some existing services may require configuration changes and a restart before the new services work correctly. Schedule this operation during off-peak hours to minimize disruption to running jobs.

    Add services to a cluster

    1. Go to the Services tab.

      1. Log on to the EMR console. In the left-side navigation pane, click EMR on ECS.

      2. In the top navigation bar, select the region where your cluster resides and select a resource group.

      3. On the EMR on ECS page, find the target cluster and click Services in the Actions column.

    2. On the Services tab, click Add Service.

    3. In the Add Service panel, select the services to add and click OK. When the operation completes, the The service is added message appears. The added services are now visible on the Services tab.

      Some services require configuration changes to existing services before they work correctly. If so, the console prompts you after the service is added. Click Continue and follow the on-screen instructions to complete the configuration.

    4. (Optional) Modify configurations of existing services. Some newly added services depend on configuration changes in existing services. For example, after adding Trino, you must update the configurations of Hive, Spark 3, Tez, Trino, and YARN. Services that require configuration changes are marked with an orange dot in the upper-right corner of their card on the Services tab.

      1. On the Services tab, click Configure for a service with an orange dot. configure

      2. Click Modify Configurations in the prompt message. Modify Configuration

      3. In the Modify Configurations panel, select all configuration items and click Save. The Save and Deliver Configuration switch is on by default. Save

      4. Restart the service for the configuration to take effect. You can also click the prompt that appears after saving to trigger the restart. image.png For information about how to restart a service, see Restart a service.

    Verify the result

    After the operation completes, verify that the newly added services are running correctly:

    1. On the Services tab, confirm that the added services appear in the list.

    2. Check that each new service shows no orange dot, indicating no pending configuration changes.

    3. For a broader health check, see View the health status of services and components.

    What's next