Why is my EC2 Windows instance down with a system status check failure or status check 0/2?

Last updated: 2019-08-28

My Amazon Elastic Compute Cloud (Amazon EC2) Windows instance went down suddenly and is no longer reachable. The system status check or both status checks failed. What happened, and how can I fix this? 

Short Description

Amazon Web Services (AWS) monitors the health of each EC2 instance with two status checks. An EC2 instance becomes unreachable if a status check fails. A system status check failure indicates a problem with the AWS systems that your instance runs on. When a problem with an underlying host impacts your production, you can stop and start your instance to migrate from the underlying host.

Resolution

First, check the AWS Service Health Dashboard for outage and status updates to confirm if the problem is on the AWS side.

If there is no outage, follow these steps:

Warning: Before you stop an instance, be aware of the following:

  • If you're not using an Elastic IP Address, the public IP address is released when you stop the instance.
  • If this instance has an instance store volume, any data on it is lost when the instance is stopped.
  • If the instance shutdown behavior is set to Terminate, the instance terminates when it is stopped.
  • If the instance is part of an Auto Scaling group, first detach the instance from the Auto Scaling Group. After you stop and start the instance, attach the instance back to the Auto Scaling group.

For more information, see Stop and Start Your Instance.

  1. Stop the instance.
    Note: If the instance becomes stuck in the stopping state, force the instance to stop using the console or AWS Command Line Interface (AWS CLI). This action can take up to 10 minutes. For more information, see Troubleshooting Stopping Your Instance.
  2. Start the instance. In most cases, the instance starts on a new healthy underlying host server.

Tip: You can create an Amazon CloudWatch alarm to monitor and automatically recover your EC2 Windows instance if it goes down due to a system status check failure. For more information, see Recover Your Instance.