AWS: Status Check + CloudWatch
Hello! 
Many people noticed in the EC2 console in the instance table the Status Check column. It is usually green - OK. Not once have I seen that check status faylitsya. What is a check status, what parameters does it track?
Status Check is a few autotests that the instance and the host node on which this instance runs. At the moment there are 2 check status:
')
1. System Status Check - check the status of parameters that depend on AWS. These problems are easily solved by restarting or stopping the start of the instnsa, it will move to another carrier. In general, problems can be:
2. Instance Status Check — check the status of parameters that are independent of AWS. These are usually problems associated with improper configuration and should be resolved by the administrator. Problems can be:
Looks like status checks like this:
Going into the properties of the host, you can view individual data on the instance:
From today, problems with the status of checks can be tracked automatically well and automatically make a decision. For example, you have 300 servers and keeping track of their status with checks is not an easy task, but there is a solution that can be described in a few steps:
Thus, you protect yourself from the fact that you will not use a healthy system. After an instance that has not passed the status of the checks is turned off, a new one will immediately rise instead, which is likely to be healthy.
The names of new checks in CloudWatch:
For me it is very convenient. Now you can stop worrying about one more thing.
Status Check
Many people noticed in the EC2 console in the instance table the Status Check column. It is usually green - OK. Not once have I seen that check status faylitsya. What is a check status, what parameters does it track?
Status Check is a few autotests that the instance and the host node on which this instance runs. At the moment there are 2 check status:
')
1. System Status Check - check the status of parameters that depend on AWS. These problems are easily solved by restarting or stopping the start of the instnsa, it will move to another carrier. In general, problems can be:
- lack of network resources
- nutritional deficiency
- problems with media software
- media hardware issues
2. Instance Status Check — check the status of parameters that are independent of AWS. These are usually problems associated with improper configuration and should be resolved by the administrator. Problems can be:
- incorrect network configuration
- wrong boot configuration
- out of memory
- file system issues
- kernel problems
Looks like status checks like this:
Going into the properties of the host, you can view individual data on the instance:
Status Check + CloudWatch
From today, problems with the status of checks can be tracked automatically well and automatically make a decision. For example, you have 300 servers and keeping track of their status with checks is not an easy task, but there is a solution that can be described in a few steps:
- in autosampling group to set the minimum number of cars 300
- install CloudWatch check, which will extinguish the instance in case of Status Check Failed
Thus, you protect yourself from the fact that you will not use a healthy system. After an instance that has not passed the status of the checks is turned off, a new one will immediately rise instead, which is likely to be healthy.
The names of new checks in CloudWatch:
For me it is very convenient. Now you can stop worrying about one more thing.
Source: https://habr.com/ru/post/162579/
All Articles