Pruning during a growth phase: lessions and techniques for optimizing cloud spend
2026-05-06 , Ballroom

Everyone wants double digit year over year growth in revenue at the same time also wanting double digit percentage reduction of their cloud spend. It seems impossible, but I've done it multiple times for multiple companies. It's not easy, it can be undone by one engineer (or director) overnight, and it requires lot of Aikido with management. I want to go over how you can re-frame success and still get costs to go down without slowing everything down with Infrastructure As Code and billing approvals.


We're paying Professional Services a lot of money to give us generic and mostly useless advice as part of our Cloud Provider Annual Agreement. They say it so often my teammates and I have started making bingo cards for every meeting. If we could have done the simple things, we would have already.

These are the solutions they sold your bosses on, but engineering doesn't think those are priorities. They have requirements from sales to increase footprint to enable that double-digit growth. Pushing everyone to a strictly controlled IAC where every request for new resources has to be approved instead of just spinning up only means you'll be even more over-provisioned "because the process is so slow".

I'll talk about the ways to do effective cost collection, which is going to have a cost. The next level is analysis of that billing data to find you have places where you can turn off unused resources (as well as identifying bursty loads). Finally we'll talk about how to reset expectations with management so that you can still succeed while the number goes up... just not as quickly.

Carl is has been part of the DevOps community for a long time (too long?), and I love sharing information and experiences with this community. When I'm not talking at DevOps Days, I run the Austin RISC-V Group, and I'm an organizer for the Works with RISC-V project. I'm also a RISC-V Ambassador, and do a lot of DevSecFinOps for my day job, and a lot of self-hosting outside of my day job.