You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the AWS ECS setup, the aws_ecs_service resource doesn't propagate tags to the tasks. This results in large amounts of fargate VCPU usage going untagged and potentially not visible in AWS Cost Explorer.
Could we get this added as per the AWS terraform documentation documentation on the service resource. There are two options, so perhaps defaulting to one and allowing a variable for the other would make sense.
The text was updated successfully, but these errors were encountered:
@alexmaras thanks for the feedback, we'll take a look. If you know how this should be solved and feel comfortable submitting a PR we will definitely try to get it merged!
In the AWS ECS setup, the
aws_ecs_service
resource doesn't propagate tags to the tasks. This results in large amounts of fargate VCPU usage going untagged and potentially not visible in AWS Cost Explorer.Could we get this added as per the AWS terraform documentation documentation on the service resource. There are two options, so perhaps defaulting to one and allowing a variable for the other would make sense.
The text was updated successfully, but these errors were encountered: