Architecture Diagrams

AWS Well-Architected reference designs for 5 infrastructure projects, built with Draw.io using official AWS icons

AWS Well-Architected Framework: Every diagram is designed against all 6 pillars, Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimisation, and Sustainability. Each includes defence-in-depth security layers, quantified cost trade-offs, and zero-SPOF reliability patterns.
01

Highly Available WordPress on AWS

3-AZ · Zero-SPOF · EC2 Auto Scaling · RDS Multi-AZ · CloudFront · WAF

3-AZ, zero-SPOF architecture with EC2 Auto Scaling, RDS Multi-AZ failover (<2 min RTO), CloudFront CDN, WAF (OWASP/SQLi rules), KMS CMK encryption at rest, IMDSv2, and SSM Session Manager (no bastion hosts, no SSH). Survives the loss of any single Availability Zone with no manual intervention.

AWS Terraform Multi-AZ Well-Architected
Networking (VPC, ALB, Route 53, CloudFront) Compute (EC2, Auto Scaling, AMI) Storage (S3, EFS, ElastiCache) Database (RDS MySQL Multi-AZ) Security (WAF, KMS, IAM, SSM) Monitoring (CloudWatch, SNS)

Reliability

3 AZs, RDS Multi-AZ failover <2 min, Auto Scaling on CPU + request metrics. Survives any single AZ loss.

Security

WAF (OWASP/SQLi), KMS CMK, IMDSv2, SSM (no SSH), S3 OAC, zero public S3 ACLs

Cost Optimisation

CloudFront edge caching reduces origin load ~60% | ElastiCache offloads DB reads

Performance Efficiency

CloudFront global CDN, ElastiCache session store, ALB connection draining

02

Multi-Account AWS Landing Zone

AWS Organizations · Transit Gateway · IAM Identity Center · GuardDuty · SCPs

Enterprise governance across 4 OUs and 10+ accounts. Transit Gateway hub-and-spoke for network isolation, IAM Identity Center SSO (SAML 2.0, MFA enforced), 8 Service Control Policies, delegated GuardDuty and Security Hub, and CloudTrail centralised to an immutable Log Archive account with MFA-Delete enabled.

AWS Organizations Terraform SCPs SSO
AWS Organizations (Root, OUs, Accounts) Networking (Transit Gateway, VPCs) Security (GuardDuty, Security Hub, IAM) Logging (CloudTrail, S3, KMS) Management (SSO, Config, SCPs)

Security

SCPs are the primary guardrail: deny root API calls, block public S3 ACLs, require IMDSv2, enforce region boundaries

Reliability

Transit Gateway with non-overlapping CIDRs; network account owns all routing (single failure domain for routing changes)

Operational Excellence

One identity source (IAM Identity Center); CloudTrail centralised to Log Archive with MFA-Delete S3 bucket

Scale

OU structure supports 100s of accounts; new account vending via Account Factory takes <15 min

03

Serverless Task Management API

API Gateway HTTP API · Lambda Graviton2/arm64 · DynamoDB · GitHub Actions OIDC

Full CRUD REST API at 90% lower cost than EC2+RDS. Five Lambda functions on Graviton2/arm64 (−20% cost vs x86), API Gateway HTTP API, DynamoDB PAY_PER_REQUEST with GSI, AWS X-Ray distributed tracing, and GitHub Actions OIDC CI/CD, eliminating all long-lived secrets. CloudWatch alarms on Duration P99, error rate, and throttle count.

Lambda Python DynamoDB GitHub Actions
API Layer (API Gateway HTTP API) Compute (Lambda Graviton2, CloudWatch, X-Ray) Database (DynamoDB PAY_PER_REQUEST + GSI) Identity (IAM Role, OIDC) CI/CD (GitHub Actions, OIDC deploy)

Cost ($2.32/mo at 1M req)

Graviton2 arm64 = 20% cheaper than x86; HTTP API = $1/M vs REST $3.50/M; DynamoDB PAY_PER_REQUEST = zero idle cost

Security

