Like SMTP before it, S3 lies about being simple.
Once, you could send mail by telnet to port 25, and enter a few commands.
I use to send mails from Santa Claus that way.
For some reason, it's not that simple any more.
But oh boy do I not think it's designed to be used without a complicated SDK. I wish I didn't have to use the AWS one, but it looks like the only reasonably complete one. I'll use that until I'm sufficiently comfortable with the API to evaluate other options.
@liw SMTP is "okay", but SNMP! :)
(It's called 'AIStor' these days, presumably to be buzzword compatible 🙄 but it's really an S3 thing, SDK at https://www.min.io/download/aistor-sdk
@wouter @liw I hear garage is the new hotness: https://garagehq.deuxfleurs.fr/
@wouter Yes, I know about Minio. Too bad they've changed the license. I'm aiming for a portable subset of S3 for Obnam to avoid locking myself or those using Obnam to any specific implementation.
But I'd also prefer to not use the Amazon SDK in Obnam in the long term. But I'll use it to learn the API.
@bert_hubert @wouter Garage is not a client for S3, as far as I can see, and so is not interesting at this time.
@wouter On my phone so can't easily look up links but there was a bit of a brouhaha a couple of months ago.
@liw all cloud vendor APIs are designed to be hard to copy so you are stuck on that provider. SMTP was at least designed to be simple and mostly is unless you leave the tomb door unlocked and sendmail.cf gets out one moonless night
@liw "simple" adj.
1. complexity left for user to deal with
2. as many degrees of freedom as a straightjacket
@liw I went looking and was disappointed to find that backblaze / b2 doesn't document any Rust bindings for either their native API nor their S3-compatible API.