Re: Near term AWS maintenance event - no way to manually relaunch? JustinC@AWS Posted by: Posted on: Sep 25, 2014 9:30 AM in response to: tellapart Reply



We will share more information as soon as it becomes available.



An important note about stopping/starting instances: this will exchange your machine instance with another randomly selected machine instance. It is not guaranteed that the replacement will already be patched. For this reason, launching new machines or stop/starting machines is not a recommended way to avoid the scheduled reboot.



The Scheduled Events view in the Console is eventually consistent, and may take some time to display new instances properly. Therefore a newly launched or newly stop/started machine will always show that it has no scheduled reboots, when it first comes up, even if one is already scheduled. Newly launched instances for which reboots have already been scheduled will appear in Scheduled Events after a time, but not immediately. We realize that this is not an ideal experience, and as Doug mentioned we are working on a better way for you to confirm which instances are patched.



In the meantime, if you launch new instances or replace instances, and you are concerned about the impact of a scheduled reboot to them, then you may wish to check the Scheduled Events page periodically.



If you wish to test the behavior of your system under reboot to verify that you can shut down and come back up gracefully, then you can trigger a reboot through the



Hope this helps,

Justin C. Hello,We will share more information as soon as it becomes available.An important note about stopping/starting instances: this will exchange your machine instance with another randomly selected machine instance. It is not guaranteed that the replacement will already be patched. For this reason, launching new machines or stop/starting machines is not a recommended way to avoid the scheduled reboot.The Scheduled Events view in the Console is eventually consistent, and may take some time to display new instances properly. Therefore a newly launched or newly stop/started machine will always show that it has no scheduled reboots, when it first comes up, even if one is already scheduled. Newly launched instances for which reboots have already been scheduled will appear in Scheduled Events after a time, but not immediately. We realize that this is not an ideal experience, and as Doug mentioned we are working on a better way for you to confirm which instances are patched.In the meantime, if you launch new instances or replace instances, and you are concerned about the impact of a scheduled reboot to them, then you may wish to check the Scheduled Events page periodically.If you wish to test the behavior of your system under reboot to verify that you can shut down and come back up gracefully, then you can trigger a reboot through the EC2 Console or with the API RebootInstances Hope this helps,Justin C.