X
Lab complete!
Now that you have completed this lab, make sure to update your Well-Architected review if you have implemented these changes in your workload.
Click here to access the Well-Architected Tool
EC2
Update Launch Configuration and Auto Scaling Group (ASG)
1.1 Click CloudFormation Stacks to navigate to the dashboard in the N. California (us-west-1) region.
1.2 Select the warm-secondary stack and click Update.
1.3 Chose Use current template and click Next to continue.
1.4 Update the IsPromote parameter to yes and click Next to continue.
1.5 Scroll to the bottom of the page, click the checkbox to acknowledge IAM role creation, and then click Update stack.
Auto Scaling Group (ASG)
The following changes were made when we updated our CloudFormation template:
- Launch Configuration was modified in order to connect our application to the newly promoted Aurora cluster.
- Auto Scaling Group was modified in order to scale out our EC2 capacity from 1 instance to 2 instances to match our primary region N. Virginia (us-east-1) EC2 capacity.
We can now be confident that when we failover, our secondary region N. California (us-west-1) can handle production level request traffic.
2.1 Click Auto Scaling Groups to navigate to the dashboard in the N. California (us-west-1) region.
2.2 Click on the warm-secondary-WebServerGroup-xxx link.
2.3 Click the Activity link, then scroll down to the Activity History section. You should see the existing instance terminated in response to the Launch Configuration update and two instances launching in response to the Auto Scaling Group update.
