3 ms·
Amazon probably can't change S3 for backwards compatibility reasons (there was an outcry about just changing some legacy URLs last year), but they definitely ca
by earthboundkid 6y ago
Amazon probably can't change S3 for backwards compatibility reasons (there was an outcry about just changing some legacy URLs last year), but they definitely can and should make an "S4" which would be an S3 compatible storage layer with sane defaults.
Essentially, people only ever want one of two things:
- A private FTP bucket
- A public static asset website (with built-in CDN and HTTPS!)
Thing people never want:
- A public upload bucket
Seriously, no one wants that in any circumstance, ever. It's a huge liability. I literally cannot imagine anyone wanting anything even similar to it. But many, many companies have accidentally made one with S3.
While they're at it, S4 should also actually use IAM and all that other "modern" stuff that S3 doesn't have because it's so ancient.
- hackmiester 6y agoWhat's the fourth S stand for?
- ls612 6y agoSuper Simple Storage Service ;)
- earthboundkid 6y agoBingo!
- rumanator 6y ago> What's the fourth S stand for? Second Simple Storage Service.
- rumanator 6y ago>Thing people never want: > >- A public upload bucket Thus is outright wrong. Public upload s3 buckets are AWS's go-to basic technique to handle file uploads. AWS's API Gateway has a max file limit, and AWS advises developers to leverage S3 and lambda triggers to implement that usecases.
- bostonvaulter2 6y agoYes, but the upload url's should be signed by the server in that case.
- john-shaffer 6y agoThe bucket should never be publicly writable. The "go-to" techniques are signed POST requests [1] and signed URLs [2]. [1] https://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-post-example.html https://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-post-e... [2] https://docs.aws.amazon.com/AmazonS3/latest/dev/PresignedUrlUploadObject.html https://docs.aws.amazon.com/AmazonS3/latest/dev/PresignedUrl...
- earthboundkid 6y agoNo (see sister comments) and your incorrect answer is part of why AWS needs to reform S3.