1 Answer
- Newest
- Most votes
- Most comments
0
Hello,
I understand that you did not find any answer with the common problems and solutions. Actually there are many problems that could cause what you are telling us, in which case I give you some more options:
- Validate which check status you have the error:
- If we have the System status checks, in which you would have to wait for AWS to fix the error or try to redeploy the instance, it is very likely that the problem is an underlying hardware error (since it would be within its scope according to with the responsibility model).
- If we have an error at the Instances status check level, the error can generally come from the operating systems or network level, although there are also changes such as a resize of the instance size that could cause this problem, here you can go ahead with the step
Docs: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/monitoring-system-instance-status-check.html
- Here I recommend you go in this sequence:
- Check the latest changes made to the instances.
- Validates if these changes were able to affect the behavior of the instance.
- Using the Monitoring options, validate the status of the instance in Actions, Monitor and troubleshoot, Get system log and in Monitor and troubleshoot, Get Instances Screenshoot if you find any errors at the operating system level. In Get system log you could get an error log at the time of boot (disk error, memory, etc) and in Get Instances Screenshoot you could visually verify it in an image of the terminal, from the error look for the solution. If you wish, you can share the logs that appear in the console with us.
Docs: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html
Greetings.
answered 3 years ago
Relevant content
- asked 3 years ago
- asked 2 years ago
