Poorly configured AWS S3 buckets have been an source of shame for Amazon Web Services and its users.
I'm not sure why a poorly configured S3 bucket is a source of shame for AWS, any more than a poorly configured router would be a source of shame for Cisco.
To borrow parlance from gamers: "git gud". Before you do something, understand what you're doing and why. Ask questions. Read the strat guide. Grind it out in QA. If you fail to do these things and put yourself and your employer at risk, the shame is yours.
Biting the hand that feeds IT
