Tagging for Cost Allocation

Thanks Jose! I am not able to access to the link that you shared. It is asking for workdocs login credentials which I don't have.

Jose, same result.

From your question, it is not clear what the input parameter is for. If the input parameter is for the cloudformation script that creates the Job, you can use cloudformation mappings to map the parameter values to the exact tag value needed on the resource. If the job resource already exists in a shared account and you are looking for a way to tag the Job execution to allocate the cost of running the job based on an input argument, unfortunately that is not possible using tags. You can only tag Glue resources, not specific Job Runs. To do chargebacks in this case, a cloudwatch event rule can be triggered when the Job completes (SUCCEEDED, FAILED, TIMEOUT). The rule can invoke a lambda that queries the job run for the job name using Glue.Client.get_job_runs, and get information about the Job run like the Job arguments, DPUSeconds etc. The lambda can then publish a custom metric to cloudwatch with business unit as a dimension. At the end of the month you can use aws cloudwatch get-metric-statistics to get a report of who ran the Jobs.

Thank you! Sorry for not asking you question clearly, but that is what exactly I was looking for for AWS Glue. I would also assume that the same process can be used for the Amazon Medical Comprehend by using input parameter for the Cloudformation template. Correct!