Guide

How to read your cloud bill.

Your cloud bill is a map. Here's how to read it in twenty minutes and turn it into decisions, not anxiety.

Last updated

FinOps is a core service, not an add-on: see FinOps & Cloud Cost Optimization if you want the full approach.

Start with the trend, not the total

The total is a rounding error compared to the shape. Look for the month-over-month trend and the weekends: a flat bill with a weekly sawtooth is healthy, a spike that persists is an incident, and a bill that grows every month without a launch to explain it is a leak.

Group by service, then by team

  • By service. Compute vs storage vs network tells you where to hunt. In most accounts it's compute, then data egress, then data-at-rest.
  • By tag. Cost that can't be attributed to a team, environment, or workload is cost nobody owns. Missing tags are the first thing to fix.
  • By schedule. Reserved capacity and savings plans should match steady-state; on-demand should only fill the unpredictable tail.

The five anomalies to look for every month

  • A dollar spike in one region you don't remember launching there.
  • Egress charges out of proportion to your traffic (classic Load Balancer and NAT surprises).
  • Orphaned volumes, snapshots, and load balancers from deleted environments.
  • A service that grew linearly for four months without a code change.
  • Reserved capacity with a decreasing utilization trend.

Tagging is not bureaucracy, it's the budget

A pragmatic minimum: team, environment, workload, owner. Two rules make it stick:

  • Use AWS Organizations / Google Cloud / Azure built-in tag propagation, not a manual spreadsheet.
  • Make untagged spend cost more than tagged spend: route it to a "no owner" budget you review loudly.

Turn the bill into decisions

Cost is an engineering input, not a finance verdict passed down:

  • Publish a weekly digest: spend vs budget by team, plus the top three anomalies.
  • Add a budget guardrail per namespace or project so spending faster than expected fails loudly in CI.
  • Once a quarter, do a rightsizing pass on the top 10 compute resources by cost.

When the bill trends, tags are complete, and anomalies get an owner within days, you have FinOps. That's the whole game.

More reading

Want a hand putting this into practice?

Tell us where things stand and what you're trying to achieve. You'll get a straight answer and a practical next step.