Properties for configuring a health check.
|enabled?||Indicates whether health checks are enabled.|
|healthy||HTTP code to use when checking for a successful response from a target.|
|healthy||The number of consecutive health checks successes required before considering an unhealthy target healthy.|
|interval?||The approximate number of seconds between health checks for an individual target.|
|path?||The ping path destination where Elastic Load Balancing sends health check requests.|
|port?||The port that the load balancer uses when performing health checks on the targets.|
|protocol?||The protocol the load balancer uses when performing health checks on targets.|
|timeout?||The amount of time, in seconds, during which no response from a target means a failed health check.|
|unhealthy||The number of consecutive health check failures required before considering a target unhealthy.|
(optional, default: Determined automatically.)
Indicates whether health checks are enabled.
If the target type is lambda, health checks are disabled by default but can be enabled. If the target type is instance or ip, health checks are always enabled and cannot be disabled.
HTTP code to use when checking for a successful response from a target.
For Application Load Balancers, you can specify values between 200 and 499, and the default value is 200. You can specify multiple values (for example, "200,202") or a range of values (for example, "200-299").
(optional, default: 5 for ALBs, 3 for NLBs)
The number of consecutive health checks successes required before considering an unhealthy target healthy.
For Application Load Balancers, the default is 5. For Network Load Balancers, the default is 3.
(optional, default: Duration.seconds(30))
The approximate number of seconds between health checks for an individual target.