Cloud cost and FinOps

Stage 1 of 9 · 7 lessons · ~2 weeks

How cloud billing works

Learn what Google Cloud actually charges for: the pricing units behind every line, how projects roll up into a Cloud Billing account, list versus effective cost, actual versus amortised cost, the lines nobody estimates and why cost data is always a little late.

Start: What you are billed for: time, quantity and requests

Lessons· one lesson for each topic, in this order

  1. 1What you are billed for: time, quantity and requests
  2. 2Cloud Billing accounts and projects
  3. 3List, discounted and effective cost
  4. 4Actual versus amortised cost
  5. 5The lines nobody estimated
  6. 6Billing data is late and keeps changing
  7. 7Estimating before you buildOptional

Do this

  • Open your cost tool and switch between service, region and usage type views.
  • Find one line each for compute, storage, data transfer and a managed service.
  • Switch between actual and amortised cost and note any difference.
  • Write down how far behind your cost data is today.
  • Estimate one small app in the pricing calculator and keep the estimate to compare later.

Start with· follow one of these

Practise

Keep handy

Also worth your time

Before moving on: A one-page note on your own cloud bill (a student or sandbox account is fine): every line explained with its pricing unit, which view you used (actual or amortised), and three charges a compute-only estimate would have missed.

Tauseef's advice
You do not need a big company bill to learn this. A sandbox account with a few dollars of spend has every kind of line in miniature. If cloud basics such as regions, VMs and networks are still new to you, do the cloud engineering roadmap at sefism.com/roadmaps/cloud-engineer/ first, then come back: FinOps is much easier when you know what each service does.

Mark this stage as not done?