Automatic aws:cloudformation:xyz resource tags are created inconsistently

[farski]

2. Scope of request

There are many resources that support tagging in CloudFormation that do not currently propagate to resources created through CloudFormation as the documentation would suggest.

This is not an exhaustive list, but some that I've noticed include:

• CloudFront distributions
• DynamoDB tables
• CloudFormation stacks (i.e., nested stacks)
• Lambda functions
• CloudTrail trails
• CodeBuild projects
• ACM certificates

[AlexChesters]

Lambda functions

This doesn't appear to be the case for us, I've just checked two of our Lambda functions and they have the following three tags that can't be edited:

• aws:cloudformation:stack-name
• aws:cloudformation:stack-id
• aws:cloudformation:logical-id

I wonder if support for this has been added since this issue was opened?

[rymndhng]

Bump on this, in my case, specifically for CloudFront distributions!

[mbp]

Same issue here. Adding Application Load Balancer and RDS DB clusters to the list.

[rene84]

I've noticed quite a number of resources not being tagged by CFN, for example IAM users and roles are not. S3 buckets are. Is there an exhaustive list somewhere of resource types that are supported rather than ones that aren't?