Mission, BC · est. 2026

Mission
FinOps

Workshops on FinOps for AWS & AI, and AWS 101 & landing zones. Taught from nearly seven years inside AWS.

Press start
Pixel-art Mt Baker at sunset over the Fraser Valley

© 2026 Mission FinOps · Yuvdeep Singh

Stage 0 · The story so far

Message

I spent nearly seven years inside AWS as a Senior Solutions Architect and Senior Technical Account Manager, helping large enterprises with their accounts, their landing zones, and their bills.

Most of those teams were never taught either one properly. They inherited an AWS organization, then a bill nobody could explain.

So I am building the workshops I wish they had had. Join early access, follow the build, and help shape what ships.

— Yuvdeep

Select your world

Two workshops.

Taught from experience: what I saw work, and break, across large enterprise AWS estates. Real stories, diagrams, decisions, and your questions. Not a product demo and not a certification course.

World 1

FinOps for AWS, AI & more

Boss: The bill nobody can explain.

  • How an AWS bill is built, and how to read it without guessing.
  • Cost Explorer, CUR 2.0, and FOCUS: which one answers which question.
  • Finding what moved, and who owns it: accounts, tags, ownership.
  • Savings Plans, RIs, and EDPs, and how teams get commitments wrong.
  • AI cost: Bedrock, inference, and GPU spend, attribution, forecasting.
  • Local AI for FinOps: put the evidence boundary before the model.
  • Explaining a cost movement to finance, limits included.

From years of enterprise AWS bills

World 2

AWS 101, landing zones & best practices

Boss: The account sprawl you inherited.

  • AWS 101: accounts, regions, IAM, and how billing really works.
  • Organizations and OUs: what goes where, and who pays for it.
  • Control Tower or not: when it helps, when it is overhead.
  • Guardrails: the SCPs and region controls worth having.
  • Identity Center and access patterns that survive the third team.
  • Networking, logging, and security baselines.
  • Best practices versus what enterprises actually do.

From years of enterprise AWS estates

Live onlineSmall groupsTaught from experienceQ&A throughout

Early access. Dates, length, and exact content are still being shaped, partly by the people on the list.

Save your spot

Get notified when it’s ready.

Enter name

Which worlds

Zero spam. You hear from me when a cohort opens. Your address stays in Mission FinOps’ own Cloudflare account, never shared or sold. To be removed, email hello@missionfinops.com with “Remove me”.

Quest log · free

Ten FinOps quests for this week.

No signup needed. Each one is something your team can do in an afternoon, in your own AWS account. Tick them off; your progress stays in this browser.

□□□□□□□□□□ 0 / 10 complete

  1. Why & how

    Why: Line-item billing evidence only exists from the day you enable it. Without it, every hard cost question stops at Cost Explorer.

    How: Billing and Cost Management → Data Exports → create a standard export (CUR 2.0) to an S3 bucket, Parquet, daily. Query it with Athena when a question comes up.

  2. Why & how

    Why: Tags you put on resources do not appear in billing until you activate them, and activation is not retroactive.

    How: Billing and Cost Management → Cost allocation tags → activate the tags you actually use: owner, application, environment.

  3. Why & how

    Why: Unowned cost is unexplained cost. The account is the one boundary every AWS bill already respects.

    How: Tag each account in AWS Organizations with an owner and team, and keep a one-page list of account → owner → purpose.

  4. Why & how

    Why: One company-wide budget alert tells everyone and therefore no one.

    How: AWS Budgets → one budget per account or owner tag, alerting the owner directly, at forecasted as well as actual spend.

  5. Why & how

    Why: It catches the spike in days instead of at month end, and the service itself costs nothing.

    How: Cost Explorer → Cost Anomaly Detection → monitors by service and by linked account, with alerts routed to the owners from quest 3.

  6. Why & how

    Why: Low utilization means you already over-committed. Low coverage only means opportunity if the usage is stable.

    How: Cost Explorer → Savings Plans and Reservations → Utilization and Coverage reports, over the last three months, per account.

  7. Why & how

    Why: Storage nobody is using keeps billing every hour, and snapshots quietly outlive the instances they came from.

    How: EC2 → Volumes filtered to state “available”; Snapshots sorted by age. Confirm with the owner, snapshot if unsure, then delete.

  8. Why & how

    Why: NAT gateways bill hourly even when idle, and public IPv4 addresses are charged per hour whether attached or not.

    How: CloudWatch: NAT gateways with near-zero bytes processed. VPC → Elastic IPs not associated. Check routes before removing anything.

  9. Why & how

    Why: Log and backup buckets only grow. Most data in them is never read after the first month.

    How: S3 Storage Lens to find the biggest buckets, then lifecycle rules to move older objects to cheaper storage classes or expire them.

  10. Why & how

    Why: The questions nobody can answer are where the money and the risk are. Writing them down is the first step to closing them.

    How: One sentence each: which cost, which scope, against what, for which decision. How to phrase them →

Read-level checks first; change things only with the owner’s agreement. Stuck on one? That is what co-op mode is for.

Co-op mode

For teams.

One question

Cost Question Review

One AWS cost question your team cannot close, answered in one evidence memo.

  • You send: the question in one sentence, then billing exports (CUR 2.0 or Cost Explorer) and context. Read-level access optional, never required.
  • You get: the conclusion, evidence for and against, what is missing, who owns the cost, how confident to be, and the next action.
  • How it runs: one intake call, the memo, one readout with engineering and finance.

See a sample memo ▶

Private run

Private team workshop

Either workshop, one or two days, live and remote, run for your team alone and built around your own AWS setup.

  • We walk through your accounts, tagging, billing data, budgets, guardrails, and ownership, and what I would change.
  • You leave with a prioritized plan your engineers can carry out. I never need write access.
  • Up to 15 people. Your questions, your estate, no generic slides.

Pilot

Local AI evidence setup

A private AI path for cost questions, where the evidence stays inside your boundary.

  • Deterministic cost evidence first (Kulshan), model interpretation second.
  • A local or private model you control, seeing only approved evidence.
  • Human review on material conclusions. No autonomous changes.

Read the architecture note ▶

All fixed fee, scoped on a 20-minute call. No retainers, no managed service, no resale.

Ask about training

Send a cost questionHow I handle access

Player 1

Yuvdeep Singh.

Class
AWS engineer. Former AWS Senior Solutions Architect and Senior Technical Account Manager.
XP
Nearly seven years inside AWS with large enterprises, including national banks and telecoms. Before that: splicing fibre, racking switches, network engineering, migrations, DDoS mitigation.
Base
Mission, BC, on Stó:lō land.
Loyalty
Independent. No reseller or partner quota behind anything I recommend.
Gear
Kulshan, my open-source, read-only AWS cost CLI, and a published IAM policy with zero write actions.
Party
Just me. You work with the person doing the work.

The Stó:lō have a word, tómiyeqw, meaning both great-great-great-great-grandparent and great-great-great-great-grandchild: seven generations back and seven forward, with the responsibility on whoever stands in the middle. Cloud infrastructure does not carry that weight. It is still worth remembering when someone signs a three-year commitment.

Side quests

Free stuff.

Read

Notes

All notes ▶

Play

Tools

Runs in your browser

Loot

Sample report

What an evidence-backed cost explanation looks like, on synthetic data.

kulshan report · v0.6.2 · Account: 012345678901 (synthetic) · Period: 2026-06-01 to 2026-06-30

Findings: 7

Open it ▶

Coming soon

101s

  • AWS 101
  • FinOps 101
  • AI 101

Unlocks later

Continue?

Yes ▶ join the waitlist

Or Email me about anything else.