Configure CloudWatch agent for Amazon EMR 7.0.0

1. Create or choose a bucket in your Amazon S3 account where you want to store the configuration files that specify the CloudWatch agent metrics.

2. Create the emr-amazon-cloudwatch-agent.json configuration file with your preferred metrics specified. To do this, use one of the methods explained in Create the CloudWatch agent configuration file. For more information about the structure of the CloudWatch agent configuration file, see Manually create or edit the CloudWatch agent configuration file in the Amazon CloudWatch User Guide.

3. Next, navigate to the aws-emr-utilities repo on GitHub and download the following system metrics scripts:

   • install_system_metrics_launcher.sh – A script that downloads and then runs install_system_metrics.sh in the background so that the node can finish bootstrapping.

   • install_system_metrics.sh – A script that waits for the instance it runs on to finish bootstrapping, then downloads and applies the configuration in the JSON file.

4. Open each SH file and replace my-s3-bucket with the name of your bucket from Step 1.

5. Upload the one JSON and two SH files to your S3 bucket.

6. Now, you can navigate to the Amazon EMR console and create a new cluster with the CloudWatch agent. Under EMR on EC2 in the left navigation, select Clusters and then Create cluster.

7. In the Name and applications section, choose an Amazon EMR release of 7.0.0 or higher.

8. Under Application bundle, select the bundle or apps that you want to install to your cluster, and include Amazon CloudWatch Agent with your selections.

9. In the Bootstrap actions section, select Add.

   • For the Name, insert install_system_metrics_launcher.sh.

   • For the Script location, insert s3://my-s3-bucket/install_system_metrics_launcher.sh. Replace my-s3-bucket with the path to your S3 bucket.

   • Leave the Arguments block empty.

10. Select Add bootstrap action.

11. Continue to create the cluster to serve your workload needs.

1. Create or choose a bucket in your Amazon S3 account where you want to store the configuration files that specify the CloudWatch agent metrics.

2. Next, navigate to the aws-emr-utilities repo on GitHub and download the following scripts:

   • install_app_metrics_launcher.sh – A script that downloads and then runs install_app_metrics.sh in the background so that the node can finish bootstrapping.

   • install_app_metrics.sh – A script that waits for the instance it runs on to finish bootstrapping, then downloads and applies the configuration in the YAML files that you'll download in an upcoming step.

3. Open each file and replace my-s3-bucket with the name of your bucket from Step 1.

4. Next, download the following YAML mapping files. For information about how these YAML files are structured, see javaagent in the OpenTelemetry Instrumentation for Java GitHub repo.

   • datanode-metrics.yaml – The configuration for Hadoop DataNode metrics.

   • namenode-metrics.yaml – The configuration for Hadoop NameNode metrics.

   • nodemanager-metrics.yaml – The configuration for Yarn NodeManager metrics.

   • resourcemanager-metrics.yaml – The configuration for Yarn ResourceManager metrics.

5. Upload the two SH and four YAML files to your S3 bucket.

6. Now, you can navigate to the Amazon EMR console and create a new cluster with the CloudWatch agent. Under EMR on EC2 in the left navigation, select Clusters and then Create cluster.

7. In the Name and applications section, choose an Amazon EMR release of 7.0.0 or higher.

8. Under Application bundle, select the bundle or custom group of apps that you want to install to your cluster, and include CloudWatch agent with your selections.

9. In the Bootstrap actions section, select Add.

   • For the Name, insert install_app_metrics_launcher.sh.

   • For the Script location, insert s3://my-s3-bucket/install_app_metrics_launcher.sh. Replace my-s3-bucket with the path to your S3 bucket.

   • Leave the Arguments block empty.

10. Select Add bootstrap action.

11. Continue to create the cluster to serve your workload needs.

Use the CloudWatch agent on an EMR cluster to publish metrics to Amazon Managed Service for Prometheus

Once the service policy has the correct permissions, use the following steps to launch a cluster that uses the CloudWatch agent to publish metrics to Amazon Managed Service for Prometheus.

1. Use the Amazon Web Services Management Console or Amazon CLI to create an Amazon Managed Service for Prometheus workspace. For more information, see Create a workspace in the Amazon Managed Service for Prometheus User Guide.

2. Create or choose a bucket in your Amazon S3 account where you want to store the launch files that specify Amazon Managed Service for Prometheus as cloud storage.

3. Next, navigate to the aws-emr-utilities repo on GitHub and download the following scripts:

   • add_prometheus_endpoint_launcher.sh – A script that downloads and then runs add_prometheus_endpoint.sh in the background so that the node can finish bootstrapping.

   • add_prometheus_endpoint.sh – A script that waits for the instance it runs on to finish bootstrapping, then configures CloudWatch agent to publish to the Amazon Managed Service for Prometheus endpoint that you provide as an argument when you launch your cluster.

4. Open each file and replace my-s3-bucket with the name of your bucket from Step 2.

5. Use the Amazon CLI to create an EMR cluster with the add_prometheus_endpoint_launcher.sh bootstrap action. In the following command, replace my-s3-bucket with the bucket that holds the bootstrap action, and replace managedpro-remote-write-workspace-url with the remote write endpoint for your Amazon Managed Service for Prometheus workspace. Be sure to specify an Amazon EMR release label of emr-7.0.0 or higher.

   aws emr create-cluster --name managedpro-cluster \
       --release-label emr-7.0.0 \
       --applications Name=Hadoop Name=AmazonCloudWatchAgent \
       --ec2-attributes KeyName=myKey --instance-type m7g.2xlarge \
       --instance-count 3 --use-default-roles
      --bootstrap-actions Name='Add Prometheus Endpoint',Path=s3://my-s3-bucket/add_prometheus_endpoint_launcher.sh,Args='managedpro-remote-write-workspace-url'

Use Amazon Managed Service for Prometheus as a data source for Amazon Managed Grafana

Once Amazon EMR has published the cluster metrics to Amazon Managed Service for Prometheus, you can use the following steps to visualize the metrics with Amazon Managed Grafana:

1. Use the Amazon Web Services Management Console to create an Amazon Managed Grafana workspace and user with appropriate permissions. For more information, see Create a workspace in the Amazon Managed Grafana User Guide.

2. Add your Amazon Managed Service for Prometheus workspace as a data source to Amazon Managed Grafana. For more information, see Use Amazon data source configuration to add Amazon Managed Service for Prometheus as a data source in the Amazon Managed Grafana User Guide.