←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: 0s | 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 #
slyall ◴[14 Nov 24 09:55 UTC] 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 #
1. mst ◴[14 Nov 24 11:47 UTC] No.42135291[source]▶
For an AWS account dedicated purely to experimentation that would be fine, though.

Having one AWS account where you actually run stuff, and one that follows the rule of "if it can't be paved and recreated from github, don't put it there" is exactly how a lot of people do it anyway.