1/3 checks passed for Ec2

Hi pratiksha

If your EC2 instance has 1/3 checks passed, it means that one out of three health checks performed by Amazon Web Services (AWS) is passing, while the other two are failing.

The three health checks are:

1. Instance status check: This checks the instance's underlying hardware and hypervisor for any issues.
2. System status check: This checks the instance's operating system and software for any issues.
3. Reachability check: This checks if the instance is reachable from the internet.

To identify the failing checks, follow these steps:

1. Log in to the AWS Management Console.
2. Navigate to the EC2 dashboard.
3. Select the instance with the issue.
4. Click on the "Status checks" tab.
5. Look for the checks that are failing and investigate the corresponding issues.

Common causes of failed health checks include:

• Network connectivity issues
• Instance configuration problems
• Software or operating system issues
• Resource constraints (e.g., CPU, memory, or disk space)

Once you identify the root cause, you can take corrective action to resolve the issue and get your instance back to a healthy state.

Hi Pratiksha,

Please go through the below steps and its documentation links, I hope it will helps solve your issue.

1. Understanding EC2 Status Checks

AWS EC2 instances perform status checks to monitor the health of the instance. These checks ensure that the instance is running correctly and that it can communicate with AWS infrastructure. The typical status checks include:

System Status Check:

• This check monitors the AWS infrastructure that your instance runs on. It includes checks on network connectivity, power, and physical hardware.
• Failure of this check usually means there’s an issue on AWS's side, and typically you may need to stop and start the instance to move it to a new host.

Instance Status Check:

• This check monitors the software and network configuration of the instance. It looks for issues like misconfigured networking, software errors, or excessive CPU usage.
• Failure of this check usually indicates a problem with the instance itself, which might require you to troubleshoot the operating system or application.

3rd Check - Nitro Hypervisor Check (if applicable):

• For Nitro-based instances, an additional check is sometimes performed to ensure the health of the underlying Nitro hypervisor.
• Failure here may indicate a problem specific to the Nitro-based hardware.

Documentation:

https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/monitoring-system-instance-status-check.html

2. Why You Might See 1/3 Checks Passed

If you're seeing "1/3 checks passed," this could indicate the following:

System Status Check Failure:

• The AWS infrastructure hosting your instance might have encountered an issue, causing the system status check to fail.

Instance Status Check Failure:

• There could be a problem within the instance itself, such as a software misconfiguration or a critical error.

Nitro Hypervisor Check (if applicable):

• On Nitro-based instances, a failure here might indicate an issue with the hypervisor layer.

3. Troubleshooting Steps

a. Review Instance Status

• Check the Instance Status in the AWS Management Console under the EC2 dashboard. The status checks section will provide specific information about which check failed.

b. Examine System Logs

• Review the instance system logs to identify potential causes of the failure. This might include software errors, kernel panics, or other critical failures.

Documentation:

https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/connect-linux-inst-ssh.html#Console-output

c. Consider Stopping and Restarting the Instance

• If the issue is with the underlying host, stopping and starting the instance might move it to new hardware, potentially resolving the issue.

d. Create an AMI and Launch a New Instance

• If troubleshooting doesn’t resolve the issue, consider creating an Amazon Machine Image (AMI) of the instance and launching a new instance from that AMI.

4. When to Contact AWS Support

• If the issue persists and you're unable to resolve the failed status check, it might be necessary to contact AWS Support. They can provide more detailed diagnostics and assist with issues related to AWS infrastructure.

Documentation:

https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AMIs.html

https://aws.amazon.com/premiumsupport/