Provider returns 'Missing Resource Identity After Update' error for AWS resources on update

[mohamed-liveeo]

Terraform and AWS Provider Version

Terraform Version: v1.5.2

AWS Provider Version: latest [version not pinned]

Affected Resource(s) or Data Source(s)

ALL

Expected Behavior

The provider should update AWS resources successfully and return a valid resource identity after the update, without producing errors. When an update operation is performed, it should complete without reporting Missing Resource Identity After Update

Actual Behavior

An error is returned:
Error: Missing Resource Identity After Update: The Terraform provider unexpectedly returned no resource identity after having no errors in the resource update. This is always a problem with the provider and should be reported to the provider developer

Relevant Error/Panic Output

Error: Missing Resource Identity After Update: The Terraform provider unexpectedly returned no resource identity after having no errors in the resource update. This is always a problem with the provider and should be reported to the provider developer

Sample Terraform Configuration

n/a

Steps to Reproduce

Apply Terraform Changes

Debug Logging

Click to expand log output

GenAI / LLM Assisted Development

n/a

Important Facts and References

• The resource appears to update correctly in AWS
• After encountering the Missing Resource Identity After Update error, running terraform apply again shows no infrastructure changes are detected, suggesting that the resource update did complete despite the error message
• This issue only occurs on update operations, delete operations complete normally without this error
• I have not tested the create operation, so I am unsure whether it is also affected by this issue

Would you like to implement a fix?

No

[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.

[Terraformadillo]

I am also hitting this error.

[drivera-armedia]

Also getting this with 6.14.0:

Error: Missing Resource Identity After Update: The Terraform provider unexpectedly returned no resource identity after
having no errors in the resource update. This is always a problem with the provider and should be reported to the provider
developer

I'm unsure how safe it is to downgrade back to a prior version.

[justinbowes]

Downgrade to 6.13.0 (and terraform init -upgrade) restored expected behavior for me.

[danielrichardtorres]

Also hit this

[ryancausey]

This is being tracked in #44366 already.

[github-actions]

Warning

This Issue has been closed, meaning that any additional comments are much easier for the maintainers to miss. 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 v6.14.1 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!