←back to thread

461 points thunderbong | 1 comments | | HN request time: 0.199s | source
Show context
modernerd ◴[] No.42134059[source]
"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.

replies(20): >>42134131 #>>42134150 #>>42134268 #>>42134271 #>>42134282 #>>42134287 #>>42134291 #>>42134375 #>>42134462 #>>42134469 #>>42134517 #>>42134613 #>>42134695 #>>42134828 #>>42135170 #>>42135288 #>>42135373 #>>42135557 #>>42135706 #>>42136718 #
spacebanana7 ◴[] No.42134695[source]
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.

replies(15): >>42134715 #>>42134725 #>>42134727 #>>42134730 #>>42134881 #>>42134971 #>>42134978 #>>42135038 #>>42135127 #>>42135132 #>>42135209 #>>42135320 #>>42135326 #>>42135818 #>>42196913 #
1. dogleash ◴[] No.42135209[source]
> Even having the option of a hard spend limit would be hazardous, because accounting teams might push the use of such tools

Tell me you're Shadow IT without telling me you're Shadow IT.

I know legitimizing shadow IT is still the value proposition of AWS to a lot of organizations. But it sucks if that's the reason the rest of us can't get an optional feature.