[SavantIdiot]

It can be a nuke or a surgical scalpel, e.g., contour traffic rather than taking down your entire site. And it is scriptable: any IAM role can be programmed into an action.

> If so yes then the problem is scaling,

Come on, man: you can't bash AWS if you don't even know how it works!

I'm addressing all these sob-stories of poor college students suddenly getting hit with $1000 bills for using lamda the wrong way, not a Series B startup with $5MM in the bank 20 employees and a billion CPM on their webapp.

[zamadatix]

I don't mean can you scale it down granularly or stop the service completely I mean can you say "when $100 disable everything in this AWS account that will generate billing without having to specify each thing individually in a rule". Snapshots, backups, IPs, instances, etc". It's not a matter of knowing how these things work it's a matter of finding what you're going to be billed for tomorrow because it is currently running - that's what's hard.

> Come on, man: you can't bash AWS if you don't even know how it works!

It is possible to understand how AWS works and still run into problems trying to scale AWS billing. This may not be apparent in a single ec2 instance setup but that doesn't mean the reason you see the complaints so often is everyone else are just idiots.

In my case I didn't lose 1000s or anything on my personal accounts more like 40 bucks by the time I just closed the account rather than wait 24 hours to track down the last thing in spend analyzer. It was a precanned product demo script for a cloud security product, first install went wrong and needed to be cleaned up manually but it was hard to tell what actually ended up staying vs not, especially since I didn't define the architecture ground up manually.

Note this is separate from "I didn't know if I clicked create 1000 GPU training instances it would cost a lot" though that would also be covered by an upfront monthly limit too I suppose.

Alternatively: imagine how quickly the UI would be fixed if the difficulty in finding how to create a new billable service were switched with the difficulty of finding which billable service is causing overruns.