PutObject fails with SignatureDoesNotMatch following release of 1.36

TL;DR

For "botocore.exceptions.ClientError: An error occurred (SignatureDoesNotMatch) when calling the PutObject operation: The request signature we ca": issue boto/boto3#4400 (closed, 32 comments): ### Describe the bug We're seeing intermittent signature errors when using boto3==1.36.x and botocore==1.36.x with S3 transfer acceleration enabled. Check your key and signing method. ``

botocore.exceptions.ClientError: An error occurred (SignatureDoesNotMatch) when calling the PutObject operation: The request signature we calculated does not match the signature you provided. Check your key and signing method.

Steps

1. Issue boto/boto3#4400 (closed, 32 comments): ### Describe the bug
2. We're seeing intermittent signature errors when using boto3==1.36.x and botocore==1.36.x with S3 transfer acceleration enabled. Either disabling transfer acceleration or downgrading to boto3==1.35.99 allows the upload to succeed.

botocore.exceptions.ClientError: An error occurred (SignatureDoesNotMatch) when calling the PutObject operation: The request signature we calculated does not match the signature you provided. Check your key and signing method.

3. - [x] Select this option if this issue appears to be a regression.
4. [jonathan343 (maintainer)]: The SignatureDoesNotMatch errors with transfer acceleration on boto3 below 1.36.0 were server-side: an intermediary was modifying the Transfer-Encoding header before S3, breaking the signature. That issue is resolved. A separate problem: third-party S3-compatible providers had checksum errors on the 1.36.x line; confirmed workarounds are pinning boto3 below 1.36.0 or setting requestchecksumcalculation to when_required for low-level ops.

When to use

You are seeing this: Either disabling transfer acceleration or downgrading to boto3==1.35.99 allows the upload to succeed. `` botocore.exceptions.ClientError: An error occurred (SignatureDoesNotMatch) when calling the PutObject operation: The request signature we calculated... Use this skill when you run into "PutObject fails with SignatureDoesNotMatch following release of 1.36".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: boto3 1.35.99, below 1.36.0. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

In the GitHub issue gh:boto/boto3#4400 (https://github.com/boto/boto3/issues/4400), the problem reported was: Issue boto/boto3#4400 (closed, 32 comments): ### Describe the bug

We're seeing intermittent signature errors when using boto3==1.36.x and botocore==1.36.x with S3 transfer acceleration enabled. Either disabling transfer acceleration or downgrading to boto3==1.35.99 allows the upload to succeed.

botocore.exceptions.ClientError: An error occurred (SignatureDoesNotMatch) when calling the PutObject operation: The request signature we calculated does not match the signature you provided. Check your key and signing method.

Regression Issue

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

Expected... The verified resolution was: [jonathan343 (maintainer)]: The SignatureDoesNotMatch errors with transfer acceleration on boto3 below 1.36.0 were server-side: an intermediary was modifying the Transfer-Encoding header before S3, breaking the signature. That issue is resolved. A separate problem: third-party S3-compatible providers had checksum errors on the 1.36.x line; confirmed workarounds are pinning boto3 below 1.36.0 or setting requestchecksumcalculation to when_required for low-level ops.