Maybe it teaches some of them not to stick their hand in lawnmowers.

When I was a student, I had an account at Citizens Bank, which had a branch on-campus. I pretty much never used it: I put some money in at the beginning, occasionally added some; used the ATM from time to time.

At the end of four years, I decided to close my account. There was less money in there than I thought there should be. I demanded an accounting. They happily demonstrated that there was a disclosed-only-in-fine-print fee charged each month that I didn't use the account according to some arcane formula. They wouldn't refund the fee.

So for the thirty or forty years since, I've never used Citizens Bank for anything, even if it would have been convenient. And I discouraged other people from doing so. I imagine I've cost them several thousand times those fees in revenue over the years.

Anyway, this is a story about AWS and their no-good, horrible-by-design billing practices.

Or it's a UX gap. If this is such a common complaint that's causing meaningful reputation damage, surely there'd be a better way to communicate this in the product? I think it's fair to assume that there's less interest in building features that encourage users to spend less money.

Old you was right. No student should ever enter personal payment information into AWS. You cannot afford the mistake.

They have chosen not to make a safe way to use it without financial risks.

> [Snapshots] get created automatically, often during deletion workflows, and nobody thinks to look for them.

creating random backups of things you are shutting down "just in case" that you must then remember to go back and delete. It's especially annoying if you stood up an EC2 instance or whatever, realized you messed up the configuration and immediately shut it down. Now you have a pile of poop running up your bill that you need to find and delete.