The Well-Architected Framework is AWS's set of design principles, best practices, and review questions for evaluating architectures. It is not a certification or a checklist to pass: it is a structured way to find risks in a workload, make trade-offs explicit, and prioritise improvements.
The six pillars
| Pillar | Core question |
|---|---|
| Operational Excellence | Can we run, observe, and continuously improve this workload? |
| Security | Are data, systems, and assets protected, and can we detect and respond to events? |
| Reliability | Does it recover from failure and meet demand without disruption? |
| Performance Efficiency | Are we using the right resources efficiently as demand and technology change? |
| Cost Optimization | Are we delivering business value at the lowest price point? |
| Sustainability | Are we minimising the environmental impact of running the workload? |
General design principles
- Stop guessing capacity needs: scale on measured demand
- Test systems at production scale, then tear them down
- Automate to make architectural experimentation cheap
- Allow evolutionary architectures: design for change
- Drive architectures using data (metrics, load tests, game days)
- Improve through game days: simulate events and learn
Shared responsibility
The ability to support development, run workloads effectively, gain insight into their operation, and continuously improve supporting processes and procedures.
Design principles
- Perform operations as code (IaC for infrastructure, runbooks, and procedures)
- Make frequent, small, reversible changes
- Refine operations procedures frequently
- Anticipate failure (pre-mortems, game days)
- Learn from all operational failures and share what you learn
Best-practice areas
| Area | What it covers |
|---|---|
| Organization | Shared ownership, clear priorities, team roles, risk tolerance |
| Prepare | Telemetry design, IaC, CI/CD, readiness checks, runbooks |
| Operate | Workload health, KPIs, alerting, event response, dashboards |
| Evolve | Post-incident analysis, feedback loops, continuous improvement |
Key services
| Service | Role |
|---|---|
| CloudFormation / CDK / Terraform | Infrastructure as code, repeatable environments |
| CodePipeline / CodeDeploy | CI/CD with blue/green, canary, and automatic rollback |
| CloudWatch | Metrics, logs, alarms, dashboards, composite alarms |
| X-Ray / CloudWatch Application Signals | Distributed tracing and service-level objectives |
| Systems Manager | Runbook automation, patching, Parameter Store, Session Manager |
| EventBridge | Event-driven remediation and automation |
Example: alarm on user-facing symptoms, not just causes
# Alarm on ALB 5xx rate, notify an SNS topic
aws cloudwatch put-metric-alarm \
--alarm-name checkout-alb-5xx \
--namespace AWS/ApplicationELB \
--metric-name HTTPCode_Target_5XX_Count \
--dimensions Name=LoadBalancer,Value=app/checkout/50dc6c495c0c9188 \
--statistic Sum --period 60 --evaluation-periods 3 \
--threshold 20 --comparison-operator GreaterThanThreshold \
--treat-missing-data notBreaching \
--alarm-actions arn:aws:sns:us-east-1:111122223333:oncall
Operating areas in detail
| Area | Topics | Summary |
|---|---|---|
| Organization | Organization priorities · Operating model · Organizational culture | Teams share an understanding of the workload and business goals. Evaluate internal and external customer needs, governance and compliance obligations, and keep a risk registry. Every workload, process and procedure has a named owner; define team responsibilities and agreements, and provide mechanisms to request changes and exceptions. Leadership sponsors best practices; encourage experimentation, learning time, and diverse perspectives. Review priorities regularly. Control Tower and Organizations support centralised governance. |
| Prepare | Implement observability · Design for operations · Mitigate deployment risks · Operational readiness and change management | Design workloads to emit metrics, logs, events and traces, tied to KPIs that matter to the business. Treat the whole stack as code (CloudFormation), use consistent tagging, and run pre-mortems. Prefer frequent, small, reversible changes with fast feedback and a rollback plan. Use operational readiness reviews with checklists, runbooks (routine tasks) and playbooks (issue resolution) before go-live. |
| Operate | Utilizing workload observability · Understanding operational health · Responding to events | Set baselines and alert thresholds, and watch for deviations. Define expected outcomes and metrics for both the workload and the operations activities around it (deployments, incident response). Every alert has an owner and a process; prioritise by customer and business impact, define escalation paths, and automate scripted responses to well-understood events. Dashboards are tailored to audience: customer, business, developers, operations. |
| Evolve | Learn, share, and improve | Dedicate time to continuous small improvements. Run post-incident analysis on every customer-impacting event, identify contributing factors and preventive actions, and share lessons across teams. Log analytics on S3 with Glue and Athena can reveal trends. Provide safe sandbox, dev, test and production environments with increasing operational control. |
Best practices by topic
| Topic | Best practices |
|---|---|
| Organization priorities (OPS01) | BP01 Evaluate external customer needs · BP02 Evaluate internal customer needs · BP03 Evaluate governance requirements · BP04 Evaluate compliance requirements · BP05 Evaluate threat landscape · BP06 Evaluate trade-offs while managing benefits and risks |
| Operating model | No numbered best practices. Describes centralised, decentralised and federated organisation models and the team-level path towards "you build it, you run it" with two-pizza teams that own a workload end to end. |
| Organizational culture (OPS03) | BP01 Provide executive sponsorship · BP02 Empower team members to take action when outcomes are at risk · BP03 Encourage escalation · BP04 Timely, clear and actionable communications · BP05 Encourage experimentation · BP06 Encourage team members to maintain and grow their skill sets · BP07 Resource teams appropriately |
| Implement observability (OPS04) | BP01 Identify key performance indicators · BP02 Implement application telemetry · BP03 Implement user experience telemetry · BP04 Implement dependency telemetry · BP05 Implement distributed tracing |
| Design for operations (OPS05) | BP01 Use version control · BP02 Test and validate changes · BP03 Use configuration management systems · BP04 Use build and deployment management systems · BP05 Perform patch management · BP06 Share design standards · BP07 Implement practices to improve code quality · BP08 Use multiple environments · BP09 Make frequent, small, reversible changes · BP10 Fully automate integration and deployment |
| Mitigate deployment risks (OPS06) | BP01 Plan for unsuccessful changes · BP02 Test deployments · BP03 Employ safe deployment strategies · BP04 Automate testing and rollback |
| Operational readiness and change management (OPS07) | BP01 Ensure personnel capability · BP02 Ensure a consistent review of operational readiness · BP03 Use runbooks to perform procedures · BP04 Use playbooks to investigate issues · BP05 Make informed decisions to deploy systems and changes · BP06 Create support plans for production workloads |
| Utilizing workload observability (OPS08) | BP01 Analyse workload metrics · BP02 Analyse workload logs · BP03 Analyse workload traces · BP04 Create actionable alerts · BP05 Create dashboards |
| Understanding operational health (OPS09) | BP01 Measure operations goals and KPIs with metrics · BP02 Communicate status and trends to ensure visibility into operations · BP03 Review operations metrics and prioritise improvement |
| Responding to events (OPS10) | BP01 Use a process for event, incident and problem management · BP02 Have a process per alert · BP03 Prioritise operational events based on business impact · BP04 Define escalation paths · BP05 Define a customer communication plan for service-impacting events · BP06 Communicate status through dashboards · BP07 Automate responses to events |
| Learn, share and improve (OPS11) | BP01 Have a process for continuous improvement · BP02 Perform post-incident analysis · BP03 Implement feedback loops · BP04 Perform knowledge management · BP05 Define drivers for improvement · BP06 Validate insights · BP07 Perform operations metrics reviews · BP08 Document and share lessons learned · BP09 Allocate time to make improvements |
The ability to protect data, systems, and assets, taking advantage of cloud technologies to improve your security posture.
Design principles
- Implement a strong identity foundation (least privilege, separation of duties, no long-lived credentials)
- Maintain traceability: monitor, alert, and audit actions and changes
- Apply security at all layers (edge, VPC, subnet, load balancer, instance, OS, application)
- Automate security best practices
- Protect data in transit and at rest
- Keep people away from data
- Prepare for security events with incident response runbooks and simulations
Best-practice areas
| Area | Key services and practices |
|---|---|
| Security foundations | Multi-account with AWS Organizations, Control Tower, SCPs, separate accounts per environment |
| Identity and access management | IAM Identity Center (SSO), IAM roles, permission boundaries, IAM Access Analyzer, MFA |
| Detection | CloudTrail (org trail), GuardDuty, Security Hub, Config, Inspector, Detective |
| Infrastructure protection | VPC design, security groups, WAF, Shield, Network Firewall, Systems Manager Session Manager |
| Data protection | KMS, Secrets Manager, ACM, S3 Block Public Access, Macie, TLS everywhere |
| Incident response | Playbooks, isolation automation, forensic accounts, snapshots, regular exercises |
| Application security | Threat modelling, dependency scanning, SAST/DAST in the pipeline, signed artifacts |
Example: least-privilege policy with conditions
{
"Version": "2012-10-17",
"Statement": [{
"Effect": "Allow",
"Action": ["s3:GetObject"],
"Resource": "arn:aws:s3:::my-app-data/reports/*",
"Condition": {
"Bool": { "aws:SecureTransport": "true" },
"StringEquals": { "aws:PrincipalOrgID": "o-exampleorgid" }
}
}]
}
Baseline quick wins
# Block public access on every bucket in the account aws s3control put-public-access-block --account-id 111122223333 \ --public-access-block-configuration \ BlockPublicAcls=true,IgnorePublicAcls=true,BlockPublicPolicy=true,RestrictPublicBuckets=true # Require IMDSv2 on an instance aws ec2 modify-instance-metadata-options --instance-id i-0abc123 \ --http-tokens required --http-endpoint enabled # Enable GuardDuty aws guardduty create-detector --enable
Identity and access management (SEC02, SEC03)
Get the right people and machines the right access under the right conditions. Two identity types: human (workforce, third parties, application users) and machine (EC2, Lambda, tools, external systems).
| ID | Best practice |
|---|---|
| SEC02-BP01 | Use strong sign-in mechanisms |
| SEC02-BP02 | Use temporary credentials |
| SEC02-BP03 | Store and use secrets securely |
| SEC02-BP04 | Rely on a centralised identity provider |
| SEC02-BP05 | Audit and rotate credentials periodically |
| SEC02-BP06 | Employ user groups and attributes |
| SEC03-BP01 | Define access requirements |
| SEC03-BP02 | Grant least-privilege access |
| SEC03-BP03 | Establish an emergency access process |
| SEC03-BP04 | Reduce permissions continuously |
| SEC03-BP05 | Define permission guardrails for your organisation |
| SEC03-BP06 | Manage access based on lifecycle |
| SEC03-BP07 | Analyse public and cross-account access |
| SEC03-BP08 | Share resources securely within your organisation |
| SEC03-BP09 | Share resources securely with a third party |
Policy types
| Type | What it does |
|---|---|
| Identity-based (managed / inline) | Attached to users, groups or roles. Managed policies (AWS-managed or customer-managed) are preferred; create customer-managed policies for least privilege. Inline policies are tied one-to-one to an identity and deleted with it. |
| Resource-based | Attached to a resource, such as an S3 bucket policy; can grant to principals in the same or another account. |
| Permissions boundary | Sets the maximum permissions an identity can have, so developers can create roles without escalating their own privilege. |
| ABAC | Grants permissions by matching tags on principals and resources, so new resources inherit access without policy edits. |
| Organizations SCP | Maximum permissions for accounts in an OU. Limits but never grants. |
| Session policy | Limits the permissions of an assumed-role or federated session. Limits but never grants. |
Detection (SEC04)
Detection has two halves: spotting unexpected configuration changes (in templates and pipelines before deployment, in deployed environments, and in running workloads outside a known deployment or scaling event) and spotting unexpected behaviour (GuardDuty for malicious activity, plus alerts on mutating API calls the workload shouldn't make and calls that change security posture). Review detection mechanisms regularly against internal and external policy.
| Best practice | Risk if absent | Summary |
|---|---|---|
| SEC04-BP01 Configure service and application logging | High | Retain security event logs for audit, investigation and compliance. Baseline sources: CloudTrail (an org trail with S3, or CloudTrail Lake with up to seven years of retention and SQL queries), VPC Flow Logs and Route 53 Resolver query logs. Add ELB, WAF, Config, GuardDuty findings, EKS audit, and OS/application logs. Store in S3 (cheap, lifecycle, Athena) or CloudWatch Logs (Logs Insights); typically 3–12 months queryable and up to 7 years retained. Avoid keeping logs forever or deleting too soon, open access to logs, and logging everything "just in case". |
| SEC04-BP02 Capture logs, findings and metrics in standardised locations | Medium | Aggregate security data into a separate Log Archive account (prevents tampering from compromised workloads, gives one integration point and one retention model). Run analytics from a separate Security Tooling account with cross-account read. Amazon Security Lake normalises data to OCSF in Parquet on S3, with no ETL; Control Tower creates both accounts. Capture data from opted-in Regions even if unused, and respect data-sovereignty rules. |
| SEC04-BP03 Correlate and enrich security alerts | Low | Alerts record who did what to which resource; map identifiers across sources so alerts can be correlated. Context sets true severity (a low-severity GuardDuty DNS alert plus hundreds of instances launched by the same identity becomes high). Sources include GuardDuty, Security Hub, Macie, Inspector, Config, IAM Access Analyzer, Network Access Analyzer and billing alarms. Amazon Detective builds relationship graphs; or build your own with Lambda, Athena and EventBridge. The AWS Threat Technique Catalog extends MITRE ATT&CK. |
| SEC04-BP04 Initiate remediation for non-compliant resources | Medium | Define standard remediations in code (Lambda, Systems Manager Automation) and start them manually or automatically via Config remediation actions or Security Hub custom actions through EventBridge. Use least-privilege roles, test before automating, keep human oversight, and log actions and outcomes (CloudWatch Logs, Security Hub finding notes). Automated Security Response on AWS provides pre-built remediations. |
# Organization-wide, multi-Region CloudTrail trail with log file validation aws cloudtrail create-trail --name org-trail \ --s3-bucket-name my-log-archive-bucket \ --is-organization-trail --is-multi-region-trail \ --enable-log-file-validation aws cloudtrail start-logging --name org-trail # VPC Flow Logs to S3 for a VPC aws ec2 create-flow-logs --resource-type VPC --resource-ids vpc-0abc123 \ --traffic-type ALL --log-destination-type s3 \ --log-destination arn:aws:s3:::my-log-archive-bucket/flowlogs/
Infrastructure protection (SEC05, SEC06)
Defence in depth: trust boundaries (network and account), system hardening and patching, OS authentication, and policy-enforcement points such as WAF and API gateways. Take a Zero Trust approach where components do not trust each other. Know Regions, AZs (independent power, cooling and physical security, with encrypted inter-AZ traffic), Local Zones and Outposts.
| ID | Best practice | Notes |
|---|---|---|
| SEC05-BP01 | Create network layers | Protecting networks: layered VPC design backed by inspection and automation. For serverless or edge-only workloads see the Serverless Applications Lens. |
| SEC05-BP02 | Control traffic flow within your network layers | |
| SEC05-BP03 | Implement inspection-based protection | |
| SEC05-BP04 | Automate network protection | |
| SEC06-BP01 | Perform vulnerability management | Protecting compute (EC2, containers, Lambda, databases, IoT): defence in depth, vulnerability management, smaller attack surface, automated configuration, and acting at a distance. |
| SEC06-BP02 | Provision compute from hardened images | |
| SEC06-BP03 | Reduce manual management and interactive access | |
| SEC06-BP04 | Validate software integrity | |
| SEC06-BP05 | Automate compute protection |
Data protection (SEC07, SEC08, SEC09)
Classify data first, then protect it at rest and in transit. Encryption makes data unreadable without a key; tokenisation substitutes a meaningless token (not derived from the data, so a hash doesn't count) and can shrink compliance scope; masking redacts part of a value. Audit key use: KMS key usage appears in CloudTrail and can be queried with CloudWatch Logs Insights.
| Area | Best practices |
|---|---|
| Data classification (SEC07) | BP01 Understand your data classification scheme · BP02 Apply data protection controls based on sensitivity · BP03 Automate identification and classification · BP04 Define scalable data lifecycle management |
| Data at rest (SEC08) | BP01 Implement secure key management · BP02 Enforce encryption at rest · BP03 Automate data-at-rest protection · BP04 Enforce access control |
| Data in transit (SEC09) | BP01 Implement secure key and certificate management · BP02 Enforce encryption in transit · BP03 Authenticate network communications |
Incident response (SEC10)
Even with strong preventive and detective controls, prepare to respond. Preparation (tools and access in place beforehand, rehearsed through game days) determines how well you can isolate, contain, investigate, and restore a known-good state.
| Aspect | What it involves |
|---|---|
| Preparation | People (stakeholders, training), process (documented architectures, plans, playbooks), technology (access, logging, alerting, investigation tooling). All three are required. |
| Operations | NIST phases: detect (find a potential event), analyse (is it an incident, and what is the scope), contain (limit the scope), eradicate (remove unauthorised artefacts and fix the cause), recover (restore a known-safe state and monitor). Phases can loop; after containment you may return to analysis. |
| Post-incident activity | Iterate on incidents and simulations to improve detection, response and time to safe operations, with clear ownership of improvements. |
| ID | Best practice |
|---|---|
| SEC10-BP01 | Identify key personnel and external resources |
| SEC10-BP02 | Develop incident management plans |
| SEC10-BP03 | Prepare forensic capabilities |
| SEC10-BP04 | Develop and test security incident response playbooks |
| SEC10-BP05 | Pre-provision access |
| SEC10-BP06 | Pre-deploy tools |
| SEC10-BP07 | Run simulations |
| SEC10-BP08 | Establish a framework for learning from incidents |
Cloud response design goals
- Establish response objectives with stakeholders and legal counsel (contain, recover, preserve forensics, learn)
- Respond in the cloud, where the event and data live
- Know what you have and need: copy logs, snapshots and evidence into a central response account with tags and retention
- Use redeployment: fix misconfigurations by redeploying; for compromise, verify the root cause is mitigated
- Automate common triage and response; use humans for unique, complex or sensitive incidents
- Choose solutions that scale with your cloud usage
- Learn and improve; simulations are a safe way to find gaps
Application security (SEC11)
Design, build and test security properties as a normal part of the SDLC. Defects are cheaper to fix earlier, and threat modeling in design is the cheapest control of all. Four themes: organisation and culture, security of the pipeline, security in the pipeline, and dependency management.
| ID | Best practice |
|---|---|
| SEC11-BP01 | Train for application security |
| SEC11-BP02 | Automate testing throughout the development and release lifecycle |
| SEC11-BP03 | Perform regular penetration testing |
| SEC11-BP04 | Conduct code reviews |
| SEC11-BP05 | Centralise services for packages and dependencies |
| SEC11-BP06 | Deploy software programmatically |
| SEC11-BP07 | Regularly assess security properties of the pipelines |
| SEC11-BP08 | Build a program that embeds security ownership in workload teams |
Operating workloads securely (SEC01)
Operating securely spans the whole lifecycle: design, build, run, and improve. The framework's answer is governance (consistent decisions that don't rely on individual judgment), automation (the same response every time), and shared components (common accounts, identity, logging, and base images) instead of each team building its own security. The best practices below follow SEC01-BP01 (separate workloads using accounts) and BP02 (secure account root user and properties).
| Best practice | Risk if absent | Summary |
|---|---|---|
| BP03 Identify and validate control objectives | High | Derive control objectives from compliance requirements and your threat model (SOC 2, PCI-DSS, ISO 27001, NIST SP 800-53, HITRUST). Use AWS Artifact to see which controls AWS covers and which are yours. Enforce with preventive controls (SCPs, resource and trust policies) and detect with AWS Config rules, Security Hub CSPM standards (FSBP, CIS AWS Foundations) and Config conformance packs. Start Config rules in report-only mode, then move to enforcement. Report effectiveness through automation. |
| BP04 Stay up to date with threats and recommendations | High | Follow MITRE ATT&CK, CVE, OWASP Top 10 and AWS Security Bulletins. Prefer services that update their own threat intelligence: GuardDuty, Inspector (CVE database), and WAF / Shield Advanced managed rule groups. Pair with automated fleet management and patching. |
| BP05 Reduce security management scope | Medium | Use managed services (RDS, ECS/EKS, serverless) to shift controls to AWS and reduce patching, backup and provisioning work. Include security upkeep in TCO comparisons against self-hosting on EC2. You still own update timing and impact (RDS engine versions, Lambda runtimes); AWS Health helps track these lifecycle events. |
| BP06 Automate deployment of standard security controls | Medium | Define controls as IaC (CloudFormation), keep them in version control, test in CI/CD (CloudFormation Guard) and detect drift. Separate pipeline accounts and separate duties for authors and deployers. Offer approved templates as self-service via Service Catalog, Control Tower and Account Factory. Back up control configurations and scripts. |
| BP07 Identify threats and prioritise mitigations with a threat model | High | Threat model early and keep it as a living document; revisit on major changes, new services and landscape shifts. Use Shostack's four questions and STRIDE. Focus on custom code, where most vulnerabilities originate. Threat Composer helps produce human- and machine-readable models. |
| BP08 Evaluate and implement new security services and features regularly | Low | Subscribe to What's New, the AWS Security Blog and the Daily Feature Updates SNS topic, plus GuardDuty and Security Hub CSPM announcements. Attend re:Inforce / re:Invent sessions and use your account team or TAM. |
Threat modeling: Shostack's four questions
| Question | Practice |
|---|---|
| What are we working on? | Data flow diagram, written assumptions, explicit scope |
| What can go wrong? | Brainstorm with STRIDE: Spoofing, Tampering, Repudiation, Information disclosure, Denial of service, Elevation of privilege |
| What are we going to do about it? | Choose mitigations you control under the shared responsibility model; cover IAM, data protection, infrastructure, logging and monitoring, and application code (input validation, session handling, bounds checks) |
| Did we do a good job? | Review, practise, and improve model quality and speed over time |
Example: preventive guardrail (SCP) and a CI check (CloudFormation Guard)
// SCP: member accounts cannot switch off GuardDuty
{
"Version": "2012-10-17",
"Statement": [{
"Sid": "ProtectGuardDuty",
"Effect": "Deny",
"Action": ["guardduty:DeleteDetector", "guardduty:UpdateDetector",
"guardduty:DisassociateFromMasterAccount"],
"Resource": "*"
}]
}
# rules.guard: fail the pipeline if a bucket has no encryption configured rule s3_buckets_encrypted { Resources.*[ Type == 'AWS::S3::Bucket' ] { Properties.BucketEncryption exists } } # Run in CI cfn-guard validate --data template.yaml --rules rules.guard
The ability of a workload to perform its intended function correctly and consistently, including operating and testing it through its total lifecycle, and recovering from failure.
Design principles
- Automatically recover from failure (detect via KPIs, trigger remediation)
- Test recovery procedures
- Scale horizontally to increase aggregate availability
- Stop guessing capacity
- Manage change through automation
Best-practice areas
| Area | Key practices |
|---|---|
| Foundations | Service quotas, network topology, multi-AZ subnets, adequate IP space |
| Workload architecture | Service-oriented design, loose coupling, idempotent APIs, avoid hard dependencies |
| Change management | Auto Scaling, deploy with canary or blue/green, feature flags |
| Failure management | Backups, multi-AZ and multi-Region DR, chaos testing, health checks, graceful degradation |
Resilience patterns
Timeouts + retries
Bounded timeouts on every call
Exponential backoff with jitter
Retry budgets to avoid retry storms
Idempotency keys for writes
Circuit breaker + bulkhead
Stop calling a failing dependency
Isolate resource pools per dependency
Fail fast, serve degraded responses
Load shedding
Reject excess work early
Prioritise critical requests
Keep latency bounded under overload
Static stability
Pre-provision capacity across AZs
Data plane works without control plane
Avoid needing to launch resources during an outage
Availability maths
| Availability | Downtime / year | Downtime / month |
|---|---|---|
| 99% | 3.65 days | 7.3 hours |
| 99.9% | 8.76 hours | 43.8 minutes |
| 99.95% | 4.38 hours | 21.9 minutes |
| 99.99% | 52.6 minutes | 4.38 minutes |
| 99.999% | 5.26 minutes | 26.3 seconds |
Disaster recovery strategies
| Strategy | RTO / RPO | Description | Relative cost |
|---|---|---|---|
| Backup & restore | Hours / hours | Backups copied to another Region, rebuilt from IaC on demand | $ |
| Pilot light | Tens of minutes / minutes | Data replicated, core infrastructure provisioned but scaled to zero | $$ |
| Warm standby | Minutes / seconds | Scaled-down but fully functional copy running in DR Region | $$$ |
| Multi-site active/active | Near zero / near zero | Full capacity in multiple Regions serving traffic | $$$$ |
Key services
| Service | Role |
|---|---|
| Auto Scaling, ELB/ALB/NLB | Self-healing capacity across AZs |
| Route 53 (health checks, failover) | DNS-based failover and routing policies |
| RDS Multi-AZ / Aurora Global Database | Synchronous in-Region replication; cross-Region replication |
| DynamoDB global tables, S3 CRR | Multi-Region data replication |
| AWS Backup | Centralised, policy-based backups with cross-Region/account copies |
| SQS / SNS / EventBridge | Decoupling and buffering between components |
| AWS Resilience Hub, Fault Injection Service | Assess resilience and run chaos experiments |
| Elastic Disaster Recovery | Continuous replication for server-based workloads |
Example: Auto Scaling group spread across AZs with ELB health checks
aws autoscaling create-auto-scaling-group \ --auto-scaling-group-name web-asg \ --launch-template LaunchTemplateName=web,Version='$Latest' \ --min-size 3 --max-size 12 \ --vpc-zone-identifier "subnet-aaa,subnet-bbb,subnet-ccc" \ --target-group-arns arn:aws:elasticloadbalancing:...:targetgroup/web/abc \ --health-check-type ELB --health-check-grace-period 120
Reliability areas in detail
| Area | Topics | Summary |
|---|---|---|
| Foundations | Manage service quotas and constraints · Plan your network topology | Requirements that reach beyond a single workload. AWS supplies the capacity; you must track service quotas and plan IP space and connectivity before architecting the workload. |
| Workload architecture | Design your workload service architecture · Design interactions to prevent failures · Design interactions to mitigate or withstand failures | Upfront software and infrastructure decisions drive reliability across all pillars. Choose service boundaries deliberately, then design the distributed-system interactions to avoid failures (for example idempotency) and to survive them (timeouts, retries, graceful degradation). |
| Change management | Monitor workload resources · Design the workload to adapt to changes in demand · Implement change | Plan for external change (demand spikes) and internal change (deployments, security patches). Monitor resources, scale automatically with demand, and deploy through automation. |
| Failure management | Back up data · Use fault isolation · Design to withstand component failures · Test reliability · Plan for disaster recovery | Everything eventually fails, so build resiliency in. Back up data, isolate faults (AZs, cells, bulkheads), remove single points of failure, test recovery paths (including with fault injection), and choose a DR strategy that matches RTO and RPO. The people building and running the workload must know the business reliability goals. |
Best practices by topic
| Topic | Best practices |
|---|---|
| Manage service quotas and constraints (REL01) | BP01 Be aware of service quotas and constraints · BP02 Manage service quotas across accounts and Regions · BP03 Accommodate fixed quotas and constraints through architecture · BP04 Monitor and manage quotas · BP05 Automate quota management · BP06 Keep a sufficient gap between current quotas and maximum usage to accommodate failover |
| Plan your network topology (REL02) | BP01 Use highly available connectivity for public endpoints · BP02 Provision redundant connectivity between cloud and on-premises private networks · BP03 Ensure IP subnet allocation accounts for expansion and availability · BP04 Prefer hub-and-spoke over many-to-many mesh · BP05 Enforce non-overlapping private IP ranges in connected address spaces |
| Design your workload service architecture (REL03) | BP01 Choose how to segment your workload (monolith, SOA, microservices) · BP02 Build services focused on specific business domains and functionality · BP03 Provide service contracts per API |
| Prevent failures in distributed systems (REL04) | BP01 Identify the kind of distributed system you depend on · BP02 Implement loosely coupled dependencies · BP03 Do constant work · BP04 Make mutating operations idempotent |
| Mitigate or withstand failures in distributed systems (REL05) | BP01 Implement graceful degradation (hard dependencies become soft) · BP02 Throttle requests · BP03 Control and limit retry calls · BP04 Fail fast and limit queues · BP05 Set client timeouts · BP06 Make systems stateless where possible · BP07 Implement emergency levers |
| Monitor workload resources (REL06) | BP01 Monitor all components (generation) · BP02 Define and calculate metrics (aggregation) · BP03 Send notifications (real-time processing and alarming) · BP04 Automate responses · BP05 Analyse logs · BP06 Regularly review monitoring scope and metrics · BP07 Monitor end-to-end tracing of requests |
| Adapt to changes in demand (REL07) | BP01 Use automation when obtaining or scaling resources · BP02 Obtain resources upon detection of impairment · BP03 Obtain resources upon detection that more are needed · BP04 Load test your workload |
| Implement change (REL08) | BP01 Use runbooks for standard activities such as deployment · BP02 Integrate functional testing into deployment · BP03 Integrate resiliency testing into deployment · BP04 Deploy using immutable infrastructure · BP05 Deploy changes with automation |
| Back up data (REL09) | BP01 Identify and back up all data that needs it, or reproduce it from sources · BP02 Secure and encrypt backups · BP03 Perform backups automatically · BP04 Periodically recover data to verify backup integrity and process |
| Fault isolation (REL10) | BP01 Deploy the workload to multiple locations · BP02 Automate recovery for components constrained to a single location · BP03 Use bulkhead architectures to limit scope of impact |
| Withstand component failures (REL11) | BP01 Monitor all components to detect failures · BP02 Fail over to healthy resources · BP03 Automate healing on all layers · BP04 Rely on the data plane, not the control plane, during recovery · BP05 Use static stability to prevent bimodal behaviour · BP06 Send notifications when events affect availability · BP07 Architect to meet availability targets and uptime SLAs |
| Test reliability (REL12) | BP01 Use playbooks to investigate failures · BP02 Perform post-incident analysis · BP03 Test scalability and performance requirements · BP04 Test resiliency using chaos engineering · BP05 Conduct game days regularly |
| Plan for disaster recovery (REL13) | BP01 Define recovery objectives for downtime and data loss · BP02 Use defined recovery strategies to meet them · BP03 Test the DR implementation · BP04 Manage configuration drift at the DR site or Region · BP05 Automate recovery |
The ability to use computing resources efficiently to meet system requirements, and to maintain that efficiency as demand changes and technologies evolve.
Design principles
- Democratise advanced technologies by consuming them as managed services
- Go global in minutes (multi-Region, edge locations)
- Use serverless architectures to remove undifferentiated operations
- Experiment more often (easy A/B comparison of instance types and designs)
- Consider mechanical sympathy: choose the technology that fits the access pattern
Selecting resources
| Domain | Options and when to choose them |
|---|---|
| Compute | EC2 (full control, Graviton for price/performance), containers on ECS/EKS/Fargate, Lambda (event-driven, spiky load) |
| Storage | EBS (block, low latency), EFS/FSx (shared file), S3 (object, durable), instance store (ephemeral, very fast) |
| Database | Aurora/RDS (relational), DynamoDB (key-value at scale), ElastiCache/MemoryDB (in-memory), OpenSearch (search), Redshift (analytics), Neptune (graph) |
| Networking | CloudFront for edge caching, Global Accelerator, placement groups, ENA/EFA, VPC endpoints, Direct Connect |
Review and monitor
Measure before tuning
Load test with realistic traffic
Track p50/p95/p99 latency, not averages
Define SLOs and alert on burn rate
Right-size continuously
Compute Optimizer recommendations
Revisit instance family each generation
Benchmark Graviton for compatible workloads
Cache at every layer
CloudFront at the edge
API Gateway cache
ElastiCache / DAX in front of the database
Trade-offs
Consistency vs latency
Compression vs CPU
Batching vs responsiveness
Choose deliberately and document
Best practices by focus area
| Focus area | Best practices |
|---|---|
| Architecture selection (PERF01) | BP01 Learn about available cloud services and features · BP02 Use guidance from your cloud provider or a partner for patterns and best practices · BP03 Factor cost into architectural decisions · BP04 Evaluate how trade-offs affect customers and architecture efficiency · BP05 Use policies and reference architectures · BP06 Use benchmarking to drive architectural decisions · BP07 Use a data-driven approach for architectural choices |
| Compute and hardware (PERF02) | BP01 Select the best compute options · BP02 Understand compute configuration and features · BP03 Collect compute-related metrics · BP04 Configure and right-size compute · BP05 Scale compute dynamically · BP06 Use optimized hardware-based accelerators |
| Data management (PERF03) | BP01 Use a purpose-built data store · BP02 Evaluate configuration options for the data store · BP03 Collect and record data store performance metrics · BP04 Improve query performance · BP05 Implement data access patterns that use caching |
| Networking and content delivery (PERF04) | BP01 Understand how networking affects performance · BP02 Evaluate networking features · BP03 Choose dedicated connectivity or VPN appropriately · BP04 Use load balancing to distribute traffic · BP05 Choose network protocols to improve performance · BP06 Choose workload location based on network requirements · BP07 Optimize network configuration based on metrics |
| Process and culture (PERF05) | BP01 Establish KPIs for workload health and performance · BP02 Use monitoring to find where performance matters most · BP03 Define a process to improve performance · BP04 Load test your workload · BP05 Automate remediation of performance issues · BP06 Keep workload and services up to date · BP07 Review metrics at regular intervals |
Process and culture principles
- Infrastructure as code and a deployment pipeline: repeatable, low-cost, source-controlled environments
- Well-defined metrics: technical and business KPIs, interpreted with maximum or p99 rather than averages
- Automated performance tests: start new environments with test data, run benchmarks and load tests after quick tests pass, and tie results to the build
- Load generation: idempotent, uncoupled scripts that mimic production user journeys (Spot Instances keep it cheap)
- Visibility and visualisation: per-build metrics, with performance overlaid on architecture diagrams to spot hot spots and wait states
- Regular review and continual optimisation: poor performance usually traces back to a missing or broken review process
The ability to run systems that deliver business value at the lowest price point, while understanding where money is being spent.
Design principles
- Implement cloud financial management (FinOps)
- Adopt a consumption model: pay only for what you use
- Measure overall efficiency (business output per unit cost)
- Stop spending money on undifferentiated heavy lifting
- Analyse and attribute expenditure to teams and workloads
Best-practice areas
| Area | Key practices |
|---|---|
| Practice Cloud Financial Management | Ownership, cost-aware culture, budgets and forecasts |
| Expenditure and usage awareness | Cost allocation tags, Cost Explorer, CUR, Budgets, Anomaly Detection |
| Cost-effective resources | Right-sizing, pricing models, managed services, data transfer awareness |
| Manage demand and supply | Auto Scaling, queues for buffering, scheduling non-prod environments off |
| Optimise over time | Review new services and instance generations, decommission unused resources |
Pricing models
| Model | Best for | Notes |
|---|---|---|
| On-Demand | Spiky, unknown, or short-lived load | No commitment, highest unit price |
| Compute Savings Plans | Steady baseline across EC2, Fargate, Lambda | 1 or 3 year commitment, flexible across families and Regions |
| EC2 Instance Savings Plans / RIs | Stable, known instance family and Region | Deeper discount, less flexibility |
| Spot | Fault-tolerant, stateless, batch, CI | Up to ~90% off; can be interrupted with a 2-minute notice |
| S3 storage classes | Data with differing access patterns | Intelligent-Tiering or lifecycle rules to move colder data |
Example: budget with alert, and tag-based cost visibility
# Monthly cost budget, alert at 80% of actual spend aws budgets create-budget --account-id 111122223333 \ --budget '{"BudgetName":"monthly","BudgetLimit":{"Amount":"5000","Unit":"USD"}, "TimeUnit":"MONTHLY","BudgetType":"COST"}' \ --notifications-with-subscribers '[{ "Notification":{"NotificationType":"ACTUAL","ComparisonOperator":"GREATER_THAN", "Threshold":80,"ThresholdType":"PERCENTAGE"}, "Subscribers":[{"SubscriptionType":"EMAIL","Address":"finops@example.com"}]}]' # Cost by tag over a period aws ce get-cost-and-usage --time-period Start=2026-10-01,End=2026-11-01 \ --granularity MONTHLY --metrics UnblendedCost \ --group-by Type=TAG,Key=team
Cloud Financial Management: see, save, plan, run
| Tenet | Question | Services |
|---|---|---|
| See | How do we measure, monitor and assign accountability for spend? | Organizations, Control Tower, cost allocation tags, tag policies, Resource Groups, Cost Categories, Cost Explorer, Cost and Usage Report |
| Save | Which levers (pricing models, resource choices) are we using? | Savings Plans / RIs, EC2 Auto Scaling, Spot Instances |
| Plan | How do we forecast and budget for variable usage? | Cost Explorer, Cost and Usage Report, Budgets |
| Run | Which guardrails and processes keep spend within budget? | Billing console, IAM, SCPs, Service Catalog, Cost Anomaly Detection, Budgets |
Cloud financial management practices (COST01)
| ID | Practice |
|---|---|
| COST01-BP01 | Establish ownership of cost optimization |
| COST01-BP02 | Establish a partnership between finance and technology |
| COST01-BP03 | Establish cloud budgets and forecasts |
| COST01-BP04 | Implement cost awareness in your organisational processes |
| COST01-BP05 | Report and notify on cost optimization |
| COST01-BP06 | Monitor cost proactively |
| COST01-BP07 | Keep up to date with new service releases |
| COST01-BP08 | Create a cost-aware culture |
| COST01-BP09 | Quantify business value from cost optimization |
The other cost areas
| Area | Topics | Summary |
|---|---|---|
| Expenditure and usage awareness | Governance · Monitor cost and usage · Decommission resources | Attribute costs to workloads, organisation units and product owners to drive efficient behaviour and reduce waste. Gather data, analyse, and report; change in usage drives change in cost. |
| Cost-effective resources | Evaluate cost when selecting services · Select the correct resource type, size and number · Select the best pricing model · Plan for data transfer | Match services, resource sizes and configurations to the workload, then pick the pricing model that fits its usage pattern. |
| Manage demand and supply (COST09) | BP01 Analyse workload demand · BP02 Implement a buffer or throttle to manage demand · BP03 Supply resources dynamically | Supply resources to match demand instead of over-provisioning, or smooth demand with throttles, buffers and queues. Know the acceptable and maximum delay before shaping demand, and balance just-in-time supply against failure, availability and provisioning time. |
| Optimise over time | Define a review process and analyse your workload regularly · Automating operations | Review architecture as AWS releases new services and features, decommission what you no longer need, and automate time-consuming operations. |
Best practices by topic (COST02 to COST11)
| Topic | Best practices |
|---|---|
| Governance (COST02) | BP01 Develop policies based on organisation requirements · BP02 Implement goals and targets · BP03 Implement an account structure · BP04 Implement groups and roles · BP05 Implement cost controls · BP06 Track project lifecycle |
| Monitor cost and usage (COST03) | BP01 Configure detailed information sources · BP02 Add organisation information to cost and usage · BP03 Identify cost attribution categories · BP04 Establish organisation metrics · BP05 Configure billing and cost management tools · BP06 Allocate costs based on workload metrics |
| Decommission resources (COST04) | BP01 Track resources over their lifetime · BP02 Implement a decommissioning process · BP03 Decommission resources · BP04 Decommission resources automatically · BP05 Enforce data retention policies |
| Evaluate cost when selecting services (COST05) | BP01 Identify organisation requirements for cost · BP02 Analyse all components of the workload · BP03 Perform a thorough analysis of each component · BP04 Select software with cost-effective licensing · BP05 Select components to optimise cost in line with organisation priorities · BP06 Perform cost analysis for different usage over time |
| Resource type, size and number (COST06) | BP01 Perform cost modeling · BP02 Select resource type, size and number based on data · BP03 Select them automatically based on metrics · BP04 Consider using shared resources |
| Best pricing model (COST07) | BP01 Perform pricing model analysis · BP02 Choose Regions based on cost · BP03 Select third-party agreements with cost-efficient terms · BP04 Implement pricing models for all components of the workload · BP05 Perform pricing model analysis at the management account level |
| Plan for data transfer (COST08) | BP01 Perform data transfer modeling · BP02 Select components to optimise data transfer cost · BP03 Implement services to reduce data transfer costs |
| Manage demand and supply (COST09) | BP01 Analyse workload demand · BP02 Implement a buffer or throttle · BP03 Supply resources dynamically |
| Review process (COST10) | BP01 Develop a workload review process · BP02 Review and analyse the workload regularly |
| Automating operations (COST11) | BP01 Perform automation for operations |
COST02-BP02 Implement goals and targets
Risk if not established: High. A goal is the direction you want to go; a target is how far, and by when. Make targets SMART: specific, measurable, assignable, realistic and timely.
| Type | Example |
|---|---|
| Usage vs cost goal | Platform usage grows a lot with only a small, non-linear rise in cost. Target: usage +20% with cost up by less than 5%. |
| Efficiency goal | Every workload gets more efficient over time. Target: cost per business metric down 5% every 6 to 12 months. |
| Waste goal | Minimise over-provisioning. Targets: waste no more than 10% of compute cost for tier-1 production workloads and 5% for tier-2. |
Example KPIs
| Category | KPI | Description |
|---|---|---|
| Compute | EC2 usage coverage | EC2 cost or hours covered by Savings Plans, RIs and Spot, versus total |
| Compute | Compute SP/RI utilisation | Utilised SP or RI hours versus total available |
| Compute | EC2 cost per hour / vCPU cost | EC2 cost divided by instances running in that hour; cost per vCPU across all instances |
| Compute | Latest instance generation | Share of instances on Graviton or other modern generations |
| Database | RDS coverage and utilisation | RDS cost or hours covered by RIs; utilised RI hours versus available |
| Database | RDS cost per hour; latest generation | RDS cost divided by instances running in that hour; share on Graviton or modern types |
| Storage | Storage utilisation | Optimised storage cost (Glacier, deep archive, Infrequent Access) divided by total storage cost |
| Tagging | Untagged resources | Cost Explorer: exclude credits, discounts, taxes, refunds and marketplace, show only untagged resources, divide by monthly cost |
Target values differ by organisation. Other common KPIs are percent of spend on-demand and adoption of gp3 EBS volumes.
Implementation steps
- Define expected usage: talk to application owners, marketing and the business about demand, seasonality and campaigns.
- Define resourcing and cost: work out what resources that usage needs and predict how cost changes as usage changes.
- Define business goals: combine usage and cost changes with expected technology changes. Keep goals simple and high-level, covering usage, cost and the relationship between them.
- Define targets: give each goal a measurable target and a deadline.
- Start with basic KPIs and refine them as the business evolves.
- Infrastructure metrics (latency, uptime) don't show business impact. Pair them with business metrics such as revenue or customer satisfaction.
- Aim for near real-time KPI visibility. AWS recommends the KPI dashboard in Cloud Intelligence Dashboards (CID), built on the Cost and Usage Report (CUR), with custom goals and progress tracking. Whatever tool you use, all cloud financial management stakeholders should adopt it.
Pricing model details
- Compute Savings Plans: up to about 66% off and the most flexible (any family, size, OS, tenancy, Region, and EC2, Fargate or Lambda). Instance Savings Plans: up to about 72%, less flexible. Payment options: no, partial or all upfront.
- Savings Plan practice: buy small commitments continually, purchase in an account with no usage (such as the management account) so they apply to the highest discounts first, and don't chase a coverage or utilisation percentage. Watch the potential savings in Cost Explorer recommendations and buy until they fall below your required discount.
- Reserved Instances: still apply to RDS, OpenSearch, ElastiCache, Redshift and DynamoDB. For EC2, Savings Plans give the same discount with more flexibility. Judge RIs by net savings in Cost Explorer.
- Spot: up to about 90% off, interruptible with a 2-minute notice (on average interrupted less than 5% of the time). Be flexible across instance types and AZs, design for statelessness, and combine with On-Demand and Savings Plans. EC2 Fleet blends On-Demand and Spot automatically.
- Third-party pricing: prefer terms that scale with the outcomes they deliver, not with your whole bill. Review pricing every two weeks to a month.
The ability to continually improve sustainability impacts by reducing energy consumption and increasing efficiency across all components of a workload, maximising the benefit from the provisioned resources and minimising the total resources required.
Design principles
- Understand your impact: measure against a business metric (e.g. emissions per transaction)
- Establish sustainability goals and model return on investment
- Maximise utilisation: right-size and consolidate
- Anticipate and adopt more efficient hardware and software offerings
- Use managed services, which share infrastructure at high utilisation
- Reduce the downstream impact of your cloud workloads (e.g. smaller payloads, fewer device upgrades)
Practical levers
| Lever | Examples |
|---|---|
| Region selection | Prefer Regions with lower carbon intensity where latency and data residency allow |
| Alignment to demand | Auto Scaling, scale to zero, schedule batch jobs for flexible times |
| Software and architecture | Efficient code, async processing, avoid polling, reduce data movement |
| Data | Lifecycle policies, compression, delete what you no longer need, tiered storage |
| Hardware and services | Graviton (better performance per watt), managed and serverless services, newer instance generations |
| Development process | Ephemeral test environments, efficient CI, device-farm usage on demand |
Best practices by area
| Area | Best practices | Focus |
|---|---|---|
| Region selection (SUS01) | BP01 Choose Region based on both business requirements and sustainability goals | Region choice affects performance, cost and carbon footprint together. |
| Alignment to demand (SUS02) | BP01 Scale infrastructure dynamically · BP02 Align SLAs with sustainability goals · BP03 Stop creating and maintaining unused assets · BP04 Optimise geographic placement based on networking requirements · BP05 Optimise team member resources for activities performed · BP06 Implement buffering or throttling to flatten the demand curve | Match resources to what users actually consume, remove what is unused, and place resources close to users. |
| Software and architecture (SUS03) | BP01 Optimise for asynchronous and scheduled jobs · BP02 Remove or refactor low- or no-use components · BP03 Optimise code that consumes the most time or resources · BP04 Optimise impact on devices and equipment · BP05 Use patterns that best support data access and storage | Keep utilisation high and smooth load; retire idle components; reduce the need for customer device upgrades. |
| Data management (SUS04) | BP01 Implement a data classification policy · BP02 Use technologies that support access and storage patterns · BP03 Use lifecycle policies for datasets · BP04 Use elasticity and automation to expand block storage or file systems · BP05 Remove unneeded or redundant data · BP06 Use shared file systems or storage for common data · BP07 Minimise data movement across networks · BP08 Back up data only when it is difficult to recreate | Provision less storage, move cold data to more efficient tiers, and delete what you don't need. |
| Hardware and services (SUS05) | BP01 Use the minimum hardware to meet your needs · BP02 Use instance types with the least impact · BP03 Use managed services · BP04 Optimise use of hardware-based compute accelerators | Provision less hardware and choose the most efficient hardware and services for the workload. |
| Process and culture (SUS06) | BP01 Communicate and cascade your sustainability goals · BP02 Adopt methods that can rapidly introduce sustainability improvements · BP03 Keep your workload up to date · BP04 Increase utilisation of build environments · BP05 Use managed device farms for testing | Reduce impact through development, test and deployment practices. |
Pillars pull against each other. The framework does not tell you which wins; it asks you to make the decision consciously, record it, and revisit it as the workload and business change.
| Decision | Gains | Costs |
|---|---|---|
| Multi-Region active/active | Reliability, latency | Cost, operational complexity, data consistency challenges |
| Extra security layers (inspection, encryption) | Security | Latency, cost, operational overhead |
| Aggressive Spot usage | Cost, sustainability | Interruption handling, reliability engineering effort |
| Caching | Performance, cost | Staleness, invalidation complexity |
| Over-provisioned headroom | Reliability, performance | Cost, sustainability |
A Well-Architected Review is a conversation, not an audit. Done with the team that owns the workload, it surfaces risks and produces an improvement plan. The AWS Well-Architected Tool (in the console, free to use) walks through the questions and tracks results.
Review flow
1. Define the workload scope, owners, environments, regions, accounts 2. Choose lenses Well-Architected Framework + any specialist lenses 3. Answer questions per pillar; choose the best-practice choices that apply 4. Identify risks each answer maps to None / Medium / High Risk Issues 5. Prioritise by business impact and effort; create improvement items 6. Remediate track in your normal backlog; save a milestone 7. Repeat on major changes, and at least yearly
Well-Architected Tool via CLI
# Create a workload aws wellarchitected create-workload \ --workload-name checkout-service \ --description "Customer checkout API" \ --environment PRODUCTION \ --lenses wellarchitected \ --review-owner team-checkout@example.com \ --aws-regions us-east-1 \ --pillar-priorities security reliability costOptimization \ --architectural-design "https://wiki.example.com/checkout" # List workloads aws wellarchitected list-workloads # See answers and risk counts for a workload aws wellarchitected list-answers --workload-id <id> \ --lens-alias wellarchitected --pillar-id security # Save a milestone (point-in-time snapshot) aws wellarchitected create-milestone --workload-id <id> \ --milestone-name "2026-Q4-review"
Good practice
- Review per workload, not per company, and include engineers who build and run it
- Don't aim for zero risks: aim for risks that are known, owned, and accepted or scheduled
- Review early in design and again before major launches, not only after incidents
- Feed findings into the same backlog as feature work
Lenses extend the core framework with guidance for a specific technology domain or industry. They apply the same six pillars with more specific questions and best practices.
| Lens | Focus |
|---|---|
| Serverless Applications | Lambda, API Gateway, Step Functions, event-driven design |
| SaaS | Tenant isolation, onboarding, tiering, per-tenant cost attribution |
| Data Analytics | Pipelines, lakes, warehouses, governance |
| Machine Learning | Training, deployment, MLOps, responsible AI |
| Generative AI | Foundation models, prompts, guardrails, evaluation |
| Container Build | ECS/EKS workload practices, image supply chain |
| Financial Services | Regulated workloads, resilience and compliance |
| Custom lenses | Your organisation's own standards, authored in JSON and shared across accounts |
Operational Excellence
IaC for everything
Small, reversible changes
Telemetry: metrics, logs, traces
Runbooks and post-incident reviews
Security
Least privilege, roles not keys
Multi-account + SCPs
CloudTrail, GuardDuty, Security Hub
Encrypt in transit and at rest (KMS)
Reliability
Multi-AZ by default
Timeouts, retries with jitter, breakers
Test restores and failovers
Know your RTO / RPO and quotas
Performance Efficiency
Pick resources by access pattern
Measure p99, load test
Cache, CDN, Graviton, serverless
Re-evaluate every few quarters
Cost Optimization
Tag and attribute spend
Right-size, Savings Plans, Spot
Watch data transfer and NAT
Turn off what is not in use
Sustainability
Maximise utilisation
Managed and serverless services
Lifecycle and delete old data
Efficient hardware (Graviton)
Useful services by purpose
| Need | Service |
|---|---|
| Automated best-practice checks | Trusted Advisor, Security Hub, Config conformance packs |
| Architecture risk tracking | Well-Architected Tool |
| Resilience assessment | Resilience Hub, Fault Injection Service |
| Right-sizing | Compute Optimizer |
| Spend visibility | Cost Explorer, Budgets, Cost Anomaly Detection, CUR |
| Account governance | Organizations, Control Tower, SCPs |
Found this guide useful? Buy me a coffee ☕