Cloudformation-coverage-roadmap: AWS::EC2::EIP showing drifted after adding Tags

Created on 19 Dec 2019  路  6Comments  路  Source: aws-cloudformation/cloudformation-coverage-roadmap

Instructions for CloudFormation Coverage New Issues Template

Quick Sample Summary:

  1. Title -> AWS::EC2::EIP-Existing Attribute
  2. Scope of request -> AWS::EC2::EIP::TheResource-ExistingAttribute supports Tagging but Drift detection is showing false positives.
  3. Expected behavior -> Actual Values and expected values should be same.
  4. Test case recommendation (optional) ->

{ "AWSTemplateFormatVersion": "2010-09-09", "Resources": { "EIPjumphost0": { "Properties": { "Domain": "vpc", "Tags": [ { "Key": "Environment", "Value": "king" }, { "Key": "Name", "Value": "EIPjumphost0" }, { "Key": "Stack", "Value": { "Ref": "AWS::StackName" } } ] }, "Type": "AWS::EC2::EIP" } } }

  1. Links to existing API doc (optional) -> https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ec2-eip.html
  2. Category tag (optional) -> Compute
  3. Any additional context (optional)
    Attaching screenshot
    Screenshot 2019-12-19 at 11 12 09 AM
compute

Most helpful comment

We're facing this issue as well. All our resources are tagged but AWS::ApiGateway::RestApi, AWS::ApiGateway::Stage and AWS::ApiGateway::ApiKey are showing up as MODIFIED because Drift Detection thinks their tags were removed

All 6 comments

Is there a workaround to put the stack back to "IN SYNC" state?
Resources are currently in use...
It's exactly the same scenario, all EIPs are saying TAGs drifted.

Thanks

Seeing this as well...

I'm seeing this behavior as well with SNS::Topics. If you go to add Tags to the resource, the drift shows up and no tags are propagated to the Topic. I am working within the scope of updating a template used to deploy stackset instances.

I am seeing this for several resources AWS::ApiGateway::RestApi, AWS::ApiGateway::Stage, AWS::IAM::Role, AWS::SNS::Topic, but for others (like AWS::Lambda::Function) the tags are added and no drift is observed.

I can't understand how this is an issue. Doesn't this render the drift detection feature pretty much useless? It's not like RestApi or SNS::Topic are exactly niche, they must be in just about every stack out there.

@badaldavda is it worth updating the title of this issue to make it clear that this affects more than just EIPs?

We're facing this issue as well. All our resources are tagged but AWS::ApiGateway::RestApi, AWS::ApiGateway::Stage and AWS::ApiGateway::ApiKey are showing up as MODIFIED because Drift Detection thinks their tags were removed

Was this page helpful?
0 / 5 - 0 ratings

Related issues

rjpereira picture rjpereira  路  4Comments

fimbulvetr picture fimbulvetr  路  3Comments

JohnPreston picture JohnPreston  路  3Comments

hoegertn picture hoegertn  路  4Comments

mweagle picture mweagle  路  3Comments