Mastodon Feed
isagalaev ("Ivan Sagalaev :flag_wbw:") wrote:
Random thought: S3 does not have an HTTP API (anymore).
At work, I needed a way to load config files owned by other teams over the network and asked people to expose them over HTTP. Someone put the file on S3, and it shouldn't be a problem, right? But since buckets are all in a single public namespace, they have to use a complicated, proprietary AWS auth. Which effectively means you have to use a proprietary library. Which means that you can't think of S3 as just another HTTP resource.