Gurkamal helps you troubleshoot
failed system reachability
status checks

gurkamal_instance_fails_reachability_status

My Amazon Elastic Compute Cloud (Amazon EC2) instance has failed the system reachability status check.

If a system reachability status check fails for your instance, you can try one or more of the following actions:

  • For an instance that's using an Amazon Elastic Block Store (Amazon EBS) backed AMI, stop and restart the instance. If the instance seems to be stuck in the stopping state, see Troubleshooting Stopping Your Instance.
  • For an instance that's using an instance store-backed AMI, terminate the instance, and then launch a replacement.
  • Wait for Amazon EC2 to resolve the issue. Allow at least 30 minutes.
  • Open a Support case by using the link on the Support for Health Checks page.

To recover an EC2 instance automatically

You can create an Amazon CloudWatch alarm that monitors your Amazon EC2 instance status checks and then automatically recovers the instance if that instance becomes impaired.

However, the following must be true:

  • The instance must use only Amazon EBS volumes.
  • The instance must not have any instance store volumes attached.
  • The instance must be one of the instance types that are supported for the recover action.

For more information, see Adding Recover Actions to Amazon CloudWatch Alarms.


Did this page help you? Yes | No

Back to the AWS Support Knowledge Center

Need help? Visit the AWS Support Center.

Published: 2014-07-03

Updated: 2019-01-18