Skip to content
Nubent

/Architecture review

AWS Well-Architected Review with a remediation plan

We review your AWS workloads against the six pillars of the AWS Well-Architected Framework, add specialized lenses such as Generative AI and SaaS where they apply, and hand you a prioritized remediation plan. Then, if you want, we carry it out through Terraform pull requests, starting with the high risks.

/Diagnosis

Signs it is time

A funding round or due diligence

Investors, enterprise customers or a potential acquirer are about to review your platform, and you need an objective assessment of where it stands.

You are launching a generative AI product

You are taking an Amazon Bedrock workload to production and want to validate security, cost, resilience and governance before opening it to customers.

You grew without revisiting the architecture

The platform was built fast to validate the product, and now you do not know which high-impact security or availability risks it carries.

Findings with no plan

You already have Security Hub alerts, Trusted Advisor checks or a previous audit, but nobody has prioritized them or turned them into actionable work.

/What we deliver

Concrete deliverables, in your repository

  • Review in the Well-Architected Tool

    Your workload registered in the AWS Well-Architected Tool in your own account, with the questions for all six pillars answered and risks classified.

  • Specialized lenses

    An additional assessment with the Generative AI Lens, SaaS Lens, Serverless Lens or others, depending on the type of workload.

  • Findings report

    High and medium risks with technical evidence, business impact and a concrete recommendation, written for both leadership and engineering.

  • Prioritized remediation plan

    A backlog ranked by risk, effort and impact, with quick wins, structural changes and an estimate for each item.

  • Optional execution

    Remediation delivered through Terraform pull requests, with review milestones and status updates in the tool.

/How we work

Our process

  1. Scope and access

    We choose the workloads to review and the lenses that apply, and access your accounts through a read-only role.

  2. Technical analysis and interviews

    We combine a review of configuration, IaC and services like Security Hub and Trusted Advisor with working sessions with your team.

  3. Report and plan

    We present the findings, agree on priorities with technical leadership and leave the remediation plan ready to execute.

  4. Remediation and re-review

    We implement the agreed changes, record milestones in the Well-Architected Tool and measure how much risk was reduced.

What the AWS Well-Architected Framework is

The AWS Well-Architected Framework is the set of best practices AWS publishes for designing and running workloads in the cloud. It is organized into six pillars: operational excellence, security, reliability, performance efficiency, cost optimization and sustainability. Each pillar has specific questions and practices against which a workload is assessed.

A Well-Architected Review applies that framework to your real system. It is less a compliance audit than a structured technical conversation that identifies high and medium risks and translates them into improvements. Its value depends on how deeply the evidence is examined, and on the outcome ending up as implemented changes.

The 6 pillars applied to your workload

For security we review identities, permissions, data protection, detection and response. For reliability, quotas, multi-AZ redundancy, backups, disaster recovery and failure handling. For operational excellence, deployments, observability and incident management. For performance efficiency, the choice of compute, storage and databases for your usage pattern.

For cost optimization we look at idle resources, commitments such as Savings Plans, architecture and spend visibility. For sustainability, resource utilization, use of Graviton and removal of unnecessary workloads. Every finding is documented with evidence and a concrete recommendation, rather than a generic pointer to the documentation.

  • Operational excellence
  • Security
  • Reliability
  • Performance efficiency
  • Cost optimization
  • Sustainability

The Generative AI and SaaS lenses

AWS complements the general framework with lenses for specific workload types. The Generative AI Lens addresses questions unique to systems built on foundation models: model selection, prompt engineering and RAG, quality evaluation, protection against prompt injection, data privacy, inference cost and operating workloads on Amazon Bedrock or SageMaker AI.

The SaaS Lens focuses on multi-tenant architectures: isolation between customers, tenant identity and context, automated onboarding, per-tenant metrics and costs, and deployment strategies that do not hit every customer at once. We also apply the Serverless Lens, Container Build Lens or others when the workload calls for it.

From report to an executed remediation plan

The most common failure of an architecture review is ending in a long document nobody acts on. Our main deliverable is a backlog prioritized by risk, effort and impact, with concrete tasks your team or ours can pick up the next day. We separate high-value quick wins from structural changes that need planning.

If you decide to have us carry out the remediation, we work through Terraform pull requests, record milestones in the AWS Well-Architected Tool and repeat the review at the end to measure how many high risks were resolved. That way the improvement is documented and can be verified by third parties.

/FAQ

Well-Architected Review: frequently asked questions

Another question? Write to hello@nubent.com and an engineer will answer.

What is an AWS Well-Architected Review?

It is a structured assessment of an AWS workload against the best practices of the AWS Well-Architected Framework. It walks through the six pillars, identifies high and medium risks with evidence and ends in prioritized recommendations. It is recorded in the AWS Well-Architected Tool, available at no additional cost in the AWS console.

What are the 6 pillars of AWS Well-Architected?

Operational excellence, security, reliability, performance efficiency, cost optimization and sustainability. Each pillar groups design principles and specific questions. A full review covers all of them, though it is common to go deeper on the ones that pose the greatest business risk at the time, such as security or reliability.

How long does a Well-Architected Review take?

It depends on how many workloads are in scope, how complex they are and which lenses are included. We agree on the scope and the calendar before starting, covering technical analysis, team sessions and the report. Any follow-up remediation is planned separately based on the number of findings and their priority.

What is the AWS Generative AI Lens?

It is an extension of the AWS Well-Architected Framework with best practices for workloads that use foundation models and generative AI. It covers model selection and customization, RAG, evaluation, security against AI-specific risks, privacy, cost and operations. It is especially useful before taking an Amazon Bedrock application to production.

Does a Well-Architected Review replace a security or compliance audit?

No. The review assesses architecture best practices across six dimensions and identifies risks, but it does not certify compliance with standards such as SOC 2, ISO 27001 or PCI DSS. It is, however, an excellent starting point, because many of its security and reliability findings overlap with controls those standards require.

Next step

Let's talk about your Well-Architected Review project

30 minutes with an engineer. Concrete next steps, whether or not you work with us.