Support aws_s3_bucket in partitions without S3 Object Lock option available

[Simple-Analysis]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• 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
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform CLI and Terraform AWS Provider Version

Terraform v0.13.0
aws-provider hashicorp/aws v4.10.0

Affected Resource(s)

• aws_s3_bucket

Terraform Configuration Files

Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.

resource "aws_s3_bucket" "test" {
   bucket = "tf-test-bucket"
}

Debug Output

...
Error: error creating S3 Bucket (tf-test-bucket): InvalidBucketState: Object Lock headers are not supported for target bucket endpoint.
      status code: 409,
...

Expected Behavior

In partitions that do not support S3 Object Lock, the S3 Bucket will be created when object_lock_enabled parameter is not declared.

Actual Behavior

The aws_s3_bucket resource is not created because the S3 Object Lock is expected to be queried.

Steps to Reproduce

1. terraform apply

Important Factoids

The S3 Bucket is being provisioned on a partition that does not have S3 Object Lock available.

The only workaround seems to be creating the S3 Bucket and using the data source for resources that are dependent on the exported attributes.

References

[scotthesterberg]

Is there any news on this, it seems to have gotten stale, but a fix would be quite helpful.

[Simple-Analysis]

Is there any news on this, it seems to have gotten stale, but a fix would be quite helpful.

We are still running into the issue in our environment. I was hoping the pull request would be sufficient but I wasn't quite sure what to expect.

Unfortunately we can't move to any newer versions (> 4.0.0) because of this issue and the Load Balancer updates for other partitions. So our provider versions are really scattered until the change is made.

[Simple-Analysis]

Possibly related to refactor effort #23106

[github-actions]

This functionality has been released in v4.24.0 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!

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