Independent AWS consulting
I spent nearly seven years at AWS as a Senior Technical Account Manager and Senior Solutions Architect, mostly with banks and telecoms. Now I work on my own, helping teams with the AWS problems they’re stuck on.
Prefer to talk? Book a 20-minute call.
Kulshan (Mt Baker), from the Fraser Valley
What I help with
AWS bills
The bill went up and nobody can say why. I go through the billing data and the accounts behind it until there’s an answer you can check for yourself.
Landing zones and governance
Accounts, OUs, guardrails and access that grew without a plan. I help you work out what you actually have, and what to change first.
Networking and migrations
I started in networking, so VPC design, data transfer costs and migrations that got messier than planned are familiar ground.
Also architecture reviews, operations, and anything where AWS, cost and several teams have got tangled together.
How it works
- You email me. A few sentences is enough: what changed, what you’ve tried, and what decision is waiting on it.
- We talk for 20 minutes. If I can help, I send a written scope with the work, the deliverable, the timeline and the fee. Nothing starts until you’ve agreed to it.
- I do the work and write it up. A focused investigation usually takes about seven business days, depending on scope and the data available. You get the answer, the evidence behind it, anything that doesn’t fit, and what to do next.
Where I can, I work with read-only access, and you stay in control of your data. How I handle access and data.
I’m happy to work alongside your own engineers or another consultancy. If you’re an advisor with a client problem outside your lane, introductions are welcome.
Why did network spend go up 34% month over month in the platform account?
- Supports
- The movement is in NAT Gateway data processing, not a general EC2 increase.
- Doesn’t fit, or missing
- Billing data alone doesn’t show which workload sent the traffic, where it went, or whether it was expected.
- Next step
- Confirm the owning workload and look at the traffic path before changing anything.
About me
I started out splicing fibre and racking switches, then moved into network engineering, migrations and DDoS mitigation.
After that I spent nearly seven years at AWS as a Senior TAM and Senior Solutions Architect, working with national banks, telecoms and other large customers on landing zones, incidents and architecture reviews. From 2019 on, a lot of that work was about the bill.
Mission FinOps is just me, working from Mission, BC, on Stó:lō land. You deal with me directly. I don’t resell AWS, take partner commissions or sell software, so none of that sits behind my advice.
Client work is confidential, so you won’t find client names or case studies here.
Get in touch
Email hello@missionfinops.com with a few sentences: what changed, what you’ve tried, and which decision is stuck.
Prefer to talk? Book a 20-minute call.
Please don’t send billing exports, logs or credentials in the first email. I’ll reply first and we’ll agree how to share data.