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?

질문됨 3달 전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.

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