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:
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.
The tagging instructions are also available in the Amazon EMR documentation.