Module 12 cheat sheet
One-page revision summary for High Availability & Disaster Recovery: services, Azure mapping, CLI commands, limits, decision rules, exam traps and cost traps.
Assumes: AWS CLI v2 · AWS SDK for .NET v4 · Microsoft.Extensions.Http.Resilience · Region us-east-1 (DR us-west-2) · facts as stated in the Module 12 lessons; items marked VERIFY there are not repeated as certain here. Verified against official sources on 2026-11-18.
A printable summary of Module 12. Each row links back to the lesson with the detail.
Key services
| Service | What it is for |
|---|---|
| EC2 Auto Scaling / Application Auto Scaling | Keep capacity between a minimum and maximum (EC2, ECS tasks, Lambda provisioned concurrency, DynamoDB, Aurora replicas) |
| Elastic Load Balancing (ALB/NLB) | Health-checked traffic spreading across AZs, connection draining |
| RDS Multi-AZ / Aurora | Managed in-Region failover; Aurora Global Database for cross-Region |
| DynamoDB global tables | Multi-Region replicas: MREC (async, last writer wins) or MRSC (sync, zero RPO) |
| Route 53 + health checks | DNS-based failover, weighted and latency routing |
| Application Recovery Controller | Zonal shift (AZ evacuation), routing controls (reliable manual Regional switch) |
| AWS Backup | Plans, vaults, Vault Lock, cross-Region and cross-account copies, restore testing |
| CloudFront / ElastiCache | Shield back ends from load and partial outages; never cache personal data carelessly |
| Fault Injection Service (FIS) | Controlled chaos with CloudWatch-alarm stop conditions |
| Resilience Hub / Well-Architected Tool | Policy-based assessment against RTO/RPO; structured reviews |
.NET / Azure → AWS
| Microsoft / Azure | AWS |
|---|---|
| Availability Zones | Availability Zones (you spread EC2/ECS yourself) |
| VM Scale Sets / App Service scale-out | EC2 ASG / ECS service auto scaling |
| Traffic Manager / Front Door | Route 53 health checks + failover routing / CloudFront |
| Azure SQL geo-replication | Aurora Global Database, RDS cross-Region replica |
| Cosmos DB multi-region writes | DynamoDB global tables |
| Azure Backup vault | AWS Backup vault + Vault Lock |
| Azure Site Recovery | Elastic Disaster Recovery, pilot light / warm standby |
| Azure Chaos Studio | FIS experiment template |
| Polly | Microsoft.Extensions.Http.Resilience pipelines |
Most useful CLI commands
| Task | Command |
|---|---|
| FIS: start / inspect / stop | aws fis start-experiment --experiment-template-id ID · aws fis get-experiment --id ID · aws fis stop-experiment --id ID |
| Create a backup vault | aws backup create-backup-vault --backup-vault-name NAME |
| Lock a vault | aws backup put-backup-vault-lock-configuration --backup-vault-name NAME ... |
| Restore testing plan | aws backup create-restore-testing-plan --restore-testing-plan file://rtplan.json |
| Check restore jobs | aws backup list-restore-jobs --by-status COMPLETED |
| Resilience Hub assessment | aws resiliencehub start-app-assessment ... · aws resiliencehub describe-app-assessment ... |
| Anything left over? | aws resourcegroupstaggingapi get-resources --tag-filters Key=Project,Values=cea-lab |
Key limits and defaults
| Item | Value | Lesson |
|---|---|---|
| 99.9% / 99.95% / 99.99% per 30-day month | 43.2 / 21.6 / 4.3 minutes allowed downtime | Availability vocabulary |
| Series availability | Multiply the links; the chain is worse than its weakest link | Availability vocabulary |
| Capacity to survive losing one AZ | N x P / (N - 1): 3 AZs need 150% of peak, 2 AZs need 200% | Auto Scaling everywhere |
| ALB health check defaults | 30 s interval, 5 s timeout, 2 failures to mark unhealthy, 5 successes to recover | ELB for resilience |
| Deregistration delay default | 300 seconds | ELB for resilience |
| Cross-zone defaults | ALB on; NLB off by default | ELB for resilience |
| Route 53 health check | 30 s standard or 10 s fast; unhealthy when 18% or fewer checkers report healthy | Failover with Route 53 |
| Worst-case DNS failover | Check interval x threshold + TTL (30 s x 3 + 60 s = 150 s) | Failover with Route 53 |
Aurora Global rds.global_db_rpo | Minimum 20 seconds; blocks commits when lag exceeds it | Database failover |
| DynamoDB MRSC | Exactly three Regions (or two plus witness); no transactions, TTL or LSIs | Database failover |
| Vault Lock compliance mode | Grace time minimum 3 days, then immutable | AWS Backup in depth |
| Vault retention bounds | Minimum at least 1 day; maximum up to 36,500 days | AWS Backup in depth |
| Restore testing quotas | 100 plans per account, 30 selections per plan | AWS Backup in depth |
Decision rules
| If… | Then… |
|---|---|
| Surviving an AZ loss matters | Three AZs, minimum capacity already running (static stability); do not rely on scale-out during the event |
| Failure is transient | Timeout, retry with backoff and jitter inside a retry budget, then a circuit breaker |
| RTO hours, RPO hours | Backup and restore |
| RTO tens of minutes, data replicated, compute off | Pilot light |
| RTO minutes, scaled-down copy running | Warm standby |
| RTO near zero, highest cost | Multi-site active-active |
| Ledger needing exactly-once debits and credits | Single writer with a hot or warm second Region; MREC last-writer-wins is unsafe |
| Planned Region rotation or failback (Aurora Global) | Switchover (RPO zero) |
| Real Regional outage (Aurora Global) | Failover with data-loss acknowledgement |
| Human-decided Regional failover | Routing control or scripted runbook, not a probe that can flip back |
| Backups must resist deletion | Separate backup account, Vault Lock, cross-Region copy |
| First chaos experiment | Sandbox, one target, alarm stop condition, alarm currently OK |
Common exam traps
- Multi-AZ is not a backup and not DR: a bad delete replicates to the standby.
- RDS Multi-AZ standby does not serve reads in the classic single-standby setup; read replicas scale reads. Aurora readers do both.
- Cross-Region read replica promotion is one-way.
- Route 53 failover time is a lower bound: resolvers and long-lived connections ignore TTLs.
- Route 53 HTTPS health checks do not validate certificates.
- Zonal shift moves traffic away from an AZ for a limited time and needs spare capacity; it is not a Region failover.
- Reserved concurrency is both a cap and a guarantee for one Lambda function.
- Vault Lock compliance mode becomes irreversible after the grace time.
- A successful backup is not a proven restore: test restores.
- ARC Readiness Check is closed to new customers; routing controls and zonal shift are separate capabilities.
- Pilot light cannot take traffic without extra steps; warm standby can, at reduced capacity.
Cost traps
| Trap | Avoid it by |
|---|---|
| Idle DR capacity forgotten in the quarterly review | Price it with a cost model; right-size warm standby |
| Multi-Region data stores (Aurora Global, global tables) | Design-only or minutes-long lab; delete after |
| NAT gateway per AZ and load balancers left running | Tear down the same day |
| ARC clusters and fast health checks | Billed per hour or per check; keep labs to minutes |
| Cross-zone and cross-Region data transfer | Estimate the traffic; keep chatty services AZ-aware |
| Over-high autoscaling maximum | Cap from the database connection budget; alarm when at maximum |
| Backups kept forever or copied everywhere | Lifecycle rules, tiering, retention from records policy |
| ElastiCache cluster left idle | Use local Valkey in Docker for learning |
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.
Well-Architected reviews for a banking API
Run a Well-Architected review of a banking API, focusing on the Reliability pillar and the Financial Services Industry Lens, record risks in the Well-Architected Tool, and turn high-risk items into a tracked improvement plan with C# tooling.
Module 13: Microsoft-to-AWS Migration
A dedicated path for experienced .NET developers moving a Microsoft and Azure estate to AWS, with side-by-side examples for every major service. You learn how to assess a portfolio, apply the 7 Rs, port .NET Framework code, migrate SQL Server data, and plan a cut-over with a tested rollback.