←back to thread

461 points thunderbong | 1 comments | | HN request time: 0.215s | 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 #
reddalo ◴[] 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 #
1. danw1979 ◴[] No.42134455[source]
> 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

Cost Explorer, in the management account if you’ve got Organization set up.