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, as follows:
-
instance-rebootevent-
During the reboot, the instance remains on the host. This is known as an in-place reboot.
-
During the reboot, the host undergoes maintenance.
-
Typically completes in seconds.
-
-
system-rebootevent-
During the reboot, the instance is migrated to a new host. This is known as a reboot migration.
-
Typically completes in minutes.
-
To check what type of event is scheduled for your instance, see Determine the event type.
Actions you
can take
When you receive a scheduled instance-reboot or
system-reboot event notification, you can take one of the
following actions:
-
Wait for scheduled reboot: You can wait for the instance reboot to occur within its scheduled maintenance window.
-
Reschedule the reboot: You can reschedule the instance reboot to a date and time that suits you.
-
Perform manual reboot: You can manually reboot 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.
After AWS reboots your instance
The following applies after AWS reboots your instance:
-
The scheduled event is cleared.
-
The event description is updated.
-
For an
instance-rebootevent:-
Maintenance of the underlying host is complete.
-
-
For a
system-rebootevent:-
The instance moves to a new host.
-
The instance retains its IP address and DNS name.
-
Any data on local instance store volumes is preserved.
-
-
You can use your instance after it has fully booted.
Alternative options
If you can't reschedule the reboot event, but want to maintain normal operation during the scheduled maintenance window, you can do the following:
-
For an instance with an EBS root volume
-
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.
-
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 in the AWS Health User Guide.
Important
The data on instance store volumes is lost when an instance is stopped. For more information, see Stop and start Amazon EC2 instances.
-
-
For an instance with an instance store root volume
-
Launch a replacement instance from your most recent AMI.
-
Migrate all necessary data to the replacement instance before the scheduled maintenance window.
-
Terminate the original instance.
-
