Skip to content

SolutionsWell-Architected

Your AWS architecture, reviewed in 48 hours.

Read-only access, a review against the six pillars of the AWS Well-Architected Framework, and a prioritised plan your team can act on. Nothing in your environment changes.

Well-Architected review

Definition

What is a Well-Architected Review?

A check of your AWS workloads against the AWS Well-Architected Framework, AWS's own best practice across six pillars. Ours runs in 48 hours with read-only access and ends with findings ranked by risk and a plan for what to fix first.

The 48 hours

Bounded, read-only, done in 48 hours.

A fixed scope and a fixed clock. You create one read-only role; we collect, analyse and walk your team through what we found.

  1. Hour 0

    Access.

    You create one read-only IAM role.

  2. Day 1

    Collect.

    Configuration evidence, gathered through AWS APIs.

  3. Day 2

    Analyse.

    Six pillars reviewed, every finding ranked by risk.

  4. Hour 48

    Report.

    A walkthrough of the findings and the plan.

Access and findings

We read. We never write.

Access model

Two AWS managed policies.

One IAM role with SecurityAudit and ViewOnlyAccess. Review it before you create it, and delete it when we finish.

aws iam list-attached-role-policies --role-name wa-reviewarn:aws:iam::aws:policy/SecurityAuditarn:aws:iam::aws:policy/job-function/ViewOnlyAccess# what the role can doPASSRead configuration: IAM, network, storage, loggingPASSNo permission to create, change or delete
Example finding

Every finding ranked, with its fix.

Each finding names the pillar, the resource and the risk, with the fix. The plan starts with what matters most.

Example · Security pillarIAM.6

Severity: critical

Hardware MFA not enabled for the root user

ResourceAccount 1111-2222-3333 · root

  1. Day 1Collected from the account settings
  2. Day 2Ranked first in the Security pillar
  3. Day 2Fix and owner agreed in the walkthrough

OpenFirst item on the remediation plan.

What you receive

Three outputs, one walkthrough.

An executive summary for leadership, a technical report by pillar for engineers, and a remediation plan ranked by risk.

Review summary · 3 accounts · eu-west-1Illustrative data

Findings

35

Critical and high

9

Findings by severity

  • critical2
  • high7
  • medium15
  • low11

Total 35 findings.

Findings by pillar

  • Security12
  • Reliability8
  • Cost Optimization6
  • Operational Excellence5
  • Performance Efficiency3
  • Sustainability1

Top of the remediation plan

  • IAM.6Hardware MFA for the root usercriticalOpen
  • S3.8Block public access on two bucketshighOpen
  • RDS.5Multi-AZ for the orders databasehighOpen
Illustrative numbers, not a client result.

Credentials

Reviewed by AWS-certified engineers.

AWS Services Partner
Advanced Tier
AWS service deliveries
8
AWS certifications
25+
AWS certified
Every engineer

FAQ

Common questions.

One IAM role with the AWS managed policies SecurityAudit and ViewOnlyAccess. Both are read-only: they let us see how your accounts are configured, not change them.

No. The role cannot create, modify or delete resources, and you can remove it as soon as the review ends.

An executive summary, a technical report organised by the six pillars, and a remediation plan ranked by risk. We walk your team through all three.

The tool is a questionnaire your team answers. We gather the evidence from your accounts, review it as engineers and tell you what to fix first.

The plan is yours to run. If you want help with the fixes, we can work through them with your team.

Next step

Know where your architecture stands.

48 hours, read-only access, and a plan your team can act on.