AWS gets weird at scale.
I’m Yuvdeep. I spent nearly seven years inside AWS as a Senior TAM and Solutions Architect. Now I’m an independent AWS consultant, helping your team investigate and resolve difficult problems.
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
I work across architecture, infrastructure, networking, migration, governance, operations, and cloud economics. FinOps is a specialty, not the boundary.
How it works
Start with the problem your team needs to solve. A bounded AWS investigation can deliver a written answer in seven business days, subject to agreed scope and available evidence: the conclusion, what supports it, what contradicts it, and the next move.
Larger architecture, migration, governance, advisory, and implementation projects are scoped independently. I agree the work, deliverables, timeline, and fee with you in writing before starting.
Investigations favor read-only access and evidence you control. If implementation is needed, we separately agree access, responsibilities, and risk boundaries before changes begin. How I handle access and data.
I can work alongside your engineering team or an existing consultancy, with named co-delivery and clear responsibilities.
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, no software sale behind my advice.
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.