Received degradation notice. Restarted instance during outage window. AWS Rebooted it anyway

0

We receive hardware degradation notices periodically, and always try to restart the host ourselves to migrate it before AWS doe it autonomously. We did a restart on one last weekend, and today, AWS rebooted the host anyway. The notice states

  • What will happen when I stop and start the instance? You can stop and start the instance at any time before the scheduled start time of the scheduled reboot event. This will migrate the instance to a new host and the instance will not have to undergo the scheduled maintenance.

Why then, if we had already stopped and started the instance, would it perform the maintenance anyway?

已提问 2 个月前95 查看次数
1 回答
1
已接受的回答

Sorry to hear that. Did you check to confirm the description of the scheduled events changed to [Completed] after you manually reboot the instance before the scheduled reboot? It could be possible that the manual reboot didn't clear the scheduled event or another reboot is required. Here is more detail how to react to scheduled events for instances.

profile pictureAWS
专家
已回答 2 个月前
profile picture
专家
已审核 2 个月前
profile picture
专家
已审核 2 个月前
  • thanks, useful detail in the documentation. Did not realize we could confirm the 'Completion' of the event based on our action. Its never been a problem before, but the unplanned reboot resulted in disruption to a number of our customers, so naturally there was some consternation.

您未登录。 登录 发布回答。

一个好的回答可以清楚地解答问题和提供建设性反馈,并能促进提问者的职业发展。

回答问题的准则