Quick Sample Summary:
{
"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"
}
}
}

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
Most helpful comment
We're facing this issue as well. All our resources are tagged but
AWS::ApiGateway::RestApi,AWS::ApiGateway::StageandAWS::ApiGateway::ApiKeyare showing up asMODIFIEDbecause Drift Detection thinks their tags were removed