OIDC eliminates GitHub secrets; Lambda IAM role scoped to one DynamoDB table; X-Ray traces all invocations

Operational Excellence

Deploy pipeline blocks on integration test failure; CloudWatch alarms on p99, error rate >1%, throttle count

Performance

Lambda cold start <300 ms (Python + Graviton2); DynamoDB single-digit ms reads; GSI enables query by status

04

Three-Tier HA with Multi-Region Disaster Recovery

us-east-1 Primary · us-west-2 Warm Standby · RTO < 15 min · RPO < 5 min · Route 53 Failover

Three-tier architecture (presentation, application, data) across 3 Availability Zones in us-east-1 with an active-passive warm standby in us-west-2. Route 53 health-check failover (10s intervals, 60s DNS TTL), RDS cross-region read replica promotable in ~1 min, S3 Cross-Region Replication, and a pre-scaled ASG enable automated failover with RTO < 15 min and RPO < 5 min. Total cost: ~$750/mo primary + ~$200/mo DR.

Route 53 RDS Multi-AZ Auto Scaling Terraform
Public Subnets (ALB · NAT Gateways · 10.0.1-3.0/24) Private App Subnets (EC2 ASG · 10.0.11-13.0/24) Private DB Subnets (RDS · ElastiCache · 10.0.21-23.0/24) Shared Services (S3 · KMS · Secrets · GuardDuty · CloudTrail) DR Region us-west-2 (Warm Standby · ~$200/mo)

Reliability (RTO < 15 min)

Route 53 health checks every 10s. 3 consecutive failures trigger DNS failover (60s TTL). RDS read replica promotes in ~1 min. ASG scales to capacity automatically on failover load.

Security (SG Chain)

ALB-SG: inbound 443 from CloudFront prefix list only · App-SG: port 8080 from ALB-SG only · DB-SG: port 3306 from App-SG only · Cache-SG: port 6379 from App-SG only. No direct internet access to any compute or data layer.

Cost (~$950/mo total)

Primary us-east-1: ~$750/mo. DR warm standby us-west-2: ~$200/mo (30% of primary). S3/DynamoDB VPC Gateway Endpoints eliminate NAT charges for AWS service traffic. Graviton2 on RDS + ElastiCache.

Operational Excellence

CodePipeline rolling deploy with 20% min healthy + auto-rollback on failure. GuardDuty auto-isolation via Lambda. CloudTrail immutable audit log (Object Lock). Quarterly DR drill exercise documented.

05

Cloud Security & Compliance Framework

5 Defence-in-Depth Layers · WAF · GuardDuty · Security Hub · EventBridge Auto-Remediation

Defence-in-depth across five layers: perimeter (WAF OWASP rules, CloudFront, Security Groups, NACLs), identity (IAM least-privilege, Permission Boundaries, IMDSv2, Secrets Manager 30-day rotation), data protection (KMS CMK, TLS 1.2+/ACM), detection (GuardDuty ML, Security Hub CIS benchmark, Config, Inspector), and automated response (EventBridge → Lambda isolation in <60 seconds).

IAM GuardDuty Security Hub Compliance
Layer 1 · Perimeter (WAF, CloudFront, SGs, NACLs) Layer 2 · Identity (IAM, IMDSv2, SSM, Secrets Manager) Layer 3 · Data Protection (KMS, TLS, ACM) Layer 4 · Detection (GuardDuty, Security Hub, Config, Inspector) Layer 5 · Response (CloudWatch, EventBridge, Lambda, SNS)

Perimeter

WAF OWASP rules at edge; CloudFront enforces HTTPS; Security Groups use least-privilege; NACLs as stateless backstop

Identity

Permission Boundaries + SCPs prevent privilege escalation; IMDSv2 blocks SSRF; Secrets Manager rotates creds every 30 days

Detection

GuardDuty ML + Config >150 rules + Inspector CVE scanning all feed Security Hub (CIS benchmark score)

Response (<60 sec)

Security Hub → EventBridge → Lambda auto-isolates compromised EC2 (quarantine SG); SNS alerts on-call within seconds