Tagging resource type coverage

[PatMyron]

Should be able to tag-on-create and update tags at the system tag-level, stack-level and resource-level for all resource types that support tagging natively without unnecessary resource replacement

#4, #7, #19, #28, #29, #64, #69, #74, #77, #84, #95, #96, #117, #133, #155, #176, #178, #184, #193, #194, #195, #196, #200, #202, #203, #205, #219, #231, #236, #238, #248, #277, #306, #309, #328, #340, #350, #354, #358, #394, #398

Wonder if tagging should be an issue label..

[andyjgordon]

Hi @PatMyron, I don't see AWS::Glue::Crawler in the above list, which I know suffers the same issue (stack-level tags dont get applied). Also suspect AWS::Glue::Workflow and AWS::Glue::Trigger may have the same, but would need to test. Do you want me to create an issue for these?

[benkehoe]

As support is added for CloudFormation to add its automatic tags to more resource types, there should be a way to get those tags added to existing resources in a stack without providing a changed template.

[benbridts]

As support is added for CloudFormation to add its automatic tags to more resource types, there should be a way to get those tags added to existing resources in a stack without providing a changed template.

But it should be aware of resources that require some interruption or replacement when adding them. Eg. EIP or ElasticBeanstalk Environment

[pareddy113]

@PatMyron I see the stack level tags not being applied to AWS::EC2::VPCEndpointService as well, do you want me to create an issue for this?

[PatMyron]

@PatMyron I see the stack level tags not being applied to AWS::EC2::VPCEndpointService as well, do you want me to create an issue for this?

#350

[tvb]

@PatMyron can you update us if there is any progress being made here?

[Maycon-Santos-sm]

@PatMyron Is this really in progress or is more of a low priority issue?

[badaldavda8]

#644 #645

[benbridts]

#652

[rgoltz]

#742

[yvele]

As support is added for CloudFormation to add its automatic tags to more resource types, there should be a way to get those tags added to existing resources in a stack without providing a changed template.

@benkehoe does your comment covers the fact that explicitly adding Tag to an existing AWS::CloudFront::Distribution does not add the tags (while adding the tags via the console works fine)?

This is not working for an existing distribution:

Distribution:
  Type: AWS::CloudFront::Distribution
  Properties:
    Tags:
      - Key: my-tag-key
        Value: my-tag-value

By the way.. any workaround?

See also https://serverfault.com/questions/898453/aws-cloudformation-change-set-is-not-adding-tags-to-the-resources

[estanqueiroa]

Please add AWS EMRCluster to this list, CFN stack-level tags are not created. Thank you

CloudFormation automatically creates the following stack-level tags with the prefix aws::

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

[ayrawat17]

#1734 :Add support for stack level tags to AWS::EC2::KeyPair

[aerle]

#1786

[aerle]

#1807
#1808

[zenttic-aws]

#19

[aerle]

#901

[zipkid]

#1934

[desikora]

1939
1940