Cloud cost management: a practical guide

The gap between knowing this and actually doing it is where most teams lose ground. This guide covers what cloud cost management actually involves, where it usually goes wrong, and how to tell whether yours is in reasonable shape.

Cloud work rewards teams who automate early and punishes teams who click through consoles. Nothing below assumes a large team or a large budget — most of it is a decision somebody has to make and then write down.

Why it matters

Cloud bills grow quietly until somebody owns them. There is a version of this that is over-engineered, and it is worth avoiding. The version that survives contact with a real deadline is the simple one.

For most businesses the question is not whether this matters but how much of it is worth doing right now. That depends on what you are trying to achieve in the next few months, not on best practice in the abstract. Small and consistent beats large and occasional here.

How we handle it

Tag everything so cost maps to a team or a product. Where this goes wrong is almost never a lack of knowledge. The teams that stay on top of it are the ones who put it on a calendar rather than a wish list.

Operability is a feature, and it has to be built rather than bought. The version that works in practice is usually less elaborate than the version described in the guides.

Idle non-production environments are the usual first saving. The teams that handle this well are rarely the ones with the biggest budgets. If two people in the business would answer this differently, that gap is the actual problem.

A working checklist

If you want a quick read on where you stand, work through this. Anything you cannot answer confidently is where to start.

• Cloud bills grow quietly until somebody owns them
• Tag everything so cost maps to a team or a product
• Idle non-production environments are the usual first saving
• Someone is named as the owner, not just assumed to be
• There is a date in the calendar to review it again
• The decision and the reasoning behind it are written down somewhere findable
• You could explain the current setup to a new hire in five minutes

The mistakes we see most

The most common failure is not doing this badly. It is doing it once, during a launch, and never revisiting it. Circumstances move, the setup does not, and the gap widens quietly until something breaks or somebody notices the numbers.

• It was configured during a launch and has not been touched since
• Different people in the business believe different things are true about it
• There is no way to tell whether the last change helped or hurt
• The only person who understands it has left, or is about to

The bill is a design document: it tells you exactly what your architecture actually does. Getting it slightly wrong is survivable. Ignoring it entirely is not.

How we approach it

On our projects this gets handled during the build rather than added afterwards, because retrofitting it costs several times more than including it. We write down what was decided and why, so the next person to touch it is not guessing.

If you are working with someone else, the questions worth asking are simple: who owns this, how will we know it is working, and what happens when it needs to change?

What to do next

Pick the single item from the checklist above that would cause the most trouble if it turned out to be wrong. Fix that one, confirm it worked, then move on. The point is not perfection, it is knowing which of these you have consciously chosen to skip.