AWS elasticloadbalancing documentation change
Summary
Added support for QUIC and TCP_QUIC protocols in target groups, and added routing explanation for QUIC traffic
Security assessment
The change introduces QUIC protocol support which includes built-in TLS 1.3 encryption by default, enhancing security. However, this is a feature addition rather than addressing a specific security vulnerability.
Diff
diff --git a/elasticloadbalancing/latest/network/introduction.md b/elasticloadbalancing/latest/network/introduction.md index 2482074b1..3882d8b2f 100644 --- a//elasticloadbalancing/latest/network/introduction.md +++ b//elasticloadbalancing/latest/network/introduction.md @@ -19 +19 @@ A _listener_ checks for connection requests from clients, using the protocol and -A _target group_ routes requests to one or more registered targets, such as EC2 instances, using the protocol and the port number that you specify. Network Load Balancer target groups support the TCP, UDP, TCP_UDP, and TLS protocols. You can register a target with multiple target groups. You can configure health checks on a per target group basis. Health checks are performed on all targets registered to a target group that is specified in a listener rule for your load balancer. +A _target group_ routes requests to one or more registered targets, such as EC2 instances, using the protocol and the port number that you specify. Network Load Balancer target groups support the TCP, UDP, TCP_UDP, TLS, QUIC, and TCP_QUIC protocols. You can register a target with multiple target groups. You can configure health checks on a per target group basis. Health checks are performed on all targets registered to a target group that is specified in a listener rule for your load balancer. @@ -43,0 +44,2 @@ For UDP traffic, the load balancer selects a target using a flow hash algorithm +For QUIC traffic, the load balancer selects a target using the Server ID specified in the Connection ID (CID). For initial connection attempts that lack a Server ID, a flow hash algorithm based on the protocol, source IP address, source port, destination IP address, and destination port is used. Once a Connection ID is established traffic for this CID gets routed to the same target for the lifetime of the CID. + @@ -69,0 +72,2 @@ Using a Network Load Balancer instead of a Classic Load Balancer has the followi + * Support for the QUIC and TCP_QUIC protocols with advanced congestion control, fewer round trip connection establishment, built in TLS, and connection migration across networks. +