[Bug]: aws_s3_bucket_lifecycle_configuration causes drift when nothing has actually changed

[johannes-gehrs]

Terraform Core Version

1.10.5

AWS Provider Version

5.86.0 and higher

Affected Resource(s)

aws_s3_bucket_lifecycle_configuration

Expected Behavior

No drift if neither resources nor templates have changed

Actual Behavior

We see drift such as this

!     rule {
          id     = "abc"
          # (1 unchanged attribute hidden)

-         filter {
          }

-         noncurrent_version_transition {
-             noncurrent_days = 0 -> null
-             storage_class   = "INTELLIGENT_TIERING" -> null
          }
+         noncurrent_version_transition {
+             newer_noncurrent_versions = (known after apply)
+             noncurrent_days           = 0
+             storage_class             = "INTELLIGENT_TIERING"
          }
      }

The empty filter element appears to be removed. newer_noncurrent_versions is set to an unknown value.

We also see drift that looks like this

!     transition_default_minimum_object_size = "varies_by_storage_class" -> "all_storage_classes_128K"

And finally and most worrisome, it looks like Terraform wants to apply a material change to a filter element in some cases

!         filter {
+             object_size_greater_than = (known after apply)
+             object_size_less_than    = (known after apply)
              # (1 unchanged attribute hidden)
          }

Is this expected?

It appears to be caused by the changes/rewrite introduced in #41159
It does not occur in version 5.85.0

Relevant Error/Panic Output Snippet

Terraform Configuration Files

Not sure what the expectation is, here. You'll need both full configuration and state files to replicate this, and I cannot give you this.

Steps to Reproduce

Perform a plan

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

No response

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.

[justinretzolk]

Hey @johannes-gehrs 👋 Thank you for taking the time to raise this! This looks like it's related to some changes that were necessary with the aws_s3_bucket_lifecycle_configuration resource in version 5.86.0 that appear to be affecting you in a couple of ways.

For the reason behind these changes and some information around the transition_default_minimum_object_size bit of your issue, see #41126. In making the necessary changes to cope with the information in that issue, some configurations experienced unexpected drift similar to what you're reporting. There was quite a bit of discussion around that in a similar issue recently (#41268), where I wrote up a fairly lengthy comment detailing some of the behavior changes.

Can you review that and verify that by updating the configuration accordingly, you're able to get around this?

[johannes-gehrs]

Thank you, I will close this in favor of the existing isue.

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