5 ms·
> ...identified several misconfigured S3 buckets... For the love of all that is holy... have your AWS, Azure, etc. cloud service setup/config wire-brushed by a
by canada_dry 6y ago
> ...identified several misconfigured S3 buckets...
For the love of all that is holy... have your AWS, Azure, etc. cloud service setup/config wire-brushed by a 3rd party expert before deploying!
That, or perhaps these cloud services need a clippy like wizard: "Are you sure these files should be 777? Perhaps you want 644?".
- csunbird 6y agoIf you are using the AWS console, S3 actually asks you if you want the bucket to be public and gives you an option to create non public buckets.
- d33 6y agoThing is, S3 ACL is pretty ugly. UX is unpleasant and testing is terrible. It could be some accidental catch-all rule letting everyone in. I guess that the only lesson here is to set up an automated test that verifies whether the resource you wanted to block is actually blocked.
- lifeisstillgood 6y agoPresumably there are some tools that will do that ?
- musingsole 6y agoSuch as DivvyCloud: https://docs.divvycloud.com/docs/amazon-web-services https://docs.divvycloud.com/docs/amazon-web-services