Skip to main content

<sysadmin stuff>

The AWS SDK for S3 suddenly stopped working for my non-AWS object stores (DigitalOcean, R2, etc)...and I thought I was losing my mind.

Well, looks like AWS decided to stop allowing others to leverage/freeload their software for use on competing services.

Understandable-ish, but doing it suddenly, know that stuff would break - on top of AWS blatantly making bank on services based on OSS software - well, that makes for some very bad karma. :sad_dog:

#DigitalOcean #mastoadmin #aws #cloudflare

DigitalOcean Spaces Customers using the latest versions (released on Jan 15, 2025) of the AWS CLI or any AWS SDK, or relying on a tool or application that depends on any of these versions of the AWS CLI or an AWS SDK, are experiencing failed uploads to Spaces buckets in all regions. This is caused by a change made by AWS on January 15, 2024 to the AWS CLI and almost all AWS SDKs (including boto3) to require use of “Data Integrity Protections for Amazon S3” (https://docs.aws.amazon.com/sdkref/latest/guide/feature- dataintegrity.html).
#mastoadmin #cloudflare #aws #digitalocean
in reply to Michael H

Roni Laukkarinen
Roni Laukkarinen
• •
What? Somehow missed this. But isn't the software open source?
in reply to Roni Laukkarinen

Michael H
Michael H
• •

@rolle Looks like yes, they are using the Apache license. So, at least it is trivial to make a fork of the last working version, and just continue building that fork.

Which, is probably the best thing in the long-run anyway. I just wish they didn't do a rug-pull in the meantime.

@Roni Laukkarinen
⇧