If what you're doing makes money, the last thing you want is to stop doing the thing making you money. If, instead, it costs you money, don't wait until a usag

If what you're doing makes money, the last thing you want is to stop doing the thing making you money. If, instead, it costs you money, don't wait until a usage surge to consider how to handle that – set it up now. You also don't need any latency in the loop or moving parts that could wrongly interfere with the reliability of making that money. Fortunately, the last thing this is is "opaque". You have all the observability you need to do what you want to do with unexpected usage. What AWS (and every CSP) gives you is all the instrumentation and out of band tools to implement your own angel of death, to API kill a runaway thing if that's what you want to do. You can also find countless TF and CDK patterns for it if you aren't sure how. But please, no, do not ask to make critical systems subject to the whims of some billing decision enforcer. The "why did they cut me off" complaints here far outnumber the "runaway bill" complaints.