AWS Builder Center is the official home for builders on AWS. Share and read what others are working on, follow people who inspire you, explore training and workshops, and find tools to support what you're building.
Clarification on AWS ElastiCache Tagging Notification for Redis Stack Created via CloudFormation
Hello,
I received the following email(10/28) from AWS Health regarding a possible issue with ElastiCache and CloudFormation stack-level tags:
Earlier in July, I created a Redis stack using ElastiCache through CloudFormation, and there have been no updates to the stack since then. Also, no tags were defined in this template, as we were unnecessary for our configuration.
Given these details, I’m not sure why I received this email and would appreciate any guidance on how to confirm if any actions are necessary. Are there steps to verify that my stack is unaffected, or any other checks I should perform?
Thank you for your assistance!
- Newest
- Most votes
- Most comments
One thing to check, resources created by the stack can also be tagged with aws:cloudformation:stack-name, aws:cloudformation:logical-id, and aws:cloudformation:stack-id. Check if similar tags are present on the Elasticache resource(s). If you confirm there are no stack tags and the resource tags from CFN aren't present, that's likely the reason.
If you are concerned, the steps in the notice to list how to re-apply tags updating/adding/removing a tag on the stack.
If you didn't apply tags to the stack, and don't use tags for the purposes noted in the Health event (access control, cost allocation, etc.), but want assistance confirming more specifics about the resources the next step would be to open a support case and reference the Health event you received.
Relevant content
asked 4 years ago
- AWS OFFICIALUpdated 2 years ago
