Live data from Hacker News

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

elliott-king.github.io

291–293 of 293 posts

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

#291

Earlier quoted context omitted.

It's not just AWS. I think there are only two types of cloud providers: The ones like AWS and DigitalOcean that shift the risk to the customer and the ones that offer shady "unlimited" and "unmetered" plans. Neither is what I want. I wish there was a provider with clear and documented limits to allow proper capacity planning while at the same time shifting all the availability risk to the customer but taking on the f…

> It's not just AWS. I think there are only two types of cloud providers: The ones like AWS and DigitalOcean that shift the risk to the customer and the ones that offer shady "unlimited" and "unmetered" plans. Actually there is a third category, those who care. I will grant you it is a rare category but it is there. One example name: Exoscale[1] Swiss cloud provider, they offer: (a) hard spend limits via account pre-…

[deleted]

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

#292

I'm on the AWS Amplify team and wanted to give folks an update. First off, definitely empathize with the pain that Elliot went through. The referenced blog post is part of our advanced extensibility documentation, which covers how customers can use AWS CDK to add features that are not directly supported by the Amplify tooling, such as integrating with OpenSearch. Our initial OpenSearch extensibility documentation did…

CDK changing default removalPolicies was obviously problematic years ago:

https://github.com/aws/aws-cdk/issues/12563#issuecomment-771...

Another implicit surprise under the hood of CDK

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

#293

"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…

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 f…

Well, then enterprise won't use it.

OTOH for example the default quota of 55PB (yes, go check it) for your daily limit of data extraction from GBQ is funny, until you make a costly mistake, or some forked process turns zombie.

This is predatory practice, that I can't set up MONEY limits for cloud services.

Post reply on HN