Update from support agent-
The kernel changed and that may be the cause of the instance failing.
The question is how did it spontaneously change? Only I use it and I've only been running some Python scripts. Pretty innocuous stuff.
I noted that the Instance in question was failing Instance Status Checks but has since recovered and is now passing both Status Checks.
As noted here , Instance Status Checks monitor the software and network configuration of your individual instance. Amazon EC2 checks the health of the instance by sending an address resolution protocol (ARP) request to the ENI. Unfortunately, due to our privacy and security policy, we do not have access to our Customers' resources therefore I cannot confirm the root cause.
I would recommend reviewing your OS level logs such as /var/log/messages during the same timeframe of the issue for any errors, warnings, etc. If you have any further concerns, please let me know.
Shot self in foot. 100% my fault. I edited fstab days before the reboot and forgot.
Issue was resolved with support case.
One agent thought the kernel had changed but second agent did not agree. Commenting out the bad line in /etc/fstab resolved the issue.
Instance reachability check failedasked 2 years ago
Instance reachability check failed on ec2 ubunut 18.04asked 6 months ago
Instance reachability check failed (Linux)asked 2 years ago
Getting "Instance reachability check failed" error again and again on Ubuntu 20.04asked a month ago
Can I get email when instance reachability check failedasked 2 years ago
Instance reachability check failedasked 6 months ago
aws ec2 Instance reachability check failedasked 10 months ago
EC2 Instance Unreachable After Failed Status Checksasked 17 days ago
Instance reachability failed!asked 3 years ago
System reachability check passed Instance reachability failed!asked 4 years ago