Live data from Hacker News

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

elliott-king.github.io

271–280 of 293 posts

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

#271

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

> give us hard spend limits. Then offer a way to set those limits during onboarding

GCP requires this when you set up a new project. GCP deserves as much credit as AWS does scorn.

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

#272

Earlier quoted context omitted.

I gave up on AWS when I realised you can’t deploy a container straight to ec2 like you can on GCP. For bigger things, yeah the support’s better, for anything small to mid GCP all day. Primitives that actually make sense to how we use containers and such these days. And Bigquery

For AWS the solution for container deployments (without dealing with VMs) is Fargate, which imo works reasonably well.

I believe I was actually trying to use that. It’s been a few years so my memory is hazy, but isn’t Fargate just a special case of ECS where they handle the host machines for you?

In any case, the problem wasn’t so much ECS or Fargate, beyond the complexity of their UI and config, but rather that Cloudwatch was flaky. The problem that prevented the deployment was in my end, some issue preventing the health check from succeeding or something like that, so the container never came up healthy when deployed (it worked locally). The issue is that AWS didn’t help me figure out what the problem was and Cloudwatch didn’t show any logs about 80% of the time. I literally clicked deploy, waited for the deploy to fail, refresh Cloudwatch, saw no logs, click deploy, repeat until logs. It took about five attempts to see logs. Every single time I made a change (it wasn’t clear the error was on my end so it was quite a frustrating process).

On digital ocean, the logs were shown correctly every single time and I was able to determine the problem was on my end after a few attempts, add the required extra logging to track it down, fix it, and get a working deployment in under ten minutes.

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

#273

Earlier quoted context omitted.

It's been mentioned several time in HN comments that the AWS billing code is a giant pile of spaghetti and there is generally a lot of fear around making big changes to it. That's been one of the more interesting inside baseball facts I've learned here.

And yet somehow every time they launch a new product they have no problem adding it to their billing code.

I mean, adding some shotgun changes to a messy codebase is always significantly easier than refactoring the whole.

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

#274
post #257

Earlier quoted context omitted.

I use a visa gift card for AWS, I only risk what I have on the card.

In that case you are risking getting perma banned if anything goes south and you end up not paying anyways.

I'd prefer a permaban over permadebt to Amazon!

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

#275
post #237

Earlier quoted context omitted.

Now multiply the logic required by multiple cost factors across hundreds of services.

Imagine how impossible it is to actually build those services, with all their logic, if just this added logic is impossible :)

I didn't say it was impossible or even intractable. Its simply not as easy as everyone "why don't they justs."

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

#276
post #175

Earlier quoted context omitted.

That’s still very expensive. At that point you’d be well served by going dedicated hardware.

The droplet I have is 32 GB ram, 160 GB disk, 16 vCPUs (dedicated CPU, Regular Intel). What would you suggest me instead? I see Hetzner and maybe OVH could cost significantly less. Actually looks like with Hetzner I would get better specs at 115 eur per month. With 16 vCP, 64GB ram, 360 GB SSD. That's crazy, I didn't realize there's such a huge difference. I think your comment is actually impressively valuable to me.…

If you don't actually need colocation for your side project, looks like you could buy an i7-11700k, 64 GB of DDR4, a motherboard, and a 512 GB NVMe drive for ~$430. That's looking at new parts on amazon. You might be able to do better with e.g. ebay.

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

#277

Earlier quoted context omitted.

> Hard spend limits are an anti-feature for enterprise customers Yada yada yada, that's the same old excuse the cloud providers trot out. Now, forgive me for my clearly Nobel Prize winning levels of intellect when I point out the following... Number one: You would not have to turn on the hard spend limit if such functionality were to be provided. Number two: You could enable customers to set up hard limits IN CONJUNC…

There's no way to implement a hard limit without getting in the middle of your system in ways that (a) alter the system design, (b) in ways you cannot correct for, and (c) not for the better.

> There's no way to implement a hard limit without ...

I don't believe that for a minute.

You know why ?

Let's turn it on its head. What happens if the credit card on your AWS account expires or is frozen ?

You think AWS are going to continue letting you rack up money with no card to charge against ?

I betcha they'll freeze your AWS assets the nanosecond they can't get a charge against the card.

The mechanism for customer-defined hard limits is basically no different.

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

#278
post #246

Earlier quoted context omitted.

Also be aware it's not all roses with Hetzner. There are stories online of folks getting their accounts deactivated or not even getting approved. https://x.com/theo/status/1827480999305118135 https://x.com/heyandras/status/1856747621962191126

I was able to buy a 8 vCPU instance right now - do you know how frequent this problem may be?

Honestly can’t say how frequent it happens but I’ve read a few accounts that say you geographic location plays a big role in whether you are treated nicely or not.

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

#279

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 seems that automatic billing is something that cloud providers invented. For example, home Internet providers or mobile providers usually use prepaid plans, where they simply stop the service once you ran out of money (but you can connect your card account if you trust them). So you cannot get charged arbitrary amount for home Internet, and for mobile unless you travel.

> So you cannot get charged arbitrary amount for home Internet

Comcast (mostly) disagrees, you have a 1.2 TB data cap and "After that, blocks of 50 GB will automatically be added to your account for an additional fee of $10 each plus tax." They do have a limit of $100 on these charges per month at least.

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

#280
post #207

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…

I don't think DigitalOcean shifts risk to the customer. They have "pre-paid" cloud VPS plans of 5/10 USD per month with hard-limits right?

"Excess data transfer is billed at $0.01 per GiB"
Post reply on HN