←back to thread

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

(elliott-king.github.io)
461 points thunderbong | 1 comments | 14 Nov 24 06:48 UTC | HN request time: 0.2s | source
Show context
modernerd ◴[14 Nov 24 08:08 UTC] 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 #
hnben ◴[14 Nov 24 09:37 UTC] No.42134517[source]▶
could you set a limit to the credit-card associated with the cloud service? Or would it still create costs after the limit has run out, which they would collect in other ways?
replies(2): >>42134557 #>>42136081 #
1. benterix ◴[14 Nov 24 09:45 UTC] No.42134557[source]▶
No, setting a limit doesn't work. They will still try to charge you. A friend had a charge for $0.35 running for a year after his credit card expired. They closed his account later but would definitely come after you if the amount was significant.