Skip to content

ECS backend tag propagation of shinyproxy task/service tags to apps on demand task and task definition #558

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
damianslee opened this issue Apr 29, 2025 · 0 comments

Comments

@damianslee
Copy link

to be able to group all shinyproxy resource AWS costs by tag in aws cost explorer, is it possible for shinyproxy ECS backend to copy tags from its own task or service or task definition to the on demand ECS task it creates?

AWS tags applied to ECS service and task definition are successfully propagated to the shinyproxy task when the ecs service property propagate_tags is set to "SERVICE" or "TASK_DEFINITION". however this doesn't extend to shinyproxy creating its own ECS tasks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant