Sefism Cloud Cost and FinOps Cheat Sheet

What this cheat sheet is

The Sefism Cloud cost and FinOps cheat sheet is a revision reference for understanding and reducing a cloud bill. It is written for cloud and DevOps engineers, analysts and students, and it follows the same order as the Cloud cost and FinOps roadmap.

It has 9 chapters and about 80 concepts in each edition. Each concept is written the same way: what it is in plain words, why it matters, and the mistake people usually make with it. Each chapter ends with up to three library resources to go deeper, and a glossary covers the smaller terms.

There are three editions, one per cloud: AWS, Azure and Google Cloud. The shared ideas are identical; the provider cards change, and the tool maps show the names on the other two clouds alongside, so you can read a job post or a colleague's notes written for a different cloud.

Chapter by chapter

1. How cloud billing works

Pricing units, how your cloud's accounts, subscriptions or projects roll up into an invoice, list, contracted, billed and effective cost, actual versus amortised cost, hidden cost lines, billing data latency, pricing calculators and a map of the cost tools on each provider. The first pitfall sets the tone: a stopped VM is not free, because its disks, snapshots and public IP addresses keep billing.

2. Reading the bill and tagging

Your cloud's cost tool and detailed export (Cost Explorer and Data Exports with CUR 2.0, Cost analysis and Cost Management exports, or billing reports and the BigQuery export), tags and labels, a tagging policy with a template, enforcement, untaggable and shared spend, and billing queries in SQL.

3. Allocation, showback and unit costs

Allocation by structure first, shared cost split methods, your cloud's allocation features (Cost Categories and split charges, cost allocation rules, or allocation views in BigQuery), showback, chargeback, unit cost and its formulas, reports by audience and allocation coverage as a quality measure.

4. Rate optimisation: commitments and spot

Commitment discounts, coverage and utilisation, break-even, your cloud's programmes (Savings Plans and Reserved Instances; reservations, savings plans and Azure Hybrid Benefit; or committed and sustained use discounts), spot capacity, usage before rate, managing commitments as a portfolio, and a table of savings programmes on each provider.

5. Usage optimisation

Rightsizing and your cloud's recommendations, idle and orphaned resources, non-production schedules, storage tiers and lifecycle rules, data transfer and NAT costs, Kubernetes requests and idle cost, OpenCost and your cloud's container cost allocation, logging and observability cost, and a savings levers checklist.

6. Forecasting, budgets and anomalies

Six concepts: cost forecasting, budgets and alerts, budget automation, cost anomaly detection, alert routing and a spike investigation runbook. The reminder: a budget is an alarm, not a brake, unless you deliberately add an action.

7. AI and GPU spend

Token pricing, prompt caching, batch discounts, model choice and routing, managed AI capacity options, GPU utilisation, reserving GPU capacity, AI unit cost and allocating AI spend to teams.

8. The FinOps Framework and FOCUS

The FinOps principles, the Inform, Optimize and Operate phases, domains and capabilities, personas, crawl-walk-run maturity, scopes, and FOCUS: the common billing format, its cost columns and how to export it on each provider.

9. Working with finance and a FinOps career

Capex and opex, accruals, month-end close, the monthly cost review and its checklist, engineering buy-in, FinOps roles, the FinOps Certified Practitioner exam, the 2026 job market and a FinOps portfolio.

Rules of thumb

The sheet closes with ten tips, among them: turn on the detailed billing export on day one, because you cannot get history back later; allocate by account, subscription or project first and use tags to refine; say which cost type every chart uses; cut waste and rightsize before you commit, then buy commitments in small slices; route every cost alert to the team that owns the spend; and for AI features, count tokens per task including history, retrieval and retries. The last one matters most: check the provider's current docs before quoting a discount or limit, because they change often.

How to use it with the roadmap

• After each stage, read the matching chapter and see whether you can explain every concept without looking. The chapter titles line up with the roadmap's nine stages.
• Before buying a commitment, reread chapter 4 end to end, especially break-even and usage before rate.
• Before a savings sprint, use the savings levers checklist in chapter 5 as your list.
• Before a monthly cost review, run through the checklist in chapter 9 and the spike runbook in chapter 6.

How it works on Sefism

Everything on Sefism is free to learn from. The public cheat sheet page shows every chapter title, with the first chapters open to read. Keeping the sheet uses credits and opens every chapter in your member area; if you add the Cloud cost and FinOps roadmap to your dashboard, its cheat sheet comes with it, and the first roadmap you add is free. New members get starting credits, and if you have a question the sheet does not answer, you can send it to Tauseef.

Related on Sefism

• FinOps Framework and FOCUS specification for chapter 8.
• OpenCost and Infracost for chapter 5.
• FinOps Certified Practitioner and State of FinOps report for chapter 9.
• Career questions: How do I practise AWS, Azure or Google Cloud without a surprise bill? and Can a fresher get a cloud engineer job?
• Related roadmaps: Cloud engineering and DevOps and cloud.

FAQ

Is this a substitute for the roadmap? No. The roadmap is the plan, with hours, milestones and checklists; the sheet is what you revise from once you have done the work.

What is the difference between billed and effective cost? Billed cost is what the invoice charges for a line. Effective cost spreads commitments and discounts back over the usage they covered, which is fairer for team reports. Chapter 1 covers all four cost types FOCUS names.

What is FOCUS? The FinOps Open Cost and Usage Specification, a common format for billing data that AWS, Azure and Google Cloud can export, so one query works across providers. Chapter 8 covers its columns and exports.

Should I buy a commitment as soon as I see on-demand spend? No. The sheet's order is waste first, rightsizing second, then commitments in small slices sized from your steady baseline.