S3 API Compatibility with CEPH Storage

[mvn187]

Acknowledgements

• I have searched (https://github.com/aws/aws-sdk/issues?q=is%3Aissue) for past instances of this issue
• I have verified all of my SDK modules are up-to-date (you can perform a bulk update with go get -u github.com/aws/aws-sdk-go-v2/...)

Describe the bug

The Issue arised because of the Lifecycle Setting transition_default_minimum_object_size that was introduced in https://aws.amazon.com/about-aws/whats-new/2024/09/amazon-s3-default-minimum-object-size-lifecycle-transition-rules/ and Terraform AWS Provider Version 5.70.0

Were using the S3 API to create CEPH Storage in our Openstack Project.

The Terraform Apply Fails with "timeout while waiting for state to become 'true' (last state: 'false', timeout: 3m0s)"

Regression Issue

• Select this option if this issue appears to be a regression.

Expected Behavior

S3 API Compatibiliy is not broken with that attribute.

Current Behavior

Terraform apply is not possible since upgrading to AWS Terraform Version >= 5.70.0

Reproduction Steps

https://docs.ceph.com/en/latest/radosgw/s3/bucketops/
Use the S3 API to create an Ceph Bucket with a version lower than on Sep 24, 2024.

Or use Terraform with AWS <= 5.70.0 create a ceph bucket with the aws s3 + lifecycle setting resource.

Then upgrade the provider to >= 5.70.0 and try to apply.

Possible Solution

Possibility for 3rd Party Services to skip the ready check/ this specific setting.

Additional Information/Context

Also opened an Issue on AWS Provider Github hashicorp/terraform-provider-aws#46021

Im tbh unsure which side is the best to ask for an upstream fix

AWS Go SDK V2 Module Versions Used

Version > 1.55.5 introduced this behaviour within the terraform aws provider hashicorp/terraform-provider-aws@v5.69.0...v5.70.0

Compiler and Version used

Operating System and version

[mvn187]

I found out our department responsible for hosting this project is using CEPH v18.2.4, which came out before the change to the s3 api in sep 2024... amazing
I assume this ticket can be closed, leaving this here as reference.

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

[mvn187]

I would like to reopen this ticket, since CEPH is on Version 19.2.3 and still failing.

I see the Issue either on s3 api or aws terraform provider side.

Terraform Request

http.request.body=
  | <LifecycleConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/"><Rule><Expiration><Days>14</Days></Expiration><Filter></Filter><ID>expire14days</ID><NoncurrentVersionExpiration><NoncurrentDays>2</NoncurrentDays></NoncurrentVersionExpiration><Status>Enabled</Status></Rule></LifecycleConfiguration>
   http.request.header.authorization="AWS4-HMAC-SHA256 Credential=XXXXX/us-east-1/s3/aws4_request, SignedHeaders=accept-encoding;amz-sdk-invocation-id;amz-sdk-request;content-length;content-type;host;x-amz-checksum-crc32;x-amz-content-sha256;x-amz-date;x-amz-transition-default-minimum-object-size, Signature=*****" http.url=https://xxxxxxx/XXXXXX?lifecycle= tf_provider_addr=registry.terraform.io/hashicorp/aws @module=aws http.request.header.x_amz_date=20260118T133600Z http.request.header.x_amz_transition_default_minimum_object_size=all_storage_classes_128K tf_req_id=d81213e4-9cec-b9aa-c660-a5371dfae97f tf_rpc=ApplyResourceChange http.user_agent="APN/1.0 HashiCorp/1.0 Terraform/1.14.2 (+https://www.terraform.io/) terraform-provider-aws/6.28.0 (+https://registry.terraform.io/providers/hashicorp/aws) aws-sdk-go-v2/1.41.0 ua/2.1 os/linux lang/go#1.25.5 md/GOOS#linux md/GOARCH#arm64 api/s3#1.95.0 m/a,e" rpc.system=aws-api tf_resource_type=aws_s3_bucket_lifecycle_configuration http.request.header.amz_sdk_invocation_id=2f03c9dc-f44a-4e1f-878e-84412f03e14b rpc.service=S3 http.method=PUT http.request.header.accept_encoding=identity http.request.header.amz_sdk_request="attempt=1; max=25" http.request.header.content_type=application/xml http.request.header.x_amz_content_sha256=95884fde6ff63b5cad8e4a3dba446e37b7703f4baab0acd263989ddd58022532 tf_mux_provider="*proto5server.Server" http.request_content_length=305 net.peer.name=XXXXXXX timestamp=2026-01-18T13:36:00.560Z

Response

http.response.header.x_amz_request_id=tx0000025a09fa1121e316e-00696ce1c0-6d0cd2dc-ceph-objectstore-st1-eu-de-2 http.status_code=200 rpc.method=PutBucketLifecycleConfiguration tf_resource_type=aws_s3_bucket_lifecycle_configuration aws.region=aws-global http.response.header.connection=Keep-Alive rpc.service=S3 tf_aws.signing_region="" tf_provider_addr=registry.terraform.io/hashicorp/aws tf_req_id=9f540acc-f2be-5d75-7478-32d53283176f tf_rpc=ApplyResourceChange http.response.header.date="Sun, 18 Jan 2026 13:36:00 GMT" rpc.system=aws-api @caller=github.com/hashicorp/aws-sdk-go-base/v2@v2.0.0-beta.70/logging/tf_logger.go:45 @module=aws http.duration=182 http.response.body="" http.response.header.content_type=application/xml tf_aws.sdk=aws-sdk-go-v2 tf_mux_provider="*proto5server.Server" timestamp=2026-01-18T13:36:00.602Z

[lucix-aws]

AWS SDKs are designed to work with official AWS services - anything else is outside of our support scope. "S3-compatibility" is a guarantee made by the owner of a service that claims to be S3-compatible. If you cannot reproduce this issue against AWS S3 then this will not be actionable for us.