- Newest
- Most votes
- Most comments
Hello JGS nim,
Here are some common problems that can cause instance status check failures [1]:
System status check failure
Incorrect networking or startup configuration
Exhausted memory
File system damage
Incompatible kernel
After reviewing the logs you provided, it appears the issue is related to a network configuration problem, as indicated by the following error:
dial tcp 169.254.169.254:80: connect: network is unreachable
This could be due to resource exhaustion in the operating system or other factors, but a full review of the operating system logs would be required to pinpoint the exact cause.
If you need further analysis, I recommend opening a support case with AWS Support, as they can conduct a more detailed investigation. The re:Post community has limited capabilities in this regard.
For common issues related to instance status checks, the documentation [2] provides helpful information.
If this response was helpful, I would appreciate if you could acknowledge it in the community to help improve the service.
Thank you.
Reference Documents:
[1] Monitoring System Instance Status Checks - Instance Status Checks
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/monitoring-system-instance-status-check.html#instance-status-checks
[2] Troubleshooting Instances with Failed Status Checks
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html
AWS Support – 한국어 고객 및 기술 지원 서비스 시작
https://aws.amazon.com/ko/blogs/korea/choose-korean-in-aws-support-as-your-preferred-language/
re:Post 에서 한국어 지원을 원하시면 언어 선택을 "Korean" 으로 하시면 지원 가능합니다.
Relevant content
- Accepted Answerasked a year ago
- asked 3 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 4 months ago