News for hackers. Stuff that matters.
Re:The $1k AWS Mistake by fergie on Wednesday November 19, 2025 @09:06AM (#45979654)
Is it possible for hobbyists to set a hard cut off for spending? Like, "SHUT EVERYTHING DOWN IF COSTS EXCEED $50"
Re:The $1k AWS Mistake by ndiddy on Wednesday November 19, 2025 @09:15AM (#45979746)
You can with some effort, but cloud providers don't provide real-time information on how much you're spending. Even if you use spending alerts to program a hard cut-off yourself, a mistake can still result in you being charged for 6+ hours of usage before the alert fires.
Re:The $1k AWS Mistake by scotty79 on Wednesday November 19, 2025 @09:53AM (#45980283)
> You can with some effort, but cloud providers don't provide real-time information on how much you're spending.

This should be illegal. If you can't inform me about the bill on my request you shouldn't be legally able to charge me that bill. Although I can already imagine plenty of ways somebody could do malicious compliance with that rule.

Re:The $1k AWS Mistake by monerozcash on Wednesday November 19, 2025 @10:48AM (#45981031)
Fixing a small issue you have with AWS via overly specific legislative efforts probably isn't very productive.
Re:The $1k AWS Mistake by Raed667 on Wednesday November 19, 2025 @09:10AM (#45979701)
my understanding from reading this kind of threads is that there is no real way to enforce it and the provider makes no guarantees, as your usage can outpace the system that is handling the accounting and shutoff
Re:The $1k AWS Mistake by rileymat2 on Wednesday November 19, 2025 @09:17AM (#45979762)
That sounds like an architecture choice? One that would cause less revenue on the AWS side, with a conflicting incentive there.
Re:The $1k AWS Mistake by tacker2000 on Wednesday November 19, 2025 @09:39AM (#45980081)
to be fair, im not sure its a conscious choice, since its not really easy to couple lets say data transfer bytes directly to billing data in real time, and im sure that would also use up a lot of resources.

But of course, the incentive to optimize this is not there.

Re:The $1k AWS Mistake by pixl97 on Wednesday November 19, 2025 @11:01AM (#45981175)
I mean, generally real time isn't needed. Even hourly updates could save a massive amount of headache. 24 hours or more is becoming excessive.
Re:The $1k AWS Mistake by lenkite on Wednesday November 19, 2025 @12:49PM (#45982483)
AWS already does per hour billing for spot instances.
Re:The $1k AWS Mistake by mr_toad on Wednesday November 19, 2025 @09:11AM (#45979710)
Shut down everything? Including S3? There goes all your data.
Re:The $1k AWS Mistake by timando on Wednesday November 19, 2025 @04:15PM (#45985310)
Turn off S3 requests, but keep the data.
Re:The $1k AWS Mistake by conception on Wednesday November 19, 2025 @09:07AM (#45979667)
Yes, but you have to program it. And there is a little bit of whack so it might be $51 or something like that.