This topic describes how to use Cloud Assistant to execute a health check script on Elastic Compute Service (ECS) instances and view the health check results. Heath check scripts are generated based on the health check configurations of listeners. You can manually execute a health check script after you attach backend servers to a Classic Load Balancer (CLB) instance.
Prerequisites
- Your CLB service is granted the required permissions to perform health checks on ECS instances. To grant the permissions, go to RAM Roles.
- The backend servers that you want to check must be ECS instances that run Linux, the default Linux shell must be Bash, and Cloud Assistant must have been installed on the ECS instances. In addition, the ECS instances must be deployed in a virtual private cloud (VPC) and they must be in the Running state.
- Health checks are enabled for the listener of the CLB instance, and the ECS instances are added to the backend server group.
Background information
- You cannot execute a health check script on backend servers that are associated with forwarding rules.
- The heath check results returned after you execute a script may differ from those after the system automatically performs a health check. This is because different connections are used to perform these health checks. The health check results returned upon a script execution only provide you with suggestions on health check configurations. For backend server troubleshooting, the health check results returned upon scheduled health checks shall prevail.