Open r-heimann opened 2 months ago
Hi,
We have validated that stack level tags are being propagated to subnet groups. To investigate further, could you please share your CloudFormation template as well as the method you're using to create the CloudFormation stack?
Thank you
Hi, thank you for your quick reply.
We are seeing this behavior in the AWS region eu-central-1
using the following CloudFormation template:
AWSTemplateFormatVersion: 2010-09-09
Description: Example
Resources:
ElastiCacheSubnetGroup:
Type: AWS::ElastiCache::SubnetGroup
Properties:
Description: "Subnet Group for ElastiCache"
SubnetIds:
- <Subnet>
Using the CloudFormation GUI to add Stacklevel-Tags:
results in the Stacklevel-Tags not being added:
and CloudFormation Drift Detection finding this as a proper drift, since the tags are actually missing:
I am currently unable to test this in any other region than eu-central-1
, so it may work in different regions.
If needed, i can create an AWS Support Ticket - but it should be easy to replicate the issue with the given template.
Name of the resource
AWS::ElastiCache::SubnetGroup
Resource name
No response
Description
For some unknown reason Stacklevel-Tags are not added to
AWS::ElastiCache::SubnetGroup
, even thoughTags
are supported: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-elasticache-subnetgroup.html#cfn-elasticache-subnetgroup-tagsExample Stack:
Other Details
CloudFormation Drift Detection is finding this issue as a proper drift, since drift detection is expecting the stacklevel-tags on the resource.