Cost related Tagging for EMR Serverless

Question

Hi team, I need some clarification on whether cost tracking is supported at the per-job level with EMR Serverless? For example, with regular EMR, costs are tracked at the cluster level, tagged by cluster id (aws:elasticmapreduce:job-flow-id). With Serverless, is the costs associated for each job submitted by application id or some other job identifier ( I am asking from cost granularity by tagging prospective)

Answer

You can tag new or existing applications and job runs. If you're using the Amazon EMR Serverless API, the AWS CLI, or an AWS SDK, you can apply tags to new resources using the tags parameter on the relevant API action. You can apply tags to existing resources using the TagResource API action.

Cost related Tagging for EMR Serverless

Conteúdo relevante