Hi all, this is a followup of this question: https://outerbounds-community.slack.com/archives/C02116BBNTU/p1710789351744259 Is it possible to populate the launched ECS tasks with custom tags via environment variable for cost attribution purposes? The use case is that we have multiple sagemaker domains in an AWS account, where each domain represents a different ML project and has an unique tag

adsk:team=tenant_key

. We would like to add this tag to metaflow configs and finally all the ECS tasks launched by metaflow in each domain will be tagged with the corresponding tag, which is used for cost attribution. Thank you!

Currently attributes like flow_name are set as tags for AWS Batch jobs. Are you able to confirm that you are able to do proper cost attribution based on those tags? If so, that would be a good proof point to prioritize this feature higher on the list.

Hi @square-wire-39606, referring to this AWS blog, I think we can do the cost attribution by tagging AWS batch job. But we hope the tags to be custom tags like

adsk:team=tenant_key

, thank you!

are you able to verify that you are able to obtain the necessary cost attribution if you use the currently supported tags (granted they aren't the one that you are looking for)? this is a sensitive change where we also need to take into account if these attributes are going to evolve independent of the deployed flows - i would want to make sure we are headed in the right direction before devoting development effort.