A migration, a scale limit or an outage put the architecture in question. We review it and write down the decisions.
You are about to commit budget to a migration, a re-platform or a scale-out, and nobody can say in writing why the current design fails.
A decision record set and a phased plan. One page per decision: the option chosen, the options rejected, the trade-off.
Yes, in writing, when the current design is fine. That answer is cheaper than the migration.
We run the six-pillar review as part of an AWS-hosted review. We are not an AWS partner and there is no partner funding attached.
Two to four weeks for most estates. Elapsed time depends on access and how many teams own the workloads.
Read-only access to the accounts in scope, the repositories holding infrastructure as code, and time with the engineers who run it.
A design question rarely arrives alone. If the concern is whether the design is safe rather than whether it will hold, a cloud security review answers that instead, and our cloud security review vs penetration test guide explains when offensive testing is required. A cloud cost review covers the case where the bill moved and nobody can explain why. Platform specifics are on the AWS consulting, Azure consulting and Google Cloud consulting pages.
Send the accounts in scope and what prompted the question. We will confirm scope and fee first.
Last reviewed: