Yeah. They also created a open source test suite for S3 clones.
This is a set of unofficial Amazon AWS S3 compatibility tests, that can be useful to people implementing software that exposes an S3-like API. The tests use the Boto2 and Boto3 libraries.
Oh heh, a trip down the memory lane. I wrote the initial version of that, in an era where AWS docs did not match observed S3 behavior. The only way to make an S3-compatible API was to create a suite of over-the-network tests to run against both AWS S3 and radosgw.
We also had a little grammar-based fuzzer for S3 requests (really, any HTTP), but over the last 10+ years I've lost track of what happened to that code. That found some incompatibilities with allowed character sets etc too.
Can vouch for it as an adequate self-hostable option. It has some missing features, compared to Minio, and is less compatible but works for most applications.
Garage worked for most of my use-cases but it lacks, among other endpoints[0], bucket ACLs and bucket replication. Anonymous access is also an open issue[1].
They are also a comparatively young project and while fully OSS do not, afaik, appear to have a solid long term funding source yet. Though that might be an opportunity to support them, if your company is interested in picking them.
Afaik Ceph has its own object-storage functionality as well, which seems to be S3-compatible: https://docs.ceph.com/en/latest/radosgw/#object-gateway
Yeah. They also created a open source test suite for S3 clones.
https://github.com/ceph/s3-tests
Oh heh, a trip down the memory lane. I wrote the initial version of that, in an era where AWS docs did not match observed S3 behavior. The only way to make an S3-compatible API was to create a suite of over-the-network tests to run against both AWS S3 and radosgw.
We also had a little grammar-based fuzzer for S3 requests (really, any HTTP), but over the last 10+ years I've lost track of what happened to that code. That found some incompatibilities with allowed character sets etc too.
I believe you're forced to have your data backed by a Ceph OSD. Whereas Minio can point to an NFS share on a NAS.
Minio used to be able to do this, but they dropped this feature - "gateway mode" - several years ago.
1 reply →
> I believe you're forced to have your data backed by a Ceph OSD.
It makes perfect sense as this is a feature of Ceph.
> Whereas Minio can point to an NFS share on a NAS.
Eh, different trade-offs.
Can vouch for it as an adequate self-hostable option. It has some missing features, compared to Minio, and is less compatible but works for most applications.
could you elaborate on this? we're looking at moving off cloudflare r2 in the somewhat near future and garage is on our short-list
Garage worked for most of my use-cases but it lacks, among other endpoints[0], bucket ACLs and bucket replication. Anonymous access is also an open issue[1].
They are also a comparatively young project and while fully OSS do not, afaik, appear to have a solid long term funding source yet. Though that might be an opportunity to support them, if your company is interested in picking them.
[0]: https://garagehq.deuxfleurs.fr/documentation/reference-manua...
[1]: https://git.deuxfleurs.fr/Deuxfleurs/garage/issues/263
2 replies →
I find garage to require quite a lot of fiddling.
Care to elaborate?
There were setup commands I needed to run before the docker image did anything. I’m used to just specifying an access/secret key and having it work.
Garage uses the AGPL v3.0 license, which is not an open source-friendly license.
Doesn't support if-match.