4 ms·
AWS defines a pretty clear delineation of responsibilities. They are responsible for security of the cloud, you are responsible for security in the cloud. http
by ryanmarsh 8y ago
AWS defines a pretty clear delineation of responsibilities. They are responsible for security of the cloud, you are responsible for security in the cloud.
https://aws.amazon.com/compliance/shared-responsibility-model/ https://aws.amazon.com/compliance/shared-responsibility-mode...
I’ve not seen AWS censor content, although I’m sure some cases might warrant it. That has nothing to do with a company that was negligent.
I don’t find AWS’ UI or command line clunky at all. In fact I find them clearer than most Unix tools.
It is not hard to know if you have world readable buckets in S3.
They should have a non-clunky dashboard of some sort where people can get a broad level overview of their security choices.
The AWS CLI allows you to easily pull the policy data attached to any resource and you can process it however you choose.
- mehrdadn 8y ago> I don’t find AWS’ UI or command line clunky at all. In fact I find them clearer than most Unix tools. That's not setting a terribly high bar ;) those take a while to learn too, people just forget that they ever went through that stage.
- the_new_guy_29 8y agoYou get a BIG INFO by AWS that you are changing the bucket to public access if you do (by default they all are private), how incompetent you have to be to not be able to read?