GetServerGroupsGroupHealthCheckConfig

data class GetServerGroupsGroupHealthCheckConfig(val healthCheckCodes: List<String>, val healthCheckConnectPort: Int, val healthCheckEnabled: Boolean, val healthCheckHost: String, val healthCheckHttpVersion: String, val healthCheckInterval: Int, val healthCheckMethod: String, val healthCheckPath: String, val healthCheckProtocol: String, val healthCheckTimeout: Int, val healthyThreshold: Int, val unhealthyThreshold: Int)

Constructors

Link copied to clipboard
constructor(healthCheckCodes: List<String>, healthCheckConnectPort: Int, healthCheckEnabled: Boolean, healthCheckHost: String, healthCheckHttpVersion: String, healthCheckInterval: Int, healthCheckMethod: String, healthCheckPath: String, healthCheckProtocol: String, healthCheckTimeout: Int, healthyThreshold: Int, unhealthyThreshold: Int)

Types

Link copied to clipboard
object Companion

Properties

Link copied to clipboard

The status code for a successful health check. Multiple status codes can be specified as a list.

Link copied to clipboard

The port of the backend server that is used for health checks.

Link copied to clipboard

Indicates whether health checks are enabled.

Link copied to clipboard

The domain name that is used for health checks.

Link copied to clipboard

HTTP protocol version.

Link copied to clipboard

The time interval between two consecutive health checks.

Link copied to clipboard

Health check method.

Link copied to clipboard

The forwarding rule path of health checks.

Link copied to clipboard

Health check protocol.

Link copied to clipboard

The timeout period of a health check response. If a backend Elastic Compute Service (ECS) instance does not send an expected response within the specified period of time, the ECS instance is considered unhealthy.

Link copied to clipboard

The number of health checks that an unhealthy backend server must pass consecutively before it is declared healthy. In this case, the health check state is changed from fail to success.

Link copied to clipboard

The number of consecutive health checks that a healthy backend server must consecutively fail before it is declared unhealthy. In this case, the health check state is changed from success to fail.