Re:Twilio: Someone broke into our AWS S3 silo, added 'non-ma...
by donor20 on Wednesday July 22, 2020 @01:32PM
(#23919437)
Not only do you have to jump through hoops to make it public, if you are worried can't you use Amazon Macie and have a separate org level view that alerts you to any public buckets?
I don't bother because it seems pretty clear what buckets are public.
That said, quick tip to make your life easier.
DON'T use S3 ACL's
DON'T use S3 policies.
If I was AWS and didn't have so many customers I'd probably just create one mental model (IAM policies probably) as the place to manage things and block the rest.
https://aws.amazon.com/macie
I don't bother because it seems pretty clear what buckets are public.
That said, quick tip to make your life easier.
DON'T use S3 ACL's DON'T use S3 policies.
If I was AWS and didn't have so many customers I'd probably just create one mental model (IAM policies probably) as the place to manage things and block the rest.