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
All stack resources of type AWS::CertificateManager::Certificate 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::CertificateManager::Certificate resource in your stack, it does not get assigned the built-in tags: aws:cloudformation:stack-name, aws:cloudformation:logical-id and aws:cloudformation:stack-id
Test Cases
deploy a 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.
r-heimann
commented
2 months ago
Name of the resource
AWS::CertificateManager::Certificate
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
All stack resources of type
AWS::CertificateManager::Certificateshould 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::CertificateManager::Certificateresource in your stack, it does not get assigned the built-in tags:aws:cloudformation:stack-name,aws:cloudformation:logical-idandaws:cloudformation:stack-idTest Cases
deploy a 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.
Other Details
No response