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.

The billing department knows exactly what you were running, but they only tell you once a month...

They tell you in hourly increments for almost everything?

Even hourly isn't good enough. If I shut down some service, I want to know right now that nothing billable is left over. I don't want to have to wait an hour and come back and check only to find I forgot to clean up some IP address.

Why can we not have a "billable items" dashboard which simply shows, globally, a list of all items in your account which are billable, and how much they will cost if left running for 1 more hour/month?