By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

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?

Topics
Compute
Tags
Amazon EC2
Language
English
Thomas Spitzer
asked 2 months ago86 views
1 Answer
1
Accepted Answer

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
EXPERT
AWS-User-alantam
answered 2 months ago
profile picture
EXPERT
Oleksii Bebych
reviewed a month ago
profile picture
EXPERT
Riku_Kobayashi
reviewed 2 months ago
  • Thomas Spitzer
    2 months ago

    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.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions

Relevant content