4 ms·
> Despite no fewer than 6 attempts to patch the Open S3 Bucket problem, it remains. You can't patch people--legally, anyway. Heh, I use S3 for hosting static s
by Scoundreller 7y ago
> Despite no fewer than 6 attempts to patch the Open S3 Bucket problem, it remains. You can't patch people--legally, anyway.
Heh, I use S3 for hosting static sites only.
2 weeks ago they sent an email saying "[...] your AWS account xxxxxxxx has one or more S3 buckets that allow read or write access from any user on the Internet."
And I go "oh shit, what has write access set up?".
But nothing did. When they said "read or write", they meant 1, the other, or both. They just sent the same ambiguous email to everyone.
- jjoonathan 7y agoThat's so AWS it hurts. "Surely this AWS service can't be as poorly integrated with that other AWS service as it seems, because if it were that poorly integrated, it would be almost completely useless." "Oh. It is. FML."
- anon1m0us 7y agoI got the same email about S3 and some lambdas, with a link to fix them, that went to some generic page. You'd think Amazon could do better. Why not link me right to the bucket's configuration page? Why not list all the problem buckets in the email?
- Scoundreller 7y agoBTW, the email was sent at 3:45AM EST (my time zone), or a bit after midnight Seattle time. Dunno if there can be a wrong time to send an email, but I usually like to send important things like resumes around 9AM so it's at the top of the morning inbox.
- rapind 7y agoSame here. I checked everything over a few times thinking I'd missed something.
- cheez 7y agoHah, I got the same one and panicked!
- duxup 7y agoShouldn't let the engineers write the emails...me included.
- mike503 7y agoI had so many clients and people in my company ask me about this. The wording was horrible. It would have been better to identify things properly, or at the least, call it out clearer.