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
As we mentioned, checking the AWS service health status before triggering the Systems Manager production change process will allow you to avoid your operational change pipeline being held up by active service events, so to proactively remediate the operational risks. With this AWS Health Aware capability, you can use Systems Manager to integrate this feature into your existing Automation Runbooks to enhance the resiliency of your operation change process.
In this lab you will take the following actions on the Change Manager:
The solution works as follows:
Click this link to validate there’s a running EC2 instance named well-architected-lab-windows-ec2.
Click this link to go to Templates tab in the Change Manager.
Select the Change Template wa-ssm-health-aware-lab-template.
Click the Create request button.
In the Basic change request details, type in a name for this request, e.g. wa-lab-change-request-normal. Then select the AWS_health_aware_normal_operation_runbook (Default) in the dropdown box under the Runbook.
Keep the other configurations as default, then scroll down to the bottom of the page and click the Next button.
Leave all parameter in the Specify parameters page as default, and click the Next button.
Review the configuration information in the Review and submit page, scroll down to the bottom of the page and click the Submit for approval button. The request has been successfully submitted when a green banner shows at the top of the page.
You will also receive an SNS email notification regarding the successful submission of the change request.
Click this link to go to the Requests tab in the Change Manager. You will find the Status of the change request will change from Scheduled, to Run in progress, and finally to Success.
Click on the Change Request wa-lab-change-request-normal.
Click on the Timeline tab in the Change Request detail page, where you can see the planned operation defined in the runbook AWS_health_aware_normal_operation_runbook has been executed, as there’s no active service events.
In case there’s active AWS service event(s) when you executed the Change Request, then you will find the operation change will be suspended, which is as expected for this AWS Health Aware operation change process. You can also visit the AWS Health Dashboard in your AWS Console to verify if there’s any active service event in that case.
Click this link to view the EC2 instance. You will find the original EC2 instance has been stopped (or still in stopping status) by the Change Manager Automation Runbook.
(Optional) Click this link to go to Documents in Systems Manager, click the Owned by me tab, and click the AWS_health_aware_normal_operation_runbook Automation runbook.
(Optional) Click the Content tab and review the automation runbook content. Please note that the current runbook is to monitor those AWS health events which status are “open”.
Now you have successfully created the change request, and completed the runbook executions.
This concludes Section 3 of this lab, click on the link below to move on to the next section to simulate the occurence of AWS service events.
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