Tear down this lab

If you are attending an in-person workshop and were provided with an AWS account by the instructor:

• There is no need to tear down the lab. Feel free to continue exploring. Log out of your AWS account when done.

If you are using your own AWS account:

• You may leave these resources deployed for as long as you want. When you are ready to delete these resources, see the following instructions

Remove AWS CloudFormation provisioned resources

How to delete an AWS CloudFormation stack

If you are already familiar with how to delete an AWS CloudFormation stack, then skip to the next section: Delete workshop CloudFormation stacks

1. Go to the AWS CloudFormation console: https://console.aws.amazon.com/cloudformation
2. Select the CloudFormation stack to delete and click Delete
3. In the confirmation dialog, click Delete stack
4. The Status changes to DELETE_IN_PROGRESS
5. Click the refresh button to update and status will ultimately progress to DELETE_COMPLETE
6. When complete, the stack will no longer be displayed. To see deleted stacks use the drop down next to the Filter text box.
7. To see progress during stack deletion
   • Click the stack name
   • Select the Events column
   • Refresh to see new events

Delete workshop CloudFormation stacks

1. First delete the HealthCheckLab CloudFormation stack
2. Wait for the HealthCheckLab CloudFormation stack to complete (it will no longer be shown on the list of actice stacks)
3. Then delete the WebApp1-VPC CloudFormation stack

Remove CloudWatch logs

After deletion of the WebApp1-VPC CloudFormation stack is complete then delete the CloudWatch Logs:

1. Open the CloudFormation console at https://console.aws.amazon.com/cloudwatch/.
2. Click Logs in the left navigation.
3. Click the radio button on the left of the WebApp1-VPC-VPCFlowLogGroup-<some unique ID>.
4. Click the Actions Button then click Delete Log Group.
5. Verify the log group name then click Yes, Delete.

---

References & useful resources

• Patterns for Resilient Architecture — Part 3
• Amazon Builders' Library: Implementing health checks
• Well-Architected Framework (see the Reliability pillar)
• Well-Architected best practices for reliability
• Health Checks for Your Target Groups (for your Application Load Balancer)

With completion of this lab you have learned several best practices. Consider how you can implement these, and update the Well-Architected Review for your workloads: REL 5 How do you design interactions in a distributed system to mitigate or withstand failures? REL 11 How do you design your workload to withstand component failures?.