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.

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.

I'm probably the last person who will defend many of Amazon's design choices, but this is really a matter of competence. Internet engineering is hardly unique in having difficult to understand/operate professional tools. While I will feel sympathetic towards someone who hurts themselves with power tools, you blame the tool when it malfunctions, not when the operator ignores basic safety.

Bottom line: this firm is incompetent to operate the tools they chose to use. Worse, they value the private data of their victims so little that they couldn't be arsed even to perform trivial sanity checks.

I wouldn't trust an outfit like this with the time of day.