![\"System](\"https:\/\/vticloud.io\/wp-content\/uploads\/2021\/02\/1.png\")
<\/p>\n<\/p>\n
Inside Amazon EC2, there are two types of status check: System Status Checks and Instance Status Checks.<\/p>\n
Errors in these will indicate different issues, and you should recover from them differently.<\/p>\n
This topic discusses the System and Instance Status Checks and how to recover from these checks.<\/p>\n
<\/p>\n
<\/p>\n
The System Status Checks monitor all the AWS systems that your instances run on. So this includes all of the back-end, networking, power, hypervisor, and everything else that you as a customer don\u2019t have access to in the Shared responsibility model.<\/p>\n
So some of the reasons that you might see a failure in the System Status Checks are:<\/p>\n
Loss of network connectivity<\/p>\n<\/li>\n<\/ul>\n
Loss of system power<\/p>\n<\/li>\n<\/ul>\n
Software issues on physical host<\/p>\n<\/li>\n<\/ul>\n
Hardware issues on the physical host that impact network reachability<\/p>\n<\/li>\n<\/ul>\n
If there\u2019s a failure because of a loss of network connectivity, or power, there\u2019s really nothing we can do about it because AWS will have to correct that themselves.<\/p>\n
However, we can resolve failures in a couple of ways:<\/p>\n
For EBS-Backed instances, we can stop and start instance to obtain new hardware<\/p>\n<\/li>\n
For instance store-backed instances, we have to terminate and replace the instance to place on new hardware. Remember, we can\u2019t stop instance store volumes so that data will be lost unless you\u2019ve previously backed it up.<\/p>\n<\/li>\n<\/ul>\n
<\/p>\n
![\"Instance](\"https:\/\/vticloud.io\/wp-content\/uploads\/2021\/02\/2.png\")
<\/p>\n
For Instance Status Checks, these are the things that we do have control over. It\u2019ll monitor the networking software configuration on an instance, you have to intervene yourself to fix any issues.<\/p>\n
And some of the reasons for failures might be:<\/p>\n
Failed system status checks<\/p>\n<\/li>\n<\/ul>\n
Incorrect networking or startup configuration<\/p>\n<\/li>\n<\/ul>\n
Exhausted memory<\/p>\n<\/li>\n<\/ul>\n
Corrupted file system<\/p>\n<\/li>\n<\/ul>\n
Incompatible kernel<\/p>\n<\/li>\n<\/ul>\n
To resolve any of these issues, you will have to make instance configuration changes or potentially reboot the instance.<\/p>\n
<\/p>\n
We can also perform the same status checks from the AWS command line interface (CLI).<\/p>\n
Here we can invoke:<\/p>\n
![\"EC2](\"https:\/\/vticloud.io\/wp-content\/uploads\/2021\/02\/3.png\")
<\/p>\n![\"EC2](\"https:\/\/vticloud.io\/wp-content\/uploads\/2021\/02\/4.png\")
<\/p>\n![\"EC2](\"https:\/\/vticloud.io\/wp-content\/uploads\/2021\/02\/5.png\")
<\/p>\n![\"EC2](\"https:\/\/vticloud.io\/wp-content\/uploads\/2021\/02\/6.png\")
<\/p>\n