Missing aws ecs task-family tags #26003
Unanswered
BabyBlue136
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi all!
How can I automatically tag the ecs task-definitions in aws, that are created for each job?
I'm running a containerized Dagster instance on aws, using Amazon Elastic Container Service. There are two code-locations, and two teams that are maintaining them. In the dagster.yaml's run_launcher block, I can't use an existing task-definition, as the two teams are using different container images. Each code-location automatically creates task-definitions (for every job) in the ecs service, copying the code-locations' task-definition, which is great, but these newly created definitions do not have any aws resource tags attached, and couldn't find any way to tag them on creation (other than doing it manually of course). I wouldn't want to define two separate daemons for the two teams, where I hard code the task-definitions.
Is there any way to resolve this? Am I conceptually doing something wrong? Are there any other way to achieve a state where there are no auto created resources in aws without tags?
Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions