I did try seaweedfs ~half a year ago and I had issues with setting up users through terraform module (if I recall correctly, users endpoint were not correctly responding on delete), and lack of S3 expiry rules (you needed to use seaweedfs configuration or API for that). Other than that, I was pretty happy with it.
Alternatives to MinIO for single-node local S3
11–20 of 112 posts
Re: Alternatives to MinIO for single-node local S3
#12I enjoyed the smooth transition from minio to RustFS quite a lot.
Re: Alternatives to MinIO for single-node local S3
#13A notable mention should also be Versity GW, https://github.com/versity/versitygw/
Re: Alternatives to MinIO for single-node local S3
#14I am using Garage for my local DEV environment.
Re: Alternatives to MinIO for single-node local S3
#15A notable mention should also be Versity GW, https://github.com/versity/versitygw/
This is what I switched to as well, works nicely. Can have just a folder as a backend as well, which makes things pretty simple.
Re: Alternatives to MinIO for single-node local S3
#16Shout-out to rustfs.
Re: Alternatives to MinIO for single-node local S3
#17Incus (spiritual successor to LXD, after the fork-off by Canonical) has a simple S3 server built-in.
Re: Alternatives to MinIO for single-node local S3
#18I enjoyed the smooth transition from minio to RustFS quite a lot.
I didn't. Hit bug after bug after bug in RustFS. Current version seems to work fine for now but it's definitely "new project"
On flipside the project maintainers react very fast on any bug I submitted and it's fixed pretty quickly, so not really complaint, just warning
Re: Alternatives to MinIO for single-node local S3
#19Filestash (https://github.com/mickael-kerjean/filestash) has a s3 gateway plugin that I made. It proxy the S3 traffic to any downstream storage: SFTP, FTP, another S3, SMB, NFS, IPFS, ...
Re: Alternatives to MinIO for single-node local S3
#20A weird target, the author has.
The title is 'for single node local S3' but what they actually mean is 'for minio-compatibility', which is an entirely different question.
When I abandoned minio a year or so ago, I also surveyed the options, and settled on Garage. It lacked the GUI, but felt about the same complexity as minio. Perhaps a smidge more complexity, as I moved to 3-node and 5-node separate instances of garage, running as containers under Nomad.
I don't recall it being onerous, but I was looking for some basic S3-alike capabilities, not just minio-alike.
(How many people set out to build an object storage system with some number of AWS S3 primitives, but primarily try to match a third-party proprietary system's foibles?)
> So, Garage does work, but gosh…it is not just a drop-in replacement in terms of code changes.
I think in terms of actual code that uses local S3, it pretty much was a drop-in replacement. (I have multiple distribution/registry, Grafana Loki / Mimir, influx3 - all backing onto my object storage system, and the config changes there were modest - key+secret, and url - just as you'd expect.)