Minor ImpactLast updated: Feb 3, 2025, 9:38 PM UTCFetched just now

AWS S3 SDK compatibility inconsistencies with R2

Started

Jan 17, 2025, 3:20 AM UTC

Resolved

Feb 3, 2025, 9:38 PM UTC

Timeline

ResolvedFeb 3, 2025, 9:38 PM UTC
An effective fix for this issue was identified and implemented. This incident is now resolved.
UpdatedJan 22, 2025, 4:33 PM UTC
We are continuing to work on a fix for native CRC32 checksum handling in R2 APIs. If you run into an issue, please see the documentation for workarounds based on the SDK that you are using: https://developers.cloudflare.com/r2/examples/aws/
UpdatedJan 17, 2025, 11:23 AM UTC
We are continuing to work on a fix for this issue.
IdentifiedJan 17, 2025, 3:20 AM UTC
AWS recently updated their SDKs to enable CRC32 checksums on multiple object operations by default. R2 does not currently support CRC32 checksums, and the default configurations will return header related errors such as Header 'x-amz-checksum-algorithm' with value 'CRC32' not implemented. Impacted users can either pin AWS SDKs to a prior version or modify the configuration to restore the prior default behavior of not checking checksums on upload. For more details, see the examples section of the R2 Docs for the relevant SDK: https://developers.cloudflare.com/r2/examples/aws/