What it changed
- From about US$240,000 a year to a target under US$40,000: a cut of more than 80%.
- Roughly US$200,000 a year back in the business, every year, for the same workload.
- Delivered in stages, each one measured on the bill, while the platform keeps running.
The situation
Cloud bills rarely explode in one go. They creep: an oversized database here, logs nobody reads there, servers running at night for traffic that only comes by day, services bought for one experiment and never turned off. After a few years of growth, this platform was paying about US$240,000 a year to AWS, and nobody could say exactly what for.
What I'm doing
This work is in progress. The method is the one I use on every bill:
- Find where the money goes. Every dollar on the bill traced to the service, the resource and the business feature behind it. On most bills a handful of lines carry most of the cost.
- Kill the waste first. Resources nobody uses, data nobody reads, capacity nobody needs at 3 am. It's the fastest money, and the least risky.
- Re-architect what's expensive by design. Always-on servers become serverless functions that cost nothing when idle, chatty services stop paying per message, and data moves to storage priced for how often it's read.
- Commit only when the baseline is known. Savings Plans and reservations come last, once the architecture has stopped moving, so the commitment matches what's really used.
Each stage is shipped and measured on the next bill before the next one starts, so the business sees the savings land, month after month, with the platform running throughout.
Why it matters to you
A cut of more than 80% sounds like a magic trick. It isn't: it's what happens when a platform designed for a server is redesigned for the cloud it runs on. If your AWS bill has grown faster than your business, the same money is probably sitting in yours.