That seems okay, since you can use any S3 client library. So, good advice, but probably very few folks would have a need to touch the server side source.

Minio's client side libraries appear to be packaged separately, and Apache licensed: https://github.com/minio/minio-go

https://github.com/minio/minio-js

(Etc)

And if you do touch the server-side code..do it in an open source fork?

They more likely afraid of smaller and upcoming cloud providers offering it as an S3 drop in.

This plus CDNs I'd imagine too. S3 protocol is the new FTP and minio ticks the box quickly, they want their share of that (and deserve it imo)

Why would AWS offer Minio, a clone of an AWS Service, as a service?

That seems very confusing

Amazon wouldn't, but another cloud service might decide to run this rather than implementing their own S3-compatible object storage from scratch. Or they might use part of Minio's code to make their existing object storage solution compatible with S3.

IIRC from this podcast with Anand Babu Periasamy [0], they already do.

https://www.dataengineeringpodcast.com/minio-object-storage-...

Who does what? Amazon runs Minio?

The notes don't mention this and the audio is over one hour, would you mind clarifying?

another cloud service [Azure] decided to run this rather than implementing their own S3-compatible object storage from scratch

So that AWS can still get people to pay subscription fees to them, instead of using their own hardware with a FOSS solution, if MinIO becomes too popular.

I don't understand. Aren't you describing S3? Why would Amazon offer a second version of S3?

I understood it as a joke referencing Aamazon's tendency to take just any open source product that happens to gain enough popularity, rename it and offer it as a shiny new feature of AWS.

Self hosted as a feature. Akin to managed vs colo hosting.

They pretty much already offer this with outposts (its technically their hardware but its on your premises).

By "self-hosted" you still mean still running on AWS hardware? I don't understand. Why would anybody pay EBS rates instead of S3 rates, to get data stored in the same place by the same people?

Unless you're running a locally patched version AGPL is indistinguishable from GPL.

While this is true a word of warning: if you ever end up in a due diligence situation or a source code audit AGPL can really freak people out and hang up/derail the process until you get them to understand this point. If you can at all.

I'm pretty sure that - the prospect of AWS hosting and rebranding minio - was a joke.

Pretty sure AWS would like to have something that at least looks and feels sorta like S3.

And, being S3-compatible at an API level would be a big bonus for a company the size of AWS, especially if it had nearly native compatibility with the aws-cli tool.