←back to thread

461 points thunderbong | 1 comments | | HN request time: 0.222s | 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 #
slyall ◴[] No.42134613[source]
Dear Customer,

You have reached your Configured Maximum Monthly Spend Limit.

As per your settings we have removed all objects from S3, All RDS Databases, All Route53 Domains, all ESB volumes, all elastic IPs, All EC2 instances and all Snapshots.

Please update your spend limit before you recreate the above.

Yours, AWS

replies(5): >>42134673 #>>42134692 #>>42134739 #>>42135291 #>>42135359 #
raverbashing ◴[] No.42134692[source]
Nowhere (serious) does billing limits work like this

There's always a dunning period and multiple alerts

replies(1): >>42135648 #
1. cdchn ◴[] No.42135648[source]
Then you go beyond that. Now what?