[Bug]: Changes to aws_iam_instance_profile are not detected

[Nuru]

Terraform Core Version

1.5.3

AWS Provider Version

5.9.0

Affected Resource(s)

• aws_iam_instance_profile

Expected Behavior

When an aws_iam_instance_profile has a role attached in Terraform but not in AWS, terraform plan should detect the drift and correct it.

Actual Behavior

In this situation, terraform plan reports "No changes"

Relevant Error/Panic Output Snippet

No response

Terraform Configuration Files

locals {
  iam_role_name = "example"
  role_enabled  = length(local.iam_role_name) > 0
}

resource "aws_iam_instance_profile" "default" {
  count = local.role_enabled ? 1 : 0

  name = local.iam_role_name
  role = local.iam_role_name
  tags = { Name = local.iam_role_name }
}

Steps to Reproduce

• Use terraform apply to create an instance profile with an attached role
• Use aws iam remove-role-from-instance-profile to remove the role from the instance profile
• Run terraform apply again

Debug Output

No response

Panic Output

No response

Important Factoids

We did not intentionally remove the role from the profile, rather I just discovered it was missing. I do not know how it got into that state, but it was not as malicious or deliberate as the "Steps to Reproduce".

My best guess at how this actually happened is that after the instance profile was created, the attached role was updated in a way that caused it to be detached from the instance profile. Possibly the role was deleted and recreated.

References

These issues are similar, but do not specifically address the lack of drift detection:

• AWS Provider 4.9 AWS IAM instance profile not updated on manually changed AWS IAM role #24540
• instance profile does not link a role upon recreation of resources if it was previously missing #24974

Would you like to implement a fix?

No

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers 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.

[github-actions]

Warning

This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.

Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.

[github-actions]

This functionality has been released in v5.43.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.