AWS elasticloadbalancing documentation change
Summary
Expanded health check documentation to include QUIC services alongside UDP, updating guidance for service availability verification
Security assessment
The change adds QUIC protocol support to health check documentation but does not address vulnerabilities or introduce security features. It is a functional update for broader protocol coverage.
Diff
diff --git a/elasticloadbalancing/latest/network/target-group-health-checks.md b/elasticloadbalancing/latest/network/target-group-health-checks.md index 66c25fcc2..40ac2f583 100644 --- a//elasticloadbalancing/latest/network/target-group-health-checks.md +++ b//elasticloadbalancing/latest/network/target-group-health-checks.md @@ -25 +25 @@ If you add a TLS listener to your Network Load Balancer, we perform a listener c -For a UDP service, target availability can be tested using non-UDP health checks on your target group. You can use any available health check (TCP, HTTP, or HTTPS), and any port on your target to verify the availability of a UDP service. If the service receiving the health check fails, your target is considered unavailable. To improve the accuracy of health checks for a UDP service, configure the service listening to the health check port to track the status of your UDP service and fail the health check if the service is unavailable. +For UDP and QUIC services, target availability can be tested using non-UDP health checks on your target group. You can use any available health check (TCP, HTTP, or HTTPS), and any port on your target to verify the availability of your service. If the service receiving the health check fails, your target is considered unavailable. To improve the accuracy of health checks for your service, configure the service listening to the health check port to track the status of your UDP or QUIC service and fail the health check if the service is unavailable.