aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap

[AWS::ECS::Service] - [BUG] - resources don't receive the aws:cloudformation built-in tags / default service-managed auto-tags

Open
#2,062 1 comment 4 reactions 0 assignees View on GitHub
bug
Dominant language
No language data
Stars
1.1k
Forks
62
PR merge metrics
No merged PRs in 30d

Description

### Name of the resource

AWS::ECS::Service

### Resource Name

_No response_

### Issue Description

To find the right CloudFormation Stack, where a AWS resource is defined/maintained **aws:cloudformation:*** built-in tags are needed. This is an important function in day-to-day business.

### Expected Behavior

Resources with type `AWS::ECS::Service`, which are managed as CloudFormations Stacks, should automatically receive the `aws:cloudformation:*` built-in tags / automatic default CFN AutoTags.

Furthermore those aws:cloudformation:* built-in tags must be handled by CloudFormation Drift-Detection correctly (hence, aws:cloudformation:* tags are _not_ a drift)

### Observed Behavior

When you have an `AWS::ECS::Service` resource in your stack, it does not get the built-in tags assigned: `aws:cloudformation:stack-name`, `aws:cloudformation:logical-id` and `aws:cloudformation:stack-id`

### Test Cases

Deploy a CloudFormation stack containing this resource named above (e.g. sample from AWS docs) and check the tags on the console. You can't see aws:cloudformation:* built-in tags.

I've re-tested it right now in eu-central-1 region. No tags `aws:cloudformation:*` are added to the ECS Service resource.

### Other Details

In the area of AWS Elastic Container Service the resource AWS::ECS::Cluster already receiving aws:cloudformation:* auto-tags. Furthermore, the previous issue https://github.com/aws-cloudformation/cloudformation-coverage-roadmap/issues/1520 got closed by a mistake of cfn-github-issues-bot.

Contributor guide

Open the contributing guide

Research direction

Deploy a CloudFormation stack containing AWS::ECS::Service, using the AWS documentation sample, and inspect the service tags in the console, including eu-central-1. Compare the behavior with AWS::ECS::Cluster and issue 1520. Done means the service receives the three aws:cloudformation:* tags and CloudFormation drift detection does not report them as drift.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud, infrastructure
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.