←back to thread

461 points thunderbong | 1 comments | | HN request time: 0.201s | source
Show context
davedx ◴[] 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 ◴[] 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 #
calgoo ◴[] No.42134155[source]
Cost and usage reports will show you what is being paid for. Then there are resources that won’t show up on that so I have used aws:config to pull down other resource lists and finally you can cross both reports to more less find everything.
replies(1): >>42136693 #
1. thayne ◴[] No.42136693[source]
Cost and Usage reports tells you what services you are paying for and which regions they are in, but doesn't give you a list of resources themselves.