This article provides overview of Health Check Improvements for AWS Gateway Load Balancer
Elastic Load Balancing (ELB) team is happy to announce the launch of health check improvements for the AWS Gateway Load Balancer (GWLB). With these improvements, you now have the ability to define health check intervals, specify HTTP response codes that determine target health, and configure the number of consecutive health check responses before a target considered is either healthy or unhealthy. These improvements help in ensuring higher availability and resiliency.
- You now have the ability to configure HealthCheckIntervalSeconds duration from 5 seconds to 300 seconds. Default is 30 seconds.
- UnhealthyThresholdCount now defaults to 2. GWLB will take the target out of the target group (TG) after 2 missed health checks (HC) and reduce the target failure detection time. If you don’t prefer the new default, you can change this value from 2 to 10.
- HealthyThresholdCount now defaults to 5. GWLB will bring a new target into the target group after 5 successful health checks, which avoids gray failures due to bootstrapping. If you don’t prefer the new default, you can change this value from 2 to 10.
- The change in health check defaults will apply only to newly created GWLB target groups. Existing target group defaults will not change and will continue to use prior defaults to ensure backward compatibility.
- These improvements are available using API and AWS Console.
- These improvements are available in all commercial, GovCloud, and China regions.
For details, see the GWLB documentation for: