News for hackers. Stuff that matters.

A comment on I Followed the Official AWS Amplify Guide and Was Charged $1,100. Parent comment

Re:I Followed the Official AWS Amplify Guide and Was Charged... by Terretta on Thursday November 14, 2024 @08:37AM (#42136027)
A service doesn't just "fall over" at a limit. There has to be other machinery to limit it.

Given that all your usage and traffic other than that at the limit request should not be gated or limited, why would you want someone else injecting additional complexity and bottleneck risk inline?

Determine your own graceful envelope, implement accordingly.

[ Parent | on HN ]
Re:I Followed the Official AWS Amplify Guide and Was Charged... by another-dave on Thursday November 14, 2024 @08:44AM (#42136075)
The OP was saying that having any spending limit would be antithetical to enterprise usage because it could bring critical services to a halt.

My point was, if that's a reason to have unbounded spending, why allow me to spin up a service that can get CPU or RAM bound?

> Determine your own graceful envelope, implement accordingly.

Which most people do have, but we then also want an "ungraceful" backstop — trains have both a brake and a dead man's switch.

[ Parent | on HN ]