Skip to Content
Cloud Engineering Academy
1. Cloud Computing & AWS Fundamentals

Well-Architected Framework introduction

Learn the six pillars and their design principles, use lenses including the Financial Services Industry Lens, and run a free review of your module-exercise workload in the AWS Well-Architected Tool.

beginner⏱ 1 h 30 min🟢 FreeCLF-C02SAA-C03

Assumes: .NET 10 LTS · AWS SDK for .NET v4 (AWSSDK.WellArchitected 4.1.1.1) · AWS CLI v2 · Region us-east-1 · Well-Architected Framework last updated 2026-11-16 · FSI Lens published 2026-01-27. Verified against official sources on 2026-11-17.

Learning objectives

By the end of this lesson you can:

  • Name the six pillars of the AWS Well-Architected Framework and explain each in one sentence.
  • Recall the main design principles of each pillar and the framework's general design principles.
  • Explain what a lens is, and what the Financial Services Industry (FSI) Lens adds for a bank.
  • Run a review in the free AWS Well-Architected Tool: define a workload, answer questions, read high and medium risks, save a milestone and delete the workload, from the console and the CLI.
  • Explain how a bank uses Well-Architected reviews as governance evidence, and why a review is not a compliance certificate.

Prerequisites

Why this matters in banking

Harbourline Bank's architecture review board meets every fortnight. Before Well-Architected, each reviewer brought their own checklist: the security architect asked about encryption, the operations lead about on-call, the finance partner about cost. Teams could not predict the questions, reviews took hours, and nothing was recorded in a form anyone could compare later. When the internal audit team asked "how do you know the statements service was designed for resilience?", the answer was a slide deck.

The Well-Architected Framework gives the board one shared vocabulary and one question set, the Well-Architected Tool records answers and risks with dates, and the Financial Services Industry Lens adds the questions a regulated firm should ask: risk roles, regulatory incident reporting, key management, resilience tiers. The result is not "compliant"; it is a consistent, repeatable, recorded architecture conversation that risk and audit colleagues can follow.

The idea in plain language

The AWS Well-Architected Framework is AWS's documented set of best practices for building systems in the cloud, organised into six areas called pillars. Each pillar has design principles, a list of questions, and best practices that answer them. You use it to check a design and to find risks before they become incidents.

A review is a conversation where the team that owns a workload answers the framework's questions honestly. Where a best practice is missing, the tool flags a high risk issue (HRI) or medium risk issue (MRI). The list of risks becomes an improvement plan. You save a milestone to record the state at a point in time, fix things, and review again.

AWS states that a review is a constructive conversation about architectural decisions, not an audit mechanism. That framing matters: if teams fear the review, they hide problems, and the review becomes useless.

Analogy: A structural survey of a building. The surveyor uses the same checklist for every building (foundations, roof, wiring, plumbing, fire safety, energy efficiency: six "pillars"). A lens is a specialist checklist added for a particular use: a hospital or a bank vault needs extra checks a house does not. The survey report lists defects by severity, and you commission work to fix them. A survey is not a building certificate; it tells you where you stand.

Key terms

TermMeaning
ComponentCode, configuration and AWS resources that together deliver one requirement; usually one team's unit of ownership
WorkloadA set of components that together deliver business value, such as "statement delivery"
PillarOne of six areas of architectural quality
LensAn extra set of questions and best practices for an industry or technology, applied on top of the framework
HRI / MRIHigh or medium risk issue: a missing best practice that AWS judges could significantly (or moderately) harm the business
Improvement planThe list of best practices to adopt, ordered by risk and by your pillar priorities
MilestoneA saved, read-only snapshot of a workload's answers and risks at a point in time

What problem the Framework and the Tool solve

