[Bug]: Applies at `aws_s3_bucket_intelligent_tiering_configuration` are not idempotent if neither the filter block nor the prefix parameter are specified

[dgdelahera]

Terraform Core Version

1.2.4,1.3.7

AWS Provider Version

4.51.0

Affected Resource(s)

• aws_s3_bucket_intelligent_tiering_configuration

Expected Behavior

The ResourceBucketIntelligentTieringConfiguration should apply the default behaviour as described in the ResourceBucketLifecycleConfiguration.

Actual Behavior

Without the default behaviour, the terraform applies in the resources are not idempotent if neither the filter block nor the prefix parameter are specified

Relevant Error/Panic Output Snippet

No response

Terraform Configuration Files

resource "aws_s3_bucket" "bucket" {
  bucket        = "bucket"
}

resource "aws_s3_bucket_intelligent_tiering_configuration" "bucket_intelligent_tiering" {
  bucket = aws_s3_bucket.bucket.bucket
  name   = "intelligent-tiering"

  filter {
    prefix = ""
  }

  tiering {
    access_tier = "ARCHIVE_ACCESS"
    days        = 90
  }
}

Steps to Reproduce

1. Apply the resources listed before.
2. Apply again and check the output. The aws_s3_bucket_intelligent_tiering_configuration will be updated.

Debug Output

 # module.test_8.aws_s3_bucket_intelligent_tiering_configuration.bucket_intelligent_tiering[0] will be updated in-place
   ~ resource "aws_s3_bucket_intelligent_tiering_configuration" "bucket_intelligent_tiering" {
        id     = "test-8-w4qybq-mp70tb35z80bfr2p:intelligent-tiering"
        name   = "intelligent-tiering"
         # (2 unchanged attributes hidden)

      + filter {}

        # (1 unchanged block hidden)
     }

Panic Output

No response

Important Factoids

No response

References

No response

Would you like to implement a fix?

None

[github-actions[bot]]

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.

[seanturner026]

Digging deeper reveals that this has been discussed previously:

https://github.com/hashicorp/terraform-provider-aws/issues/29052