aws s3api put-bucket-replication -> Missing required header for this request: Content-MD5

[jplitza]

Describe the bug

Calling aws s3api put-bucket-replication --bucket foo --replication-configuration '{...}' returns an error after updating to version 2.23.0 (via snap), while it worked before (with 2.22.35)

Regression Issue

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

Expected Behavior

The replication config ist applied to the bucket.

Current Behavior

An error occurred (InvalidRequest) when calling the PutBucketReplication operation: Missing required header for this request: Content-MD5

Reproduction Steps

BUCKET="test-put-replication-config"
aws s3api create-bucket --bucket "$BUCKET"
aws s3api put-bucket-versioning --bucket "$BUCKET" --versioning-configuration Status=Enabled
aws s3api put-bucket-replication --bucket "$BUCKET" --replication-configuration '{"Role":"foo", "Rules":[]}'
aws s3api delete-bucket --bucket "$BUCKET"

Possible Solution

No response

Additional Information/Context

I'm using a 3rd party S3 provider, not Amazon AWS S3.

CLI version used

2.23.0

Environment details (OS name and version, etc.)

Ubuntu 24.04 (installed via snap)

[kdaily]

Hi @jplitza,

This appears to be caused by the change in AWS CLI 2.23.0 to use a new checksum algorithm by default for S3 operations. The third party S3 provider you are using does not appear to support that change. You can read more about that change in this issue "Announcement: S3 default integrity change":

#9214

You can read more about workarounds using configuration options covered in Data Integrity Protections for Amazon S3.

[jplitza]

@kdaily Setting the request_checksum_calculation and response_checksum_validation settings to WHEN_REQUIRED does not help. Tried it via config file and environment variables.

[RyanFitzSimmonsAK]

@kdaily Setting the request_checksum_calculation and response_checksum_validation settings to WHEN_REQUIRED does not help. Tried it via config file and environment variables.

This is likely due to the behavior described in boto/s3transfer#327. Please try updating to the most recent version of the AWS CLI (or at least a version using s3transfer-0.11.2. The request_checksum_calculation and response_checksum_validation settings should work as intended once you do.

[github-actions]

Greetings! It looks like this issue hasn’t been active in longer than five days. We encourage you to check if this is still an issue in the latest release. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or upvote with a reaction on the initial post to prevent automatic closure. If the issue is already closed, please feel free to open a new one.