Security

5041 readers

6 users here now

Confidentiality Integrity Availability

founded 5 years ago

MODERATORS

[email protected]

497

Amazon storing classified US government documents improperly (lemmy.ml)

submitted 7 months ago by [email protected] to c/[email protected]

64 comments fedilink hide all child comments

https://wetdry.world/@ari/112230288896956003

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 7 months ago* (last edited 7 months ago) (2 children)

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.

[–] [email protected] 6 points 7 months ago (1 children)

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

[–] [email protected] 1 points 7 months ago

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.

[–] [email protected] 2 points 7 months ago

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