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

"Billing alerts" are a joke, give us hard spend limits. Then offer a way to set those limits during onboarding.

Building a business on blank cheques and accidental spends is shady. It's also a large barrier to adoption. The more times devs see reports like, "I tried [random 20-minute tutorial] and woke up to a bill for my life's savings and luckily support waived the fee this one time but next time they're coming for my house", the less they'll want to explore your offerings.

Hard spend limits are an anti-feature for enterprise customers, who are the core customer of AWS. Almost no level of accidental spend is worth creating downtime or data loss in a critical application.

Even having the option of a hard spend limit would be hazardous, because accounting teams might push the use of such tools, and thereby risk data loss incidents when problems happen.

Hard spend limits might make sense for indie / SME focused cloud vendors though.

> Hard spend limits are an anti-feature for enterprise customers

Yada yada yada, that's the same old excuse the cloud providers trot out.

Now, forgive me for my clearly Nobel Prize winning levels of intellect when I point out the following...

Number one: You would not have to turn on the hard spend limit if such functionality were to be provided.

Number two: You could enable customers to set up hard limits IN CONJUNCTION WITH alerts and soft limits, i.e. hitting the hard limit would be the last resort. A bit like trains hitting the buffers at a station ... that is preferable to killing people at the end of the platform. The same with hard spend limits, hitting the limit is better than waking up in the morning to a $1m cloud bill.

There's no way to implement a hard limit without getting in the middle of your system in ways that (a) alter the system design, (b) in ways you cannot correct for, and (c) not for the better.