- 最新
- 最多得票
- 最多評論
Hi Alfredo,
I can confirm due to unforeseen circumstances the underlying hardware that your EC2 Instance was running on experienced a transient underlying hardware issue. As a result, it was rebooted as part of the recovery process, apologies for any inconvenience this may have caused. You can review this via the System Status Check Cloudwatch graph [1].
For future references, I would highly recommend implementing Auto Recovery for your Instances. You can automatically recover Instances when a system impairment is detected. This feature recovers the instance on different underlying hardware and reduces the need for manual intervention. More information regarding this can be found in the below documentation:
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-recover.html
In summary, the reboot was caused as part of a recovery procedure when the underlying hardware experienced a transient issue. However, since you performed a stop/start your instance was migrated to a different underlying hardware. More information about what happens when you perform a stop/start can be found below:
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Stop_Start.html#instance_stop
Regards,
LoiyAWS
[1] https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/monitoring-system-instance-status-check.html#types-of-instance-status-checks
相關內容
- 已提問 6 個月前
- 已提問 1 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前