We are continuing to work on a fix for this issue.
Posted Feb 06, 2025 - 19:10 UTC
Identified
We have determined the origin of the incident affecting our Object Storage S3 offer.
Here are some supplementary details : Start time : 01/01/2025 00:00 UTC Impacted Service(s) : Object Storage S3 Customers Impact : Requests to our Object Storage endpoint could return the error "InvalidArgument", on different Object operations. Root Cause : Following a recent AWS SDK upgrade, this issue is due to a new checksum enforcement in those SDKs. Unsupported headers are: - x-amz-content-sha256 with value STREAMING-UNSIGNED-PAYLOAD-TRAILER - x-amz-sdk-checksum-algorithm with value CRC32 Workaround A workaround is to downgrade the version, until the feature is implemented on our side. Max supported versions: - boto3 1.35.99 - legacy aws cli 1.36.40 - aws cli 2.22.35 - aws-sdk-go 1.72.3 - aws-sdk-java 2.29.52 - aws-sdk-js-v3 3.726.1 - aws-sdk-net 3.7.962.0 - aws-sdk-php 3.336.15 - aws-sdk-ruby 1.177.0 Ongoing Actions : The incident has been identified and our teams are mobilized to restore service as quickly as possible.
We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
Posted Jan 23, 2025 - 15:11 UTC
Investigating
We are currently experiencing an event affecting our Object Storage S3 offer. Start time : 01/01/2025 00:00 UTC
Our teams are fully committed to investigating this issue and working towards a resolution as soon as possible. As investigations are ongoing, we will share any new findings or updates with you as soon as possible.
We apologize for any inconvenience caused and appreciate your understanding.
Posted Jan 23, 2025 - 14:51 UTC
This incident affects: Storage || Object storage (BHS, GRA, DE, RBX, SBG, SGP, SYD, UK, US-EAST-VA-1, US-WEST-OR-1, WAW, YYZ, LIM).