Cloud cost management, explained without the jargon

It comes up on almost every project, usually later than it should. Here is cloud cost management without the vocabulary that usually surrounds it.

Cloud work rewards teams who automate early and punishes teams who click through consoles. Assume whoever inherits this will have half your context and none of your patience.

The short version

Cloud bills grow quietly until somebody owns them. The cost of getting this wrong is rarely visible on the day it happens. Write the reasoning down alongside the decision, because the reasoning is what changes first.

Why people complicate it

Most of the confusion comes from tooling rather than from the idea itself. The cost of getting this wrong is rarely visible on the day it happens.

Tag everything so cost maps to a team or a product. The cost of getting this wrong is rarely visible on the day it happens. Check it against what you would want a competitor's site to get wrong.

Making it stick

Idle non-production environments are the usual first saving. The reasoning matters more than the rule, because the rule has exceptions. Doing this properly once is usually cheaper than doing it approximately three times.

In practice

Operability is a feature, and it has to be built rather than bought. Three things worth confirming about cloud cost management before you move on:

• Someone can say what the current setup is without going to look
• Tag everything so cost maps to a team or a product — and you know whether that is true here
• There is a way to tell whether the last change to this helped

If you are not sure where your systems currently stand on this, it takes us about an hour to find out.