NeedHow Well-Architected helpsLimitation
Consistent design reviewsSame questions for every workload, across teamsQuestions are generic; a lens or your own custom lens adds specifics
Finding risks earlyHRIs/MRIs and an improvement planOnly as good as the honesty of the answers; it does not inspect your resources
Tracking improvementMilestones show progress over timeSomeone has to schedule re-reviews
Industry contextLenses such as Financial Services, Serverless, Generative AILenses guide; they do not interpret regulation for you
Sharing with reviewersWorkloads can be shared with other accounts or across an organisationShared workloads may reveal architecture details; control access
Cost of the toolingNo additional charge for the AWS Well-Architected ToolYou pay only for resources you create while fixing things

The tool also supports custom lenses (your own questions, for example Harbourline's internal standards) and review templates (pre-filled answers for common patterns). Both are useful later; this lesson uses the official framework.

The six pillars

Names and one-line definitions, paraphrased from the framework's definitions page (checked 2026-11-17):

PillarIn one sentenceHarbourline question to ask
Operational ExcellenceRun and monitor workloads effectively, learn from operations, and keep improving processesCan on-call engineers see, from dashboards, whether statements are being delivered right now?
SecurityProtect data, systems and assets using cloud capabilitiesWho can read statement PDFs, how is that enforced, and how would we know if it changed?
ReliabilityThe workload performs its intended function correctly and consistently, and recovers from failureWhat happens to month-end statement generation if one AZ fails at 02:00?
Performance EfficiencyUse computing resources efficiently to meet requirements as demand and technology changeDoes generation still finish before 06:00 with twice the customers?
Cost OptimizationDeliver business value at the lowest price pointWhat does it cost to produce one statement, and who sees that number?
SustainabilityReduce the environmental impact of running the workload by maximising use of provisioned resources and minimising total resourcesDo we keep seven years of rendered PDFs when we could re-render from data?

Design principles per pillar

The principles below are summarised in plain words from the current framework, last updated 16 November 2026. AWS revises wording from time to time, and exam preparation material may use slightly older phrasing; the ideas are stable.

Operational Excellence

  • Build observability in, so telemetry drives decisions (measure business outcomes, not just CPU).
  • Automate safely: define the workload and its operations as code, with guardrails such as approvals and rate limits.
  • Make frequent, small, reversible changes.
  • Refine operational procedures often and keep teams familiar with them.
  • Anticipate failure: run failure scenarios and test the response.
  • Learn from every operational event, good or bad, and share the lessons.
  • Use managed services to reduce operational burden.

Security

  • Implement a strong identity foundation: least privilege, separation of duties, central identity, fewer long-term static credentials.
  • Maintain traceability: log, monitor and alert on actions and changes in real time.
  • Apply security at all layers (defence in depth): account guardrails, network edge, VPC, compute, OS, application, code.
  • Automate security best practices, defined as version-controlled code.
  • Protect data in transit and at rest, based on classification.
  • Keep people away from data: reduce direct and manual access.
  • Prepare for security events: incident processes, simulations and automation.

Reliability

  • Automatically recover from failure, triggered by business-level KPIs.
  • Test recovery procedures, not just normal operation.
  • Scale horizontally to remove single points of failure.
  • Stop guessing capacity: monitor and scale with demand (within quotas).
  • Manage change through automation.

Performance Efficiency

  • Use managed services to avoid running specialised technology yourself.
  • Deploy closer to customers, using Regions and edge locations.
  • Build scalable architectures, for example serverless.
  • Experiment more often with instance types, storage and configurations.
  • Consider "mechanical sympathy": choose technology that fits the data access pattern.
  • Design for change and variable demand: loosely coupled components, throttling, backoff with jitter, load shedding and circuit breakers.

Cost Optimization

  • Implement Cloud Financial Management as a practice, not a one-off project.
  • Adopt a consumption model: pay for what you use and switch off what you don't need.
  • Measure business outcomes relative to cost (for example cost per statement).
  • Use managed services and automation to reduce operational cost.
  • Allocate cost granularly (tags, accounts) so owners see what they spend.

Sustainability

  • Understand and measure your impact.
  • Set sustainability goals per workload (for example resources per transaction).
  • Maximise utilisation: right-size and remove idle resources.
  • Adopt new, more efficient hardware and software as it appears.
  • Match the computational approach to the problem's complexity: don't over-engineer.
  • Minimise the data you keep and process; give each data set an owner and an expiry date.

General design principles

Across all pillars, the framework lists six general principles, again in plain words:

  1. Stop guessing capacity needs: scale with demand instead of buying for a forecast.
  2. Test systems at production scale: create a full-size test environment on demand and delete it afterwards.
  3. Automate with experimentation in mind: automation makes it cheap to try, measure and roll back.
  4. Consider evolutionary architectures: design decisions are not one-off; let the system evolve.
  5. Drive architectures using data: measure how design choices behave and decide from the data.
  6. Improve through game days: rehearse failures and events regularly.

Lenses, including the Financial Services Industry Lens

A lens adds questions and best practices for a specific domain. The Lens Catalog in the Well-Architected Tool lists official lenses that need no installation. On 2026-11-17 it included, among others: Serverless Applications, Financial Services Industry, Generative AI, Data Analytics, Container Build, DevOps, Migration, SaaS, Machine Learning, Government and Healthcare Industry. The AWS Well-Architected Framework lens is applied to every workload by default.

Financial Services Industry Lens

The FSI Lens (publication date 27 January 2026) focuses the six pillars on financial institutions: security, data privacy and resiliency in line with the risk and control objectives you define, including those that help you align with supervisory requirements. It is written for risk, compliance and audit staff as well as engineers, and it is available as an official lens in the Tool's Lens Catalog.

Its four FSI design principles, in short:

FSI design principleWhat it means at Harbourline
Documented operational planningDefine the cloud operating model with clear roles across the three lines of defence: operational management (first line), risk and compliance functions (second line) and internal audit (third line)
Automated infrastructure and application deploymentPipelines and infrastructure as code so security and governance checks are embedded in every release
Security by designPre-approved, tested architecture patterns with encryption, baselines and audit capability turned on by default
Automated governanceAccount provisioning, budget enforcement and compliance checks run automatically rather than through runbooks and spreadsheets

The lens adds FSI-specific questions to each pillar. A few examples from its table of contents show the flavour:

  • Operational excellence: Have you defined risk management roles for the cloud? Have you assessed the workload against regulatory needs? How do you assess the business impact of a cloud provider service event?
  • Security: How do you accommodate separation of duties in IAM design? How are you managing your encryption keys? How are you protecting against ransomware? How are you meeting your obligations for incident reporting to regulators?
  • Reliability: How do business and regulatory requirements drive the resilience of your workload? Can you detect and recover from gray failures (partial, hard-to-see degradation)? How are backups retained?

It also includes scenario guidance for payments, open banking, cyber event recovery, financial data mesh, AI/ML, capital markets and insurance. Several later modules use these scenarios (Module 14 for payments and open banking, Module 12 for cyber event recovery).

Microsoft / Azure comparison

You know (Microsoft/Azure)AWS equivalentWhat's different
Azure Well-Architected Framework (five pillars: Reliability, Security, Cost Optimization, Operational Excellence, Performance Efficiency)AWS Well-Architected Framework (six pillars)AWS adds Sustainability as a pillar
Azure Well-Architected Review (assessment)AWS Well-Architected ToolThe AWS tool stores workloads, risks, milestones and improvement plans in your account, with an API and CLI
Azure workload-specific guidance (for example mission-critical, financial services)Lenses in the Lens Catalog, including the Financial Services Industry LensAWS lenses are answered inside the same tool alongside the core framework
Azure Advisor recommendationsAWS Trusted Advisor, AWS Config, Security Hub CSPM, Compute OptimizerThese inspect your actual resources; the Well-Architected Tool records your answers. Use both
Cloud Adoption FrameworkAWS Cloud Adoption Framework (AWS CAF)CAF is about organisational adoption; Well-Architected is about individual workloads

Architecture

The review lifecycle. You will walk through it with the CLI below.

Governance view at Harbourline. The review sits inside the bank's three lines of defence, not outside them:

Step-by-step implementation

You will review the module exercise workload: a .NET console app that, through an SSO role, creates a private, encrypted, tagged S3 bucket, uploads a fictional statement, lists and deletes it, plus a static status page served from private S3 through CloudFront. All steps are free.

Sign in and check the Region

aws sso login --profile learn-sandbox
aws sts get-caller-identity --profile learn-sandbox

The Well-Architected Tool stores workloads per Region. Use us-east-1 throughout so you can find the workload again.

Define the workload

Create it with the CLI (next section) or the console. Give it an environment of PREPRODUCTION, the Region us-east-1, a review owner and the default wellarchitected lens.

Answer at least three Security questions

Find the Security pillar's question IDs with list-answers, read each question's choices with get-answer, then record what the workload really does with update-answer. Be honest: the lab uses an administrator role, so least-privilege best practices are not met.

Read the risks and improvement plan

get-lens-review gives risk counts per pillar; list-lens-review-improvements lists the best practices to adopt. Optionally run the C# report in Complete code.

Save a milestone

A milestone freezes today's answers. In a bank, this is the artefact the risk team and auditors look at.

Optionally add the FSI Lens

Associate the Financial Services Industry Lens and skim its Security questions. Notice how they assume a regulated organisation.

Delete the workload

The workload costs nothing, but deleting it practises cleanup. Deleting also deletes its milestones and cannot be undone.

AWS Console instructions

  1. Sign in through the access portal to the sandbox account and select US East (N. Virginia).
  2. Console → search "Well-Architected" → AWS Well-Architected Tool → Define workload.
  3. Name hl-m01-hello-aws, Description "Module 1 exercise: .NET console app calling STS and S3 via SSO; static status page on private S3 + CloudFront", Review owner your name, Environment Pre-production, Regions AWS Regions → us-east-1. Choose Next.
  4. Skip the profile and review template steps (choose Next), keep AWS Well-Architected Framework as the lens and choose Define workload.
  5. Choose Start reviewing → AWS Well-Architected Framework, then select the Security pillar in the left panel. For each question, tick the best practices the workload follows, add a short note, and choose Save and exit when done.
  6. Open the workload's Overview or Improvement plan tab to see high and medium risks.
  7. Milestones → Save milestone, name it m01-baseline.
  8. Optional: Lenses (on the workload) → Edit → add Financial Services Industry Lens from the Lens Catalog.
  9. Cleanup: Workloads → select the workload → Delete, type the confirmation text and confirm.

Console labels can change; if a button name differs, look for the same step in the workload's Actions menu.

AWS CLI

# 1. Create the workload (returns WorkloadId and WorkloadArn).
aws wellarchitected create-workload \
  --workload-name "hl-m01-hello-aws" \
  --description "Module 1 exercise: .NET console app calling STS and S3 via SSO; static status page on private S3 + CloudFront" \
  --environment PREPRODUCTION \
  --aws-regions us-east-1 \
  --review-owner "alex.learner" \
  --lenses wellarchitected \
  --pillar-priorities security reliability operationalExcellence costOptimization performance sustainability \
  --tags Project=cea-lab,Lab=m01-hello-aws,Environment=learn,Owner=alex \
  --profile learn-sandbox --region us-east-1

# Save the id in a variable (PowerShell): $wid = "<WorkloadId from the output>"

# 2. List the Security pillar's questions with their ids and current risk.
aws wellarchitected list-answers --workload-id $wid --lens-alias wellarchitected --pillar-id security \
  --query "AnswerSummaries[].[QuestionId, QuestionTitle, Risk]" --output table \
  --profile learn-sandbox --region us-east-1

# 3. Read one question's choices (best practices) and their ids.
aws wellarchitected get-answer --workload-id $wid --lens-alias wellarchitected --question-id securely-operate \
  --query "Answer.Choices[].[ChoiceId, Title]" --output table \
  --profile learn-sandbox --region us-east-1

# 4. Record the answer: the choices the workload really follows, plus a note.
aws wellarchitected update-answer --workload-id $wid --lens-alias wellarchitected --question-id securely-operate \
  --selected-choices sec_securely_operate_multi_accounts sec_securely_operate_aws_account \
  --notes "Separate sandbox account in an Organization; root locked down (Module 0). No threat model yet." \
  --profile learn-sandbox --region us-east-1

# 5. Risk counts per pillar, and the improvement plan for Security.
aws wellarchitected get-lens-review --workload-id $wid --lens-alias wellarchitected \
  --query "LensReview.PillarReviewSummaries[].[PillarName, RiskCounts]" \
  --profile learn-sandbox --region us-east-1
aws wellarchitected list-lens-review-improvements --workload-id $wid --lens-alias wellarchitected --pillar-id security \
  --query "ImprovementSummaries[].[QuestionId, Risk, ImprovementPlanUrl]" --output table \
  --profile learn-sandbox --region us-east-1

# 6. Freeze the current state as a milestone.
aws wellarchitected create-milestone --workload-id $wid --milestone-name m01-baseline \
  --profile learn-sandbox --region us-east-1

# 7. Optional: find and add the Financial Services Industry Lens.
aws wellarchitected list-lenses --lens-type AWS_OFFICIAL \
  --query "LensSummaries[?contains(LensName, 'Financial')].[LensName, LensAlias, LensArn]" --output table \
  --profile learn-sandbox --region us-east-1
aws wellarchitected associate-lenses --workload-id $wid --lens-aliases "<LensAlias or LensArn from the previous output>" \
  --profile learn-sandbox --region us-east-1

# 8. Cleanup: deletes the workload and all its milestones (irreversible).
aws wellarchitected delete-workload --workload-id $wid --profile learn-sandbox --region us-east-1

Notes on each command:

  • create-workload requires --workload-name, --description, --environment (PRODUCTION or PREPRODUCTION) and --lenses. --pillar-priorities orders the improvement plan; Harbourline puts Security first. The pillar IDs other than security are shown as the author expects them (⚠ VERIFY by running get-lens-review and reading PillarId).
  • list-answers takes --pillar-id to filter to one pillar; the --query is a JMESPath expression that keeps only the id, title and risk.
  • The question ID securely-operate and the choice IDs sec_securely_operate_multi_accounts / sec_securely_operate_aws_account match the framework's SEC 1 best-practice pages (⚠ VERIFY against your own list-answers and get-answer output; always copy IDs from the output rather than from this page).
  • update-answer --selected-choices replaces the previously selected choices, so list every choice you want ticked each time.
  • create-milestone numbers milestones from 1; a workload can hold up to 100.
  • In PowerShell, replace \ line continuations with backticks or put each command on one line.

Infrastructure as Code

Well-Architected workloads are review records, not infrastructure, and this lesson found no CloudFormation resource type or Terraform resource for them (⚠ VERIFY). Teams automate reviews with the CLI (as above) or the SDK (below), and they put the fixes that come out of a review into their CDK or Terraform code. For example, the improvement "use least-privilege permission sets" for the module exercise becomes a change to the permission set definitions you met in Secure your AWS account.

Complete code

A read-only C# report that prints risk counts per pillar for one workload, useful for pasting into an architecture review board pack.

Harbourline.WellArchitected.Report.csproj
<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>net10.0</TargetFramework>
    <Nullable>enable</Nullable>
    <ImplicitUsings>enable</ImplicitUsings>
    <TreatWarningsAsErrors>true</TreatWarningsAsErrors>
    <RootNamespace>Harbourline.WellArchitected.Report</RootNamespace>
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="AWSSDK.WellArchitected" Version="4.1.1.1" />
    <!-- Needed at runtime so IAM Identity Center (SSO) profiles resolve. -->
    <PackageReference Include="AWSSDK.SSO" Version="4.1.0.2" />
    <PackageReference Include="AWSSDK.SSOOIDC" Version="4.1.0.2" />
  </ItemGroup>
</Project>
Program.cs
// Harbourline.WellArchitected.Report: prints risk counts per pillar for one Well-Architected Tool workload.
// Read-only. Usage: dotnet run -- <workload-id> [lens-alias]   (default lens: wellarchitected)
using Amazon.WellArchitected;
using Amazon.WellArchitected.Model;

if (args.Length is 0 or > 2)
{
    Console.Error.WriteLine("Usage: dotnet run -- <workload-id> [lens-alias]");
    return 2;
}

var workloadId = args[0];
var lensAlias = args.Length == 2 ? args[1] : "wellarchitected";

using var wa = new AmazonWellArchitectedClient(); // default credential chain + Region (AWS_PROFILE / AWS_REGION)

var workload = await wa.GetWorkloadAsync(new GetWorkloadRequest { WorkloadId = workloadId });
var review = await wa.GetLensReviewAsync(new GetLensReviewRequest { WorkloadId = workloadId, LensAlias = lensAlias });

Console.WriteLine($"Workload : {workload.Workload.WorkloadName} ({workload.Workload.Environment})");
Console.WriteLine($"Lens     : {review.LensReview.LensName}");
Console.WriteLine();
Console.WriteLine($"{"Pillar",-28} {"HIGH",5} {"MEDIUM",7} {"NONE",5} {"UNANSWERED",11}");

foreach (var pillar in review.LensReview.PillarReviewSummaries ?? [])
{
    var counts = pillar.RiskCounts ?? new Dictionary<string, int>();
    int Count(Risk risk) => counts.TryGetValue(risk.Value, out var n) ? n : 0;

    Console.WriteLine($"{pillar.PillarName,-28} {Count(Risk.HIGH),5} {Count(Risk.MEDIUM),7} {Count(Risk.NONE),5} {Count(Risk.UNANSWERED),11}");
}

return 0;

Run it while the workload still exists:

$env:AWS_PROFILE = "learn-sandbox"
$env:AWS_REGION = "us-east-1"
dotnet run -- $wid

Illustrative output after answering three Security questions (your numbers will differ):

Workload : hl-m01-hello-aws (PREPRODUCTION)
Lens     : AWS Well-Architected Framework

Pillar                        HIGH  MEDIUM  NONE  UNANSWERED
Operational Excellence           0       0     0          11
Security                         2       1     0           8
Reliability                      0       0     0          13
Performance Efficiency           0       0     0           5
Cost Optimization                0       0     0          11
Sustainability                   0       0     0           6

The code compiled cleanly with .NET 10 and the package versions shown on 2026-11-17 (warnings as errors). Question counts per pillar in the sample output are illustrative ⚠ VERIFY against your run.

Code explained line by line

  1. using Amazon.WellArchitected; using Amazon.WellArchitected.Model; import the client and request/response types from the AWSSDK.WellArchitected package.
  2. The argument check accepts a workload ID and an optional lens alias; exit code 2 means wrong usage.
  3. lensAlias defaults to wellarchitected, the alias of the core framework lens. Pass the FSI Lens alias or ARN to report on that lens instead.
  4. new AmazonWellArchitectedClient() uses the default credential chain and Region. Setting AWS_PROFILE and AWS_REGION selects your SSO profile and us-east-1.
  5. GetWorkloadAsync returns the workload's properties; the code prints its name and environment so the report is self-describing.
  6. GetLensReviewAsync returns the lens review, including one summary per pillar.
  7. PillarReviewSummaries ?? [] — in SDK v4, collections in responses can be null when empty, so the code defaults to an empty collection expression.
  8. RiskCounts is a dictionary from risk name (HIGH, MEDIUM, NONE, UNANSWERED, NOT_APPLICABLE) to a count.
  9. Risk is an SDK constant class; Risk.HIGH.Value is the string "HIGH" used as the dictionary key. Using the constants avoids typos.
  10. The local function Count returns zero for missing keys, because the API omits risks that have no questions.
  11. The Console.WriteLine with -28, 5, 7 format widths prints aligned columns for a board pack.

Security considerations

  • Review notes are sensitive. Answers and notes describe weaknesses in your architecture. Never put credentials, customer data or exploit detail in notes. Treat workloads as confidential and share them only with named reviewer accounts.
  • Least privilege for reviewers. Reviewers and auditors need read-only access (for example the AWS managed policy WellArchitectedConsoleReadOnlyAccess); only workload owners need write access. Deleting a workload deletes its milestones, so restrict wellarchitected:DeleteWorkload.
  • Answers are not evidence of configuration. The Tool records what people say. Pair important answers with machine evidence: AWS Config rules, Security Hub CSPM controls, the C# checker from the Shared Responsibility lesson.
  • Not a compliance attestation. A clean review means the team believes it follows AWS best practices. It does not show that the workload meets UK GDPR, PCI DSS, PRA or DORA requirements; those need your bank's control framework, testing and sign-off.

⚠ Learning shortcut — not for production

In this lesson you create, answer, approve and delete your own review, in the sandbox account, with an administrator role. At Harbourline, workloads live in the workload's own account (or a central governance account), are shared read-only with the architecture review board and the technology risk team, milestones are never deleted (they are evidence), and risk acceptances are approved by someone other than the workload owner.

Banking use case

Harbourline Bank (fictional) embeds Well-Architected in its delivery process:

  • Gate reviews. Every new customer-facing workload completes a Well-Architected review with the Framework and the FSI Lens before the "build" gate and again before "go-live". The workload owner presents the improvement plan; the board approves it or asks for changes.
  • Pillar priorities. Security and Reliability are always the first two priorities, so their risks top the improvement plan.
  • HRIs need decisions. Every HRI is either fixed before go-live, or formally accepted by the business owner with a date for remediation, recorded in the bank's risk system, with technology risk (second line) challenging the acceptance.
  • Milestones as evidence. Milestones are saved at each gate and retained. Internal audit (third line) samples them and checks that the claimed fixes exist in code and in AWS Config evidence.
  • Custom lens. Harbourline adds a custom lens with its own standards (for example "all statement data uses SSE-KMS with a customer managed key", "card data never leaves the PCI account"), so bank-specific rules are asked in the same tool.
  • Re-reviews. Production workloads are re-reviewed annually and after major changes, because the AWS framework itself changes (the version used here was last updated on 16 November 2026).

None of this makes a workload compliant on its own. It produces a consistent record of architecture decisions and risks that compliance, risk and audit colleagues can rely on as one input to their assessments.

Common mistakes

  • Treating the review as an exam to pass. → Teams tick boxes to look good → the risk list is fiction. Make honesty safe: risks found in review are cheaper than risks found in production.
  • Reviewing once. → The review is done for go-live → architecture and the framework drift. Schedule re-reviews and save milestones.
  • Ignoring the lens catalog. → Only the core framework is used → industry-specific risks such as regulatory incident reporting or gray failures are never asked. Add the FSI Lens for banking workloads.
  • Answering for the ideal design. → People describe the target state → the improvement plan is empty. Answer for what is deployed today.
  • Treating the Tool as monitoring. → "The Tool will tell us if encryption is off" → it does not inspect resources. Use AWS Config, Security Hub CSPM and Trusted Advisor for that.
  • Deleting workloads to clear risks. → A fresh workload looks clean → you lose the evidence trail. Keep workloads and milestones; mark risks as fixed by updating answers.

Troubleshooting

SymptomLikely causeFix
ValidationException on create-workloadMissing required parameter (--description, --environment, --lenses) or a value out of rangeCheck the four required options; --environment must be PRODUCTION or PREPRODUCTION
ResourceNotFoundException for the workloadDifferent Region from where it was createdAdd --region us-east-1 (workloads are Regional)
ValidationException on update-answerChoice ID or question ID copied from another lens or an older framework versionCopy IDs from list-answers / get-answer for this workload and lens
Previously ticked choices disappeared--selected-choices replaces the whole selectionPass every choice you want selected each time
AccessDeniedExceptionYour permission set lacks wellarchitected:* actionsUse SandboxAdmin; in a bank, request the reviewer or owner role
FSI Lens not in list-lenses outputFilter or name mismatchRun list-lenses --lens-type AWS_OFFICIAL without the --query and search the output
C# report prints all zerosWrong lens alias, or nothing answered yetCheck LensAlias with list-lens-reviews; answer at least one question

Cost and cleanup

Cost: $0. There is no additional charge for the AWS Well-Architected Tool; you pay only for AWS resources you create, and this lesson creates none.

Cleanup:

# Delete the practice workload (and its milestones). Irreversible.
aws wellarchitected delete-workload --workload-id $wid --profile learn-sandbox --region us-east-1

# Confirm no workloads with this name remain.
aws wellarchitected list-workloads --workload-name-prefix hl-m01 --profile learn-sandbox --region us-east-1 --query "WorkloadSummaries[].WorkloadName"

# Confirm nothing else tagged for the module exercise remains.
aws resourcegroupstaggingapi get-resources --tag-filters Key=Lab,Values=m01-hello-aws --profile learn-sandbox --query "ResourceTagMappingList[].ResourceARN"

Exercises

  • 🟢 Guided: Create the hl-m01-hello-aws workload with the CLI, answer three Security questions honestly (identity, data at rest, incident preparation), read the improvement plan, save a milestone, then delete the workload.
  • 🟡 Challenge: Add the Financial Services Industry Lens to the workload. Pick two FSI Security questions that the core framework does not ask and write, for each, what Harbourline would need in place (people, process and technology) to answer "yes".
  • 🔴 Live problem: A product owner emails: "The Well-Architected review for the card-statement service shows zero high risks, so we are PCI DSS compliant and can go live Friday." You notice that most questions are unanswered and that the workload was created yesterday. Write your reply.

Assignment

Add docs/well-architected-m01.md to your learning-journal repository: the workload description, your pillar priorities and why, the answers you gave to three Security questions (with notes), the resulting risks, and a three-item improvement plan with an owner and target date for each. Include the C# report output.

Solutions

Knowledge check

Interview questions

  • "How have you used the Well-Architected Framework?" — Describe a review: defining the workload, applying the Framework and a relevant lens, answering honestly with the team, prioritising Security and Reliability, turning HRIs into backlog items with owners, saving milestones and re-reviewing after changes.
  • "Which pillar matters most for a bank?" — All six, but trade-offs are explicit: Security and Reliability usually take priority; Cost Optimization shapes how you meet them; Operational Excellence makes them sustainable. Name a trade-off, such as multi-Region resilience versus cost and data-residency complexity.
  • "What does the Financial Services Industry Lens add?" — Governance and risk roles (three lines of defence), regulatory assessment of workloads, separation of duties, key management, ransomware protection, regulatory incident reporting, resilience tiers driven by business and regulatory requirements, gray-failure detection and backup retention, plus scenarios such as payments and open banking.
  • "How do you stop a Well-Architected review becoming a box-ticking exercise?" — Make it blameless, answer for today's state, back key answers with automated evidence (Config, Security Hub CSPM), track HRIs to closure, and re-review on a schedule.

Certification practice

Completion checklist

  • I can name the six pillars and one design principle of each
  • I can list the six general design principles
  • I can explain what the FSI Lens adds and name its four design principles
  • I created a workload, answered Security questions, saved a milestone and read the improvement plan
  • I deleted the practice workload and confirmed with list-workloads
  • I can explain why a review is not a compliance attestation

Key takeaways

  • Six pillars: Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimization, Sustainability.
  • A review is a blameless conversation that produces risks, an improvement plan and dated milestones, not an audit or a certificate.
  • Lenses add domain questions; the Financial Services Industry Lens brings governance, regulatory and resilience questions for banks.
  • The Well-Architected Tool is free and scriptable from the CLI and C#.
  • Back important answers with automated evidence, and re-review as the workload and the framework change.

Further reading

Independent learning resource — not affiliated with, endorsed or sponsored by Amazon Web Services. AWS and related marks are trademarks of Amazon.com, Inc. or its affiliates. All banking data in examples is fictional. Sample architectures are for learning and are not automatically compliant with GDPR, PCI DSS or any banking regulation.

On this page