AWS AWSEC2 documentation change
Summary
Restructured and expanded documentation about actions to take during system maintenance events, including clearer formatting and additional details about launching replacement instances
Security assessment
The changes are organizational and provide more detailed operational guidance for maintenance events, but do not address any specific security issues or introduce security-related content.
Diff
diff --git a/AWSEC2/latest/UserGuide/schedevents_actions_maintenance.md index 3f6d9e375..e3a43a217 100644 --- a/AWSEC2/latest/UserGuide/schedevents_actions_maintenance.md +++ b/AWSEC2/latest/UserGuide/schedevents_actions_maintenance.md @@ -4,0 +5,2 @@ +Actions you can take + @@ -17,0 +20,2 @@ After your instance has rebooted (this normally takes a few minutes), verify tha +## Actions you can take + @@ -20 +24 @@ After your instance has rebooted (this normally takes a few minutes), verify tha -You can take one of the following actions: +When you receive a `system-maintenance` event notification, you can take one of the following actions: @@ -22 +26 @@ You can take one of the following actions: - * You can wait for the maintenance to occur as scheduled. + * **Wait for scheduled maintenance:** You can wait for the maintenance to occur as scheduled. @@ -24 +28 @@ You can take one of the following actions: - * You can stop and start the instance, which migrates it to a new host. This is not the same as rebooting the instance. For more information, see [Stop and start Amazon EC2 instances](./Stop_Start.html). + * **Perform manual stop and stop:** You can stop and start the instance, which migrates it to a new host. This is not the same as rebooting the instance. For more information, see [Stop and start Amazon EC2 instances](./Stop_Start.html). @@ -26 +30 @@ You can take one of the following actions: - * You can automate an immediate stop and start in response to a scheduled maintenance event. For more information, see [Running operations on EC2 instances automatically in response to events in AWS Health](https://docs.aws.amazon.com/health/latest/ug/automating-instance-actions.html) in the _AWS Health User Guide_. + * **Automate stop and start:** You can automate an immediate stop and start in response to a scheduled maintenance event. For more information, see [Running operations on EC2 instances automatically in response to events in AWS Health](https://docs.aws.amazon.com/health/latest/ug/automating-instance-actions.html) in the _AWS Health User Guide_. @@ -33 +37,7 @@ You can take one of the following actions: -You can take one of the following actions: +When you receive a `system-maintenance` event notification, you can take one of the following actions: + + * **Wait for scheduled maintenance:** You can wait for the maintenance to occur as scheduled. + + * **Launch a replacement instance:** If you want to maintain normal operation during the scheduled maintenance window: + + 1. Launch a replacement instance from your most recent AMI. @@ -35 +45 @@ You can take one of the following actions: - * You can wait for the maintenance to occur as scheduled. + 2. Migrate all necessary data to the replacement instance before the scheduled maintenance window. @@ -37 +47 @@ You can take one of the following actions: - * If you want to maintain normal operation during a scheduled maintenance window, you can launch a replacement instance from your most recent AMI, migrate all necessary data to the replacement instance before the scheduled maintenance window, and then terminate the original instance. + 3. Terminate the original instance.