Keep checkout alive through an AZ failure
Try this labAll SAA-C03 practice
- Certification
- SAA-C03
- Format
- Artifact workspace
- Difficulty
- medium
- Estimated time
- 18 min
- Automated checks
- 9
SCENARIO
Checkout disappeared when one Availability Zone failed. The stack already has a load balancer and an Auto Scaling group, but both are pinned to the same zone and instance replacement only notices EC2 failures.
TASK
Repair checkout-stack.yaml so the load balancer and Auto Scaling group span both supplied zones and replace unhealthy application instances after a 120-second startup grace period.
- The application reports healthy at
/healthwith HTTP200; keep minimum and desired capacity 2 and maximum 4. - Preserve the network, traffic path, security groups, and private-only instances.