AWS Architecture Review & Roadmap
If your AWS footprint has grown faster than your documentation, or you're about to make a big decision, a migration, a new region, a disaster-recovery plan, and want a second set of eyes first, this review is built for that. I work with growing teams in Canada and the US to assess their AWS architecture against the AWS Well-Architected Framework, flag risk before it becomes an incident, and turn scattered tribal knowledge into a roadmap the whole team can work from.
What's included
- A structured AWS Well-Architected review across reliability, security, cost, performance, and operations
- Migration planning for moving workloads, regions, or accounts
- A long-term infrastructure roadmap aligned to your actual growth plans, not generic best practices
- Clear, written documentation your team can reference after the engagement ends
Proof it works
- Led business continuity and disaster recovery (BCDR) implementation across two AWS regions, Canada and the US.
Is this right for you?
This review is a fit if your AWS footprint has grown faster than your documentation, or you're facing a decision — a migration, a new region, a disaster-recovery plan — and want a structured, outside assessment before committing. It's also useful if nobody on the team has formally checked the architecture against AWS's own Well-Architected Framework and you want to know where the real risk sits, not just a generic best-practices checklist. The engagement is fixed-price and scoped after a free 30-minute call covering your current architecture and what decision or concern is driving the review. It's not a fit if you need code written or infrastructure migrated — this is an assessment and roadmap, not implementation work (though it pairs well with the Terraform or Containers & Serverless engagements if implementation follows). You keep the full written review and roadmap afterward, with no dependency on me to interpret or act on it. I respond within 24 hours and work with teams in Canada and the US.
FAQ
Does this review result in actual changes being made, or just a report?
The deliverable is the review and roadmap itself — a written assessment and prioritized plan you can act on with your own team, or bring to a separate implementation engagement.
How long does a typical architecture review take?
Typically a couple of days to a couple of weeks, depending on scope, complexity, and how quickly we get access and get oriented in your environment — the scoping call narrows this down before work starts.
Do you need admin access to our AWS account to do this?
No — I never need write or delete access. The specific read-only permissions depend on which services and architecture are in scope for the review, and that's confirmed on the scoping call.
How it works
Simple, low-friction engagement. No lengthy contracts or discovery phases.
Tell me what you need
Fill out the contact form with a brief description of your challenge. I'll respond within 24 hours.
Quick scoping call
We jump on a 30-minute call to understand your environment, goals, and timeline. I'll follow up with a clear scope and fixed price — usually within a couple of days, up to a week for more complex asks.
I get to work
Hands-on delivery with regular updates. You get clean documentation and knowledge transfer — not a black box.
Done — and you own it
Everything I build is yours. I document it thoroughly so your team can maintain and extend it independently.
Ready to talk about architecture review?
Tell me a bit about your challenge and I'll get back to you within 24 hours.
Get in touch →