AWS AWSEC2 documentation change
Summary
Restructured and updated documentation about EC2 instance reboot events, including clearer distinctions between instance-reboot and system-reboot types, actions users can take, and post-reboot behavior. Added details about alternative options for handling reboot events.
Security assessment
The changes focus on improving clarity and organization of reboot event documentation, including user actions and system behavior. There is no mention of security vulnerabilities, patches, or security-related features in the changes.
Diff
diff --git a/AWSEC2/latest/UserGuide/schedevents_actions_reboot.md index 912c0607e..e36022888 100644 --- a/AWSEC2/latest/UserGuide/schedevents_actions_reboot.md +++ b/AWSEC2/latest/UserGuide/schedevents_actions_reboot.md @@ -5 +5 @@ -View the reboot event type +Actions you can take @@ -9 +9 @@ View the reboot event type -When AWS must perform tasks such as installing updates or maintaining the underlying host, it can schedule a reboot for the instance or the underlying host. You can [reschedule most reboot events](./reschedule-event.html) so that your instance is rebooted at a specific date and time that suits you. +When AWS must perform tasks such as installing updates or maintaining the underlying host, it can schedule an instance reboot. During the scheduled reboot, the instance either stays on the same host, or migrates to a different host, depending on the event type, as follows: @@ -11 +11 @@ When AWS must perform tasks such as installing updates or maintaining the underl -## View the reboot event type + * `instance-reboot` @@ -13 +13 @@ When AWS must perform tasks such as installing updates or maintaining the underl -You can view whether a reboot event is an instance reboot or a system reboot by using one of the following methods. + * During the reboot, the instance remains on the host. This is known as an _in-place reboot_. @@ -15 +15 @@ You can view whether a reboot event is an instance reboot or a system reboot by -Console + * During the reboot, the host undergoes maintenance. @@ -16,0 +17 @@ Console + * Typically completes in seconds. @@ -18 +19 @@ Console -###### To view the type of scheduled reboot event + * `system-reboot` @@ -20 +21 @@ Console - 1. Open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/). + * During the reboot, the instance is migrated to a new host. This is known as a _reboot migration_. @@ -22 +23 @@ Console - 2. In the navigation pane, choose **Events**. + * Typically completes in minutes. @@ -24 +24,0 @@ Console - 3. Choose **Resource type: instance** from the filter list. @@ -26 +25,0 @@ Console - 4. For each instance, view the value in the **Event type** column. The value is either **system-reboot** or **instance-reboot**. @@ -28,0 +28 @@ Console +To check what type of event is scheduled for your instance, see [Determine the event type](./monitoring-instances-status-check_sched.html#scheduled-event-type). @@ -29,0 +30 @@ Console +## Actions you can take @@ -31 +32 @@ Console -AWS CLI +When you receive a scheduled `instance-reboot` or `system-reboot` event notification, you can take one of the following actions: @@ -32,0 +34 @@ AWS CLI + * **Wait for scheduled reboot:** You can wait for the instance reboot to occur within its scheduled maintenance window. @@ -34 +36 @@ AWS CLI -###### To view the type of scheduled reboot event + * **Reschedule the reboot:** You can [reschedule](./reschedule-event.html) the instance reboot to a date and time that suits you. @@ -36 +38 @@ AWS CLI -Use the [describe-instance-status](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ec2/describe-instance-status.html) command. + * **Perform manual reboot:** You can manually [reboot](./ec2-instance-reboot.html) the instance yourself at a time that suits you. However, with a manual reboot, your instance remains on the current hardware (in-place reboot), no host maintenance takes place, and the event stays open. @@ -39,2 +40,0 @@ Use the [describe-instance-status](https://awscli.amazonaws.com/v2/documentation - aws ec2 describe-instance-status \ - --instance-id i-1234567890abcdef0 @@ -42 +41,0 @@ Use the [describe-instance-status](https://awscli.amazonaws.com/v2/documentation -For scheduled reboot events, the value for `Code` is either `system-reboot` or `instance-reboot`. The following example output shows a `system-reboot` event. @@ -43,0 +43 @@ For scheduled reboot events, the value for `Code` is either `system-reboot` or ` +**After AWS reboots your instance** @@ -45,12 +45 @@ For scheduled reboot events, the value for `Code` is either `system-reboot` or ` - [ - "Events": [ - { - "InstanceEventId": "instance-event-0d59937288b749b32", - "Code": "system-reboot", - "Description": "The instance is scheduled for a reboot", - "NotAfter": "2019-03-14T22:00:00.000Z", - "NotBefore": "2019-03-14T20:00:00.000Z", - "NotBeforeDeadline": "2019-04-05T11:00:00.000Z" - } - ] - ] +The following applies after AWS reboots your instance: @@ -58 +47 @@ For scheduled reboot events, the value for `Code` is either `system-reboot` or ` -###### Actions you can take for instance reboot + * The scheduled event is cleared. @@ -60 +49 @@ For scheduled reboot events, the value for `Code` is either `system-reboot` or ` -When you receive a scheduled instance reboot event notification, you can take one of the following actions: + * The event description is updated. @@ -62 +51 @@ When you receive a scheduled instance reboot event notification, you can take on - * You can wait for the instance reboot to occur within its scheduled maintenance window. + * For an `instance-reboot` event: @@ -64 +53 @@ When you receive a scheduled instance reboot event notification, you can take on - * You can [reschedule](./reschedule-event.html) the instance reboot to a date and time that suits you. + * Maintenance of the underlying host is complete. @@ -65,0 +55 @@ When you receive a scheduled instance reboot event notification, you can take on + * For a `system-reboot` event: @@ -66,0 +57 @@ When you receive a scheduled instance reboot event notification, you can take on + * The instance moves to a new host. @@ -67,0 +59 @@ When you receive a scheduled instance reboot event notification, you can take on + * The instance retains its IP address and DNS name. @@ -69 +61 @@ When you receive a scheduled instance reboot event notification, you can take on -After your instance is rebooted, the scheduled event is cleared and the event's description is updated. The pending maintenance to the underlying host is completed, and you can begin using your instance again after it has fully booted. + * Any data on local instance store volumes is preserved. @@ -71 +63 @@ After your instance is rebooted, the scheduled event is cleared and the event's -You can [reboot](./ec2-instance-reboot.html) the instance yourself at a time that is convenient for you. However, this does not clear the scheduled event. Only a reboot performed by AWS will clear the event. + * You can use your instance after it has fully booted. @@ -73 +64,0 @@ You can [reboot](./ec2-instance-reboot.html) the instance yourself at a time tha -###### Actions you can take for system reboot @@ -75 +65,0 @@ You can [reboot](./ec2-instance-reboot.html) the instance yourself at a time tha -When you receive a scheduled system reboot event notification, you can take one of the following actions: @@ -77 +66,0 @@ When you receive a scheduled system reboot event notification, you can take one - * It is not possible for you to reboot the system yourself. @@ -79 +68 @@ When you receive a scheduled system reboot event notification, you can take one - * You can wait for the system reboot to occur during its scheduled maintenance window. +**Alternative options** @@ -81 +70 @@ When you receive a scheduled system reboot event notification, you can take one - * You can [reschedule](./reschedule-event.html) the system reboot to a date and time that suits you. +If you can't reschedule the reboot event, but want to maintain normal operation during the scheduled maintenance window, you can do the following: @@ -83 +72 @@ When you receive a scheduled system reboot event notification, you can take one -A system reboot typically completes in a matter of minutes. After the system reboot has occurred, the instance retains its IP address and DNS name, and any data on local instance store volumes is preserved. After the system reboot is complete, the scheduled event for the instance is cleared, and you can verify that the software on your instance is operating as expected. + * **For an instance with an EBS root volume** @@ -84,0 +74 @@ A system reboot typically completes in a matter of minutes. After the system reb + * Manually stop and start the instance to migrate it to a new host. This is not the same as manually rebooting the instance, where the instance stays on the same host. @@ -85,0 +76 @@ A system reboot typically completes in a matter of minutes. After the system reb + * Optionally, automate an immediate instance stop and start in response to the scheduled reboot 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_. @@ -86,0 +78 @@ A system reboot typically completes in a matter of minutes. After the system reb +###### Important @@ -88 +80 @@ A system reboot typically completes in a matter of minutes. After the system reb -If you're unable to reschedule the system reboot, but need to maintain the instance at a different time, you can do the following: +The data on instance store volumes is lost when an instance is stopped. For more information, see [Stop and start Amazon EC2 instances](./Stop_Start.html). @@ -90 +82 @@ If you're unable to reschedule the system reboot, but need to maintain the insta - * For an instance with an EBS root volume, you can stop and start the instance. This is not the same as rebooting the instance. This migrates the instance to a new host. However, the data on the local instance store volumes is not preserved. For more information, see [Stop and start Amazon EC2 instances](./Stop_Start.html). + * **For an instance with an instance store root volume** @@ -92 +84 @@ If you're unable to reschedule the system reboot, but need to maintain the insta - * You can also automate an immediate instance stop and start in response to a scheduled system reboot 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_. + 1. Launch a replacement instance from your most recent AMI. @@ -94 +86,3 @@ If you're unable to reschedule the system reboot, but need to maintain the insta - * For an instance with an instance store root volume, 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. + 2. Migrate all necessary data to the replacement instance before the scheduled maintenance window. + + 3. Terminate the original instance.