- Newest
- Most votes
- Most comments
Hi,
Based on the fact that t2 and t3 instance types use different virtualisation (t2 uses Xen, t3 uses Nitro) I suspect the issue may be the ENA driver.
If you changed the instance type to an instance built on the Nitro System, status checks fail if you migrated from an instance that does not have the required ENA and NVMe drivers. For more information, see https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/resize-limitations.html. However, you mentioned that is was working fine until in the last 2 weeks but it is not the problem that you encounter daily.
For more information on the ENA driver on Red Hat, see [this](How do I install and activate the latest ENA driver for enhanced network support on an Amazon EC2 instance running Red Hat 6/7?) on how to install and activate the latest ENA driver.
The following documents will help you to troubleshoot the instance status check fails. [1]https://aws.amazon.com/premiumsupport/knowledge-center/ec2-linux-status-check-failure-os-errors/ [2] https://aws.amazon.com/premiumsupport/knowledge-center/ec2-linux-status-check-failure/
I hope the above information is helpful. Kindly let me know if you have additional concerns.
Thank you.
Relevant content
- asked 6 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 5 days ago
- AWS OFFICIALUpdated a year ago
aws ec2 describe-instances --instance-ids i-xxxxxxx --query "Reservations[].Instances[].EnaSupport" comes TRUE