Amazon EMR

MAP Tagging Instructions for Amazon EMR

It is important for you to know the Migration tracking for Amazon EMR (previously called Amazon Elastic MapReduce) when the service is part of your migration plan.

Amazon EMR for the most part will continue to rely on the existing MAP2.0 tagging process. The tag-key will be same as the standard MAP tags as detailed in the MAP tagging instruction Guide. For the tag-value, it is important to make a note of the following:

  1. Generate a new Server ID for migration tracking of EMR. Please refer to the following section on generating additional Server Id.
  2. Only the resources (EC2, or EKS) launched or managed by EMR as well as resources of EMR must be tagged using the Server Id obtained from previous step.
  3. Tags can be added using the Tagging editor from AWS console, AWS Management console of respective AWS service, AWS CLI, AWS API, or infrastructure-as-a-code tools.

EMR allows for tagging propagation. Thus, in most cases, it is sufficient to tag EMR resources, and the resources launched by EMR (like EC2) automatically carry the EMR tags. In select scenarios where there is no actual new resources creation done by EMR (e.g. job submitted to virtual clusters without creation); it is expected that you will tag the respective resources of the dependent AWS services in same way as that of EMR.

References

The tagging instructions are also available in the Amazon EMR documentation.

  1. https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-plan-tags.html
  2. https://docs.aws.amazon.com/emr/latest/EMR-on-EKS-DevelopmentGuide/tag-resources.html