Hello AWS Community,
I recently received the following notification regarding my Amazon Lightsail instance:
"One or more of your Amazon Lightsail instances is scheduled for maintenance on Mon, 20 May 2024 00:00:00 GMT. Maintenance activity will result in the affected Lightsail instance(s) becoming unavailable and then rebooted."
The timing of this maintenance coincides with a peak period for my service, which leads me to anticipate significant disruptions. In searching for solutions, I found discussions suggesting that a manual restart of the instance prior to the scheduled maintenance might preemptively trigger the necessary migrations, thereby avoiding downtime during the planned maintenance window. Relevant discussions were found in links such as https://repost.aws/questions/QU7AeM4HfTTbOOpeSfyj5DRg/aws-lightsail-maintenance , https://repost.aws/questions/QURJrmxf21TMqRI5qrkS0B8A/how-frequently-should-i-expect-scheduled-maintenance-for-amazon-lightsail-instances, and https://repost.aws/questions/QUYRCzrCbRR-SAFxwY92zLug/lightsail-instance-maintenance.
I am concerned that these solutions might not be universally applicable but specific to certain types of maintenance, which is why I am querying whether they are applicable to this particular maintenance event. Since the notification did not mention the possibility of such a preemptive action, I am also concerned about whether a manual restart would effectively address the issue or might instead result in an unnecessary additional reboot.
Could anyone confirm if preemptively restarting the instance is a recommended action in this scenario? Any guidance or additional recommendations would be greatly appreciated.
Thank you for your attention.
AWS OFFICIALUpdated a year ago
Hi, thank you for your answer. Yesterday, on the dashboard, I manually stopped the instance. After the instance had been stopped, I manually started it again. However, on today's AWS health dashboard, there's still an "Upcoming" event labeled "Lightsail instance maintenance scheduled". Does this mean the stop-start procedure didn't work?
The AWS health dashboard event unfortunately doesn't pickup the manual stop-start and hence shows the maintenance event as upcoming - but it won't actually cause action on 5/20 anymore. Your stop-start action has taken effect.