I Followed the Official AWS Amplify Guide and Was Charged $1,100

This seems like a glaring bug in the scripts run by that `npx` command. The author is correct, the scripts should 100%:

- Choose the lowest cost resource (it's a tutorial!)

- Cleanup resources when the `delete` subscript is run

I don't think it's fair to expect developers to do paranoid sweeps of their entire AWS account looking for rogue resources after running something like this.

If a startup had this behavior would you shrug and say "this happens, you just have to be paranoid"? Why is AWS held to a different standard by some?

> do paranoid sweeps of their entire AWS account looking for rogue resources

That's the thing that annoys me the most about AWS. There's no easy way to find out all the resources I'm currently paying for (or if there's a way, I couldn't find it).

Without an easy to understand overview, it feels like I don't have full control of my own account.

You can set up daily or hourly cost and usage reports on the account. I built a finops function based on it, feeding the data into a Postgres db. Make sure to select incremental updates, if not you’ll en up paying for tb of s3 storage.

TB of S3 storage is surprisingly inexpensive though. Especially compared to everything else AWS.