aws-cloudformation / cloudformation-coverage-roadmap

The AWS CloudFormation Public Coverage Roadmap
https://aws.amazon.com/cloudformation/
Creative Commons Attribution Share Alike 4.0 International
1.1k stars 53 forks source link

[AWS::ElastiCache::SubnetGroup] - [Coverage] - Stacklevel-Tags not propagated to Resource #2031

Open r-heimann opened 2 months ago

r-heimann commented 2 months ago

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 though Tags are supported: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-elasticache-subnetgroup.html#cfn-elasticache-subnetgroup-tags

Example Stack:

AWSTemplateFormatVersion: 2010-09-09
Description: Example

Resources:
  ElastiCacheSubnetGroup:
    Type: AWS::ElastiCache::SubnetGroup
    Properties:
      Description: "Subnet Group for ElastiCache"
      SubnetIds:
        - <Subnet>

Other Details

CloudFormation Drift Detection is finding this issue as a proper drift, since drift detection is expecting the stacklevel-tags on the resource.

singhprz commented 1 month 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

r-heimann commented 1 month ago

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:

image

results in the Stacklevel-Tags not being added:

image

and CloudFormation Drift Detection finding this as a proper drift, since the tags are actually missing:

Screenshot 2024-05-16 061832

I am currently unable to test this in any other region than eu-central-1, so it may work in different regions.

r-heimann commented 1 month ago

If needed, i can create an AWS Support Ticket - but it should be easy to replicate the issue with the given template.