News for hackers. Stuff that matters.
Re:AWS to bare metal two years later: Answering your questio... by torginus on Wednesday October 29, 2025 @10:23AM (#45747246)
Unfortunately it's not, and it gets more difficult the more cloud-y your app gets.

You can pay for EC2+EBS+network costs, or you can have a fancy cloud native solution where you pay for Lambda, ALBs, CloudWatch, Metrics, Secret Manager, (things you assume they would just give you, like if you eat at a restaurant, you probably won't expect to pay for the parking, toilet, or paying rent for the table and seats).

So cloud billing is its own science and art - and in most orgs devs don't even know how much the stuff they're building costs, until finance people start complaining about the monthly bills.

Re:AWS to bare metal two years later: Answering your questio... by jmaker on Wednesday October 29, 2025 @11:44AM (#45748387)
We run regular FinOps meetings within departments, so everyone’s aware. I think everyone should. But it’s a lot of overhead of course. So a dev is concerned not only with DevOps anymore but with DevSecFinOps. Not everyone can cope with so many aspects at once. There’s a lot of complexity creep in that.
Re:AWS to bare metal two years later: Answering your questio... by torginus on Wednesday October 29, 2025 @12:53PM (#45749573)
Yeah, AWS has the billing panel, that's where I usually discover that after I make a rough estimate on how much the thing I'm building should cost by studying the relevant tables, I end up with stuff costing twice as much, because on top of the expected items there's always a ton of miscellaneous stuff I never thought about.
Re:AWS to bare metal two years later: Answering your questio... by UltraSane on Wednesday October 29, 2025 @12:33PM (#45749242)
I have Claude, ChatGPT, and Gemini analyze our AWS bills and usage metrics once a month and they are surprisingly good at finding savings.
Re:AWS to bare metal two years later: Answering your questio... by jrs235 on Friday October 31, 2025 @07:23PM (#45777806)
I have a fair idea of how much our cloud costs. However, others in the org don't want me to actually see how much it costs. Which is bonkers. I can help identify how we could rearchitect or investigate lowering our costs, if I know what they are and where to look first. No point guessing and accidentally optimizing something that will be an order of magnitude or more less beneficial.