[Bug]: AWS SSM document association tags not reflected in AWS resource but are present in Terraform provider, causing drift

[glg-satish-tripathi]

Terraform Core Version

1.9.0

AWS Provider Version

5.90.0

Affected Resource(s)

aws_ssm_association

Expected Behavior

We expect that the tags should be applied in the very fist run it should not create drift in each run. Even the AWS CLI don't have any option to add tags while creating the association.
https://awscli.amazonaws.com/v2/documentation/api/2.1.21/reference/ssm/create-association.html
https://awscli.amazonaws.com/v2/documentation/api/2.0.34/reference/ssm/add-tags-to-resource.html
The association don't have any option as tag in the resource. So i believe this is a bug in the terraform provider.

Actual Behavior

aws_ssm_association tags are getting reapplied even if the first run already applied in AWS China.

Relevant Error/Panic Output Snippet

For AWS China every time tofu plan runs it tags_all shows drift in each runs:

Terraform Configuration Files

resource "aws_ssm_document" "test_document" {
name = "test-document"
document_type = "Command"

content = jsonencode({
schemaVersion = "2.2"
description = "Test document"
parameters = {}
mainSteps = [
{
action = "aws:runShellScript"
name = "runShellScript"
inputs = {
runCommand = ["echo Hello World"]
}
}
]
})
}
resource "aws_ssm_association" "test_association" {
name = aws_ssm_document.test_document.name
association_name = "test-association"
parameters = {}
targets {
key = "tag:Environment"
values = ["test"]
}
}

Steps to Reproduce

• tofu init
• tofu plan

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

• https://awscli.amazonaws.com/v2/documentation/api/2.1.21/reference/ssm/create-association.html

No response

Would you like to implement a fix?

None

[github-actions]

Community Guidelines

This comment is added to every new Issue to provide quick reference to how the Terraform AWS Provider is maintained. Please review the information below, and thank you for contributing to the community that keeps the provider thriving! 🚀

Voting for Prioritization

• Please vote on this Issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize it.
• Please see our prioritization guide for additional information on how the maintainers handle prioritization.
• Please do not leave +1 or other comments that do not add relevant new information or questions; they generate extra noise for others following the Issue and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.
• For new resources and data sources, use skaff to generate scaffolding with comments detailing common expectations.

[mikemartin1090]

I am also facing this issue!