←back to thread

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

(elliott-king.github.io)
461 points thunderbong | 2 comments | 14 Nov 24 06:48 UTC | HN request time: 0.408s | 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 #
ElFitz ◴[14 Nov 24 08:11 UTC] No.42134079[source]▶
Is there even a simple way of listing all the existing resources in an AWS account? I’ve always had to check service by service, region by region. It’s tedious and error-prone.
replies(2): >>42134147 #>>42134155 #
1. ShroudedNight ◴[14 Nov 24 08:22 UTC] No.42134147[source]▶
I thought the tag editor was where one could get a comprehensive inventory of account resources? (Unable to check as I don't currently have easy access to the AWS console)
replies(1): >>42134162 #
2. calgoo ◴[14 Nov 24 08:25 UTC] No.42134162[source]▶
Yea it’s ok for that but won’t list everything. Example: ec2 snapshots won’t show up in the aws:config report but you will be charged for it, so Cost and Usage reports will show you what you will be charged for.