You are viewing a single thread.
View all comments View context
2 points
*

What kills me about S3 is that the use cases for publicly accessing S3 contents over HTTP have got to be vanishingly small compared to every other use of the service. I appreciate there’s legacy baggage here but I seriously wonder why Amazon hasn’t retired public S3 and launched a distinct service or control for this that’s harder to screw up.

permalink
report
parent
reply
6 points

Public access is disabled by default and it warns you when you enable it. How much more idiot proof does it need to be?

permalink
report
parent
reply
1 point

Honestly, I’m for removing the option and moving that “feature” somewhere else in AWS entirely. And those warnings aren’t really a thing when using IaC. Right now it’s still a “click here for self harm” button, even with the idiot proofing around it.

permalink
report
parent
reply
2 points

Wouldn’t say so, loads of people and organisations use it as a pseudo-CDN of sorts AFAIK

permalink
report
parent
reply

Security

!security@lemmy.ml

Create post

Confidentiality Integrity Availability

Community stats

  • 38

    Monthly active users

  • 217

    Posts

  • 352

    Comments

Community moderators