Yes, you can customize both the health check interval and the threshold count in AWS Global Accelerator, specifically for endpoint groups within a standard accelerator.
**Health Check Interval
This is the time interval, in seconds, between each health check that Global Accelerator performs on endpoints in an endpoint group. You can set this interval when you create or edit an endpoint group. The typical valid range for the health check interval is configurable, for example, from 1 to 50 seconds in some contexts, with a default often being 30 seconds or 2 seconds depending on the service or console interface used. This interval controls how frequently the health status of each endpoint is verified[2][5][11].
**Threshold Count
This parameter defines the number of consecutive health checks that must succeed or fail before Global Accelerator changes the health status of an endpoint. For example, if the threshold count is set to 3, an endpoint must fail 3 consecutive health checks before it is marked unhealthy, or pass 3 consecutive checks before being marked healthy again. This helps avoid flapping (rapid state changes) caused by transient network issues. The valid values for threshold count generally range from 2 to 10, with a default of 3[2][5][11].
**How to Configure
- You specify these settings at the endpoint group level, either during the creation of the accelerator or when editing the endpoint group configuration.
- The health check port and protocol can also be set, often matching the listener port and protocol, but you can override the port if needed (with appropriate security group adjustments).
- For HTTP/S health checks, you can specify a URI path for the health check request.
- These settings ensure that Global Accelerator only routes traffic to endpoints that meet your customized health criteria[2][5][8][11].
**Additional Notes
- The health check settings are applied per endpoint group and affect how Global Accelerator routes traffic to healthy endpoints.
- If no endpoints pass the health checks, Global Accelerator may route traffic to all endpoints regardless of health status to maintain availability[3].
- Make sure your firewall and security group rules allow inbound traffic from the IP ranges used by Route 53 health checkers, as these are the sources of the health check probes[2].
In summary, AWS Global Accelerator allows you to customize the health check interval and threshold count to control how frequently health checks occur and how sensitive the system is to endpoint health changes, providing flexibility to match your application's reliability and responsiveness requirements. This customization is done per endpoint group in the accelerator configuration[2][5][11].
Citations:
[1] https://docs.aws.amazon.com/global-accelerator/latest/dg/about-endpoint-groups-health-check-options.html
[2] https://docs.aws.amazon.com/global-accelerator/latest/dg/introduction-how-it-works.html
[3] https://repost.aws/knowledge-center/global-accelerator-unhealthy-endpoints
[4] https://docs.aws.amazon.com/global-accelerator/latest/dg/getting-started-standard.html
[5] https://www.alibabacloud.com/help/en/ga/user-guide/enable-and-manage-health-checks
[6] https://docs.aws.amazon.com/global-accelerator/latest/dg/limits-global-accelerator.html
[7] https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/route53/client/update_health_check.html
[8] https://docs.aws.amazon.com/global-accelerator/latest/dg/about-endpoint-groups.html
[9] https://docs.aws.amazon.com/pdfs/global-accelerator/latest/dg/global-accelerator-guide.pdf
[10] https://repost.aws/questions/QUKCRI46A5SbmsHxtXo3bfYg/elb-health-check-frequency
[11] https://boto3.amazonaws.com/v1/documentation/api/1.12.30/reference/services/globalaccelerator.html