Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

elliott-king.github.io

Post reply on HN
Print view View original

81–90 of 293 posts

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

#81

Post by devoutsalsa »

weinzierl wrote: post #76
modernerd wrote: post #30

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

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…

Bare metal server with unmetered bandwidth.

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

#83

Post by _betty_ »

reddalo wrote: post #34
davedx wrote: post #10

This seems like a glaring bug in the scripts run by that `npx` command. The author is correct, the scripts should 100%: - Choose the lowest cost resource (it's a tutorial!) - Cleanup resources when the `delete` subscript is run I don't think it's fair to expect developers to do paranoid sweeps of their entire AWS account looking for rogue resources after running something like this. If a startup had this behavior wou…

> do paranoid sweeps of their entire AWS account looking for rogue resources That's the thing that annoys me the most about AWS. There's no easy way to find out all the resources I'm currently paying for (or if there's a way, I couldn't find it). Without an easy to understand overview, it feels like I don't have full control of my own account.

this is one of the things i love about azure, easily being able to see everything.

closest i found in aws was something like tag manager?

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

#84

Post by rgblambda »

hereonout2 wrote: post #56
braza wrote: post #27

Earlier quoted context omitted.

It's a Tim foil hat pet conspiracy that I have, but I strongly believe that part important of the business model (or revenue share) is from people making mistakes or forgetting resources; more or less like gym subscriptions where the gym owners are more than happy to sell the [maximum_amount_of _people + 40%] knowing that the absenteeism will give the revenue offset that sustain part of the business.

There's certainly wastage in large organisations. Over provisioning or keeping that huge S3 bucket full of data from some long forgotten project. I suspect a lot of the huge AWS customers just eat this because it's so hard to mitigate. If a business has hundreds of AWS accounts it becomes very hard to track, and if each account can only shave a few hundred dollars a month off their individual bill then there's very l…

My team was migrating from one cloud provider to another and I was tasked to go through the soon to be deleted accounts in the old provider and delete resources that we were absolutely sure were serving no purpose whatsoever. You'd wonder why this wasn't something done on the regular.

Ended up saving at least $4000 dollars a month. And this was mostly sandbox environments that people forgot about.

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

#85

Post by soup10 »

modernerd wrote: post #30

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

Spend limits are such an obvious and necessary feature that the only reason they don't have them is shady business practices.

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

#86

Post by phatfish »

dkersten wrote: post #71

I know it’s minor in comparison, but I will never use AWS again after running up a $100 bill trying to get an app deployed to ECS. There was an error (on my side) preventing the service from starting up, but cloud waatch only had logs about 20% of the time, so I had to redeploy five times just to get some logs, make changes, redeploy five more times, etc. They charged me for every single failed deploy. After about tw…

I've only used Azure and it looks like ECS is equivelent to Azure Container Apps. I found their consumption model to be very cheap for doing dev/test. Not sure what it is like for larger workloads.

Charing per deployment sounds crazy though.

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

#87

Post by hereonout2 »

rgblambda wrote: post #84
hereonout2 wrote: post #56

Earlier quoted context omitted.

There's certainly wastage in large organisations. Over provisioning or keeping that huge S3 bucket full of data from some long forgotten project. I suspect a lot of the huge AWS customers just eat this because it's so hard to mitigate. If a business has hundreds of AWS accounts it becomes very hard to track, and if each account can only shave a few hundred dollars a month off their individual bill then there's very l…

My team was migrating from one cloud provider to another and I was tasked to go through the soon to be deleted accounts in the old provider and delete resources that we were absolutely sure were serving no purpose whatsoever. You'd wonder why this wasn't something done on the regular. Ended up saving at least $4000 dollars a month. And this was mostly sandbox environments that people forgot about.

I can well believe it, I know in my own team's account I can save hundreds a month and multiple thousands a year.

I keep raising this but it's never prioritized as it means taking my time from developing our products

Essentially my manager then loses dev time to reduce a bill that due to institutional accounting practices they never actually see!

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

#89

Post by blitzar »

NBJack wrote: post #16
themanmaran wrote: post #9

Par for the course for AWS. I tried following their quickstart Sagemaker guide to run Llama 2 a few months back. And it certainly spins up quick, but next day I realize it's running me $400/day. I was able to get the charges reversed, but definitely learned not to trust their guides.

Bug: Guide charged the user $400/day Status: Won't fix (working as intended) Notes: Got the author promoted to SDE III for great impact and revenue boost

Feature request: Write more guides that charge the user $400/day for a toy example.

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

#90

Post by _bare_metal »

devoutsalsa wrote: post #81
weinzierl wrote: post #76

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…

Bare metal server with unmetered bandwidth.

Indeed. Shameless plug of a toy I built that lets you see the price difference :

https://baremetalsavings.com

Post reply on HN