A review lab in sixteen slides, with nothing built: read the project's final architecture and fill in its inventory; design its disaster recovery in us-west-2 for two targets (RPO and RTO 24 hours, then 1 minute and 15 minutes) and price both with the AWS Pricing Calculator; read the bill by service and by the tag project with aws ce, and the backups with aws backup; review the project against the six pillars, record it in the Well-Architected Tool, and present three improvements. Each worksheet has a worked reference answer.
The slides
The tool is a lab in sixteen slides, one step each, with the steps to follow beside a worksheet or a terminal; under
each worksheet is a reference answer, closed until the team has filled the table:
- Introduction: the project as the course built it.
- 1. The project
- Read the project's architecture: its parts by tier, and the session that built each.
- Fill in the inventory: the data each part holds, and its copy today.
- 2. DR at two targets
- Read the two targets: RPO and RTO 24 hours; RPO 1 minute and RTO 15 minutes.
- Design DR for target A (backup and restore) and for target B (warm standby).
- 3. Price both
- Open the AWS Pricing Calculator, price design A and price design B, in us-west-2.
- 4. The bill and the backups
- Read the costs by service, read the costs by the tag project, read what AWS Backup protects.
- 5. The review
- Review the project against the six pillars, record the review in the Well-Architected Tool, and choose three improvements and present them.
- 6. Clean up: the review's workload.
The buttons on the left and right edges move between slides. So do the arrow keys and a swipe.
The slides
Disaster Recovery, Cost and the Well-Architected Framework explain everything
the lab uses.
The placeholders
The reference prices are On-Demand, us-west-2, from the AWS Price List API on 2026-11-16, for assumed sizes (a 20 GB
database, 5 GB in the bucket, 30 GB copied a month). The aws backup outputs are a real read-only run. The Cost
Explorer amounts and the Well-Architected risk counts are examples, written in the CLI's output format.
Sources