[OBJECT-STORAGE] [AWS CLI] AWS CLI enforces integrity header on PUT and POST requests

Incident Report for Scaleway

Update

We did discover that the trouble is broader than we thought.
As a first mitigation we do recommend that users wait before upgrading from aws v1 (we do recommand any version strictly prior to aws-cli 1.37.0 or boto3 < 1.36.0).
If aws v2 (that we do not recommend for the moment) is mandatory, we do recommend using aws-cli < 2.23.0
We are working actively to support those new versions, and plan to release fixes for the end of next week.
The details of the bug are :
support of CRC64NVME does not work properly
Tranfer-Encoding: chunked header does not work

Posted Jan 24, 2025 - 16:57 CET

Identified

Everyone using aws-cli versions versions v1: >=1.37.0 and v2: >=2.23.0 received a 400 errors on PUT and POST requests.

Posted Jan 16, 2025 - 15:04 CET

Investigating

aws-cli now enforces a CRC64NVME integrity checksum on all PUT and POST requests. This concerns the versions v1: >=1.37.0 and v2: >=2.23.0. We do not currently support this checksum, we are working on how best to handle it on our end. In the meantime, you can choose one of these options to keep your aws-cli request working:
- Use the --checksum-algorithm option with one of our supported checksums:
- SHA1
- SHA256
- CRC32
- CRC32C
- Use an older version of aws-cli, this way it will not enforce the CRC64NVME checksum

Posted Jan 16, 2025 - 14:57 CET

This incident affects: Elements - Products (Object Storage).