Services // AWS Architecture Consulting
Get the architecture right before it's expensive to change.
I work as an AWS architecture consultant out of Delhi NCR, focused on the design decisions that are cheap to fix on a whiteboard and brutal to fix six months into production service boundaries, failure domains, data ownership, what actually needs to scale versus what just feels like it should.
This is design and review work, not day-to-day operations. If you need help running what's already built, that's a separate conversation this page is about getting the shape of the system right in the first place.
Start with a review →What this actually covers
Design and review work, not day-to-day operations
AWS Well-Architected Reviews
A structured walk-through of your account against the actual Well-Architected pillars not a checkbox exercise. You get a document ranking issues by what will actually hurt you first, not a 40-page PDF nobody opens twice.
Greenfield System Design
Building something new and want the architecture right before the first line of infrastructure code gets written. I'll draw it, argue with you about the tradeoffs, and hand over a design doc your engineers can build from.
Second Opinion / Pre-Launch Review
Someone else designed it an agency, an in-house team, a previous hire and you want an outside set of eyes before launch. I'll tell you what's genuinely fine and what isn't, even if that's an uncomfortable conversation.
Architecture Documentation
Diagrams and decision records that explain why the system is shaped the way it is, not just what services it uses. Useful when you're raising funding, going through a security review, or just tired of tribal knowledge living in one engineer's head.
How people usually bring me in
Three shapes, scoped after a call not off a rate card
Architecture Review
One to two weeks. I go through what exists, flag the risks, and give you a prioritized list. No changes get made without your sign-off this is diagnosis, not surgery.
New System Architecture
For a new product, a new service, or a rebuild. Diagrams, decision records, and enough detail that your team isn't guessing at implementation.
Ongoing Architecture Advisory
A standing arrangement where I review design decisions before they're built, not after. Works well for teams shipping fast who want a second opinion without slowing down.
How a review or design engagement runs
Four steps, nothing hidden
Share what exists (or what you're planning)
An existing account, a Figma-level idea, or a half-finished design doc any of these is a fine starting point.
I ask the annoying questions
Expected traffic, compliance requirements, team size, what happens if this component goes down at 3 AM. Architecture decisions live or die on these answers.
You get a design, not a slide deck
Diagrams, service choices, and written reasoning for each major decision including the ones I talked you out of.
Review before you build it
One follow-up pass once your team starts implementation, to catch drift between the design and what's actually getting built.
Questions people actually ask
Before the discovery call
What's the difference between architecture consulting and cloud consulting?
Architecture consulting is about the design which services, how they connect, what happens under failure, and why. Cloud consulting (the broader work I also do) covers running that architecture day to day: deployments, cost, ongoing operations. A lot of clients start with an architecture review and only bring me into the operational side later, once the design itself is solid.
Do you do AWS Well-Architected Framework reviews specifically?
Yes that's one of the more common ways people start. It's structured enough to be useful even for a first engagement where we haven't worked together before, and it usually surfaces two or three things worth fixing regardless of how confident the team was going in.
I already have an architecture. Can you just review it before I build it?
That's exactly what the pre-launch review is for. Bring the design as-is a doc, a diagram, even a rough Terraform repo and I'll tell you what I'd change and why, before it's expensive to change.
How long does an architecture review actually take?
Most reviews run one to two weeks depending on how big the system is and how much documentation already exists. I'd rather scope it properly on a call than give you a generic number that's wrong for your case.
Do you provide architecture diagrams as a deliverable?
Yes, along with written decision records explaining the reasoning useful for onboarding new engineers, security audits, or investor due diligence, not just for me to reference during the build.
Can you review an architecture another consultant or agency built?
Regularly. I'm not going to pretend everything another team did was wrong just to justify the engagement I'll tell you plainly what's solid and what genuinely needs to change.
Whiteboard it before you build it.
Bring what you have a rough idea, a half-built diagram, or a system already in production. Fifteen minutes is usually enough to know if a review makes sense.
Get in touch →