AWS gets weird at scale.
I’m Yuvdeep. I spent nearly seven years inside AWS as a Senior TAM and Solutions Architect. Now I work independently, on the problems your team can’t close.
Or email hello@missionfinops.com
Kulshan (Mt Baker), from the Fraser Valley
- Kulshan, my open-source AWS cost CLI, on PyPI
- Read-only IAM policy, published with its SHA-256
- 12 technical notes on AWS cost questions
What people bring me
FinOps is often where the question starts. It’s rarely where it ends.
How it works
You tell me what changed. I look, read-only, and within 7 business days of complete evidence you get a written answer: the conclusion, what supports it, what contradicts it, and who owns the next move.
Fixed fee, agreed in writing before I start. Or I spend a day or two with your team, on your own estate.
Why did network-related spend increase 34% month over month in the platform account?
- Supports
- Service and usage-type movement point to NAT Gateway data processing, not an across-the-board EC2 increase.
- Contradicts or missing
- Billing data alone does not show the source workload, the destination, or whether the transfer was expected.
- Next move
- Confirm the owning workload and inspect the traffic path before changing anything.
From the network cable to the CFO’s spreadsheet
I started out splicing fibre and racking switches. Then network engineering, migrations, and DDoS mitigation. Then nearly seven years inside AWS with national banks, telecoms, and other large estates: landing zones, incidents, architecture reviews, and, since 2019, the bill.
I can’t tell you the customer stories. I can tell you what tends to break.
Mission FinOps is just me, in Mission, BC, on Stó:lō land. You work with the person doing the work. No reseller margin, no partner quota, nothing to sell you but the answer.
Bring me the weird AWS problem.
Tell me what changed, what you’ve tried, and which decision is stuck. A few sentences is enough.
hello@missionfinops.com Please keep billing exports and credentials out of the first email.