[Bug]: S3 Lifecycle rule with no filter gives a warning

[BroMattMiller]

Terraform Core Version

1.11.1

AWS Provider Version

5.90.0

Affected Resource(s)

aws_s3_bucket_lifecycle_configuration

Expected Behavior

If I understand the provider docs correctly, it's recommend to omit both filter and prefix options from a rule that should apply to all objects in the bucket. If I do this I get such a rule in AWS, but "terraform apply" gives an "Invalid Attribute Combination" warning. No warning should be issued in this case.

Actual Behavior

The warning includes:

No attribute specified when one (and only one) of [rule[0].prefix.<.filter] is required

Relevant Error/Panic Output Snippet

Terraform Configuration Files

resource "aws_s3_bucket_lifecycle_configuration" "main" {
  for_each = toset(local.data_bucket_types)

  bucket = aws_s3_bucket.main[each.key].id

  rule {
    id     = aws_s3_bucket.main[each.key].id
    status = "Enabled"

    expiration {
      expired_object_delete_marker = true
    }

    noncurrent_version_expiration {
      noncurrent_days           = 90
      newer_noncurrent_versions = 2
    }

    abort_incomplete_multipart_upload {
      days_after_initiation = 10
    }
  }
}

Steps to Reproduce

Create a lifecycle configuration with no filter and no prefix

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

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.

[ewbankkit]

@BroMattMiller Thanks for raising this issue.
It has already been noticed in #41710. I'm going to close this one as a duplicate so that we can concentrate discussion in the linked issue.
Please add any additional comments there.

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

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.