When cloud cost management is worth the effort

The advice here is unglamorous, which is probably why it gets skipped. Cloud cost management is not free, and pretending otherwise leads to bad decisions.

The bill is a design document: it tells you exactly what your architecture actually does. Check it against what you would want a competitor's site to get wrong.

When it is worth it

Cloud bills grow quietly until somebody owns them. Where this goes wrong is almost never a lack of knowledge. Anything you cannot measure here, you are deciding by taste, which is fine as long as everyone knows it.

When it is not

If nothing downstream depends on it and nobody is complaining, it can wait. The teams that handle this well are rarely the ones with the biggest budgets.

How to decide

Idle non-production environments are the usual first saving. In practice this is a scheduling problem more than a technical one. Most teams find the first pass takes an afternoon and the maintenance takes minutes a month.

The short version

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
• Cloud bills grow quietly until somebody owns them — and you know whether that is true here
• There is a way to tell whether the last change to this helped

Most of the value here comes from doing the first two things, not all of them.