←back to thread

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

(elliott-king.github.io)
461 points thunderbong | 1 comments | 14 Nov 24 06:48 UTC | HN request time: 0.406s | source
Show context
davedx ◴[14 Nov 24 07:46 UTC] No.42133938[source]▶
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?

replies(7): >>42134019 #>>42134079 #>>42134081 #>>42134225 #>>42134243 #>>42134471 #>>42134516 #
reddalo ◴[14 Nov 24 08:11 UTC] No.42134081[source]▶
> 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.

replies(8): >>42134089 #>>42134104 #>>42134146 #>>42134222 #>>42134354 #>>42134455 #>>42134772 #>>42134973 #
quixoticelixer- ◴[14 Nov 24 08:12 UTC] No.42134089[source]▶
Yes i was charged $400 once for services i had running for three months without any idea it was happening
replies(1): >>42134265 #
1. Moru ◴[14 Nov 24 08:48 UTC] No.42134265[source]▶
We were billed about $5000 per month by Google even though we had asked what the billing change would mean for us and they said you will be inside the free limits. Turns out we weren't.