s3_bucket_lifecycle_configuration Warning: Invalid Attribute Combination

[jaw111]

Terraform and AWS Provider Version

OpenTofu v1.9.1
on linux_amd64

hashicorp/aws 5.97

Affected Resource(s) or Data Source(s)

• s3_bucket_lifecycle_configuration

Expected Behavior

It should be possible to specify an empty filter per the example in the documentation.

Actual Behavior

I see a warning that this will be an error in a future version of the provider.

Relevant Error/Panic Output

╷
│ Warning: Invalid Attribute Combination
│
│   with aws_s3_bucket_lifecycle_configuration.example,
│   on s3.tf line 16, in resource "aws_s3_bucket_lifecycle_configuration" "example":
│   16:     filter {}
│
│ No attribute specified when one (and only one) of
│ [rule[0].filter[0].prefix.<.object_size_greater_than,rule[0].filter[0].prefix.<.object_size_less_than,rule[0].filter[0].prefix.<.and,rule[0].filter[0].prefix.<.tag]
│ is required
│
│ This will be an error in a future version of the provider
│
│ (and one more similar warning elsewhere)
╵

Sample Terraform Configuration

Click to expand configuration

resource "aws_s3_bucket_lifecycle_configuration" "example" {
  bucket = aws_s3_bucket.bucket.id

  rule {
    id = "30-day-lifecycle"

    filter {}

    expiration {
      days = 30
    }

    status = "Enabled"
  }
}

Steps to Reproduce

1. Apply the configuration.

Debug Logging

Click to expand log output

GenAI / LLM Assisted Development

n/a

Important Facts and References

No response

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.

[jmuleiro]

I'm noticing the same thing with:

Terraform v1.11.4
on linux_amd64
+ provider registry.terraform.io/hashicorp/aws v5.97.0

If you remove filter {}, you get:

│ No attribute specified when one (and only one) of [rule[0].filter,rule[0].prefix] is required
│ 
│ This will be an error in a future version of the provider
│ 
│ (and one more similar warning elsewhere)

[jmuleiro]

Looks like this issue is a duplicate of #42274.

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