Spend came down, and for the first time it was possible to say which team spends what.
Rightsizing and cost attribution on AWS
- Sector
- Digital product
- Duration
- 4 weeks
- Role
- Head of DevOps · design and delivery
Where it started
The bill climbed every month and nobody could explain why. The problem was not only the amount: without attributing spend to a team or a product, there was no way to decide what to cut. Every conversation about cost ended in estimates.
The decision
Measure first, cut second. An inventory of what was actually running, rightsizing of the oversized resources, and tagging by team so every resource has an identifiable owner. On that base, budget alerts that warn before the month closes rather than when the invoice arrives.
What came of it
Spend came down, and for the first time it was possible to say which team spends what. The cost conversation stopped being an estimate and started resting on a number someone owns.
Something similar in front of you?
Get in Touch