AWS elasticloadbalancing documentation change
Summary
Replaced 'ELB' with 'Elastic Load Balancing' in dualstack DNS and UDP timeout sections
Security assessment
Terminology update without technical changes. UDP timeout behavior and dualstack implementation remain unchanged. No security implications or vulnerability fixes introduced.
Diff
diff --git a/elasticloadbalancing/latest/network/network-load-balancers.md b/elasticloadbalancing/latest/network/network-load-balancers.md index bb9d98a31..8dc4c78c6 100644 --- a//elasticloadbalancing/latest/network/network-load-balancers.md +++ b//elasticloadbalancing/latest/network/network-load-balancers.md @@ -97 +97 @@ Clients can connect to the Network Load Balancer using both IPv4 addresses (for - * When you enable dualstack mode for the Network Load Balancer, ELB provides an AAAA DNS record for the Network Load Balancer. Clients that communicate with the Network Load Balancer using IPv4 addresses resolve the A DNS record. Clients that communicate with the Network Load Balancer using IPv6 addresses resolve the AAAA DNS record. + * When you enable dualstack mode for the Network Load Balancer, Elastic Load Balancing provides an AAAA DNS record for the Network Load Balancer. Clients that communicate with the Network Load Balancer using IPv4 addresses resolve the A DNS record. Clients that communicate with the Network Load Balancer using IPv6 addresses resolve the AAAA DNS record. @@ -114 +114 @@ The connection idle timeout for TLS listeners is 350 seconds and can't be modifi -While UDP is connectionless, the load balancer maintains UDP flow state based on the source and destination IP addresses and ports. This ensures that packets that belong to the same flow are consistently sent to the same target. After the idle timeout period elapses, the load balancer considers the incoming UDP packet as a new flow and routes it to a new target. ELB sets the idle timeout value for UDP flows to 120 seconds. This cannot be changed. +While UDP is connectionless, the load balancer maintains UDP flow state based on the source and destination IP addresses and ports. This ensures that packets that belong to the same flow are consistently sent to the same target. After the idle timeout period elapses, the load balancer considers the incoming UDP packet as a new flow and routes it to a new target. Elastic Load Balancing sets the idle timeout value for UDP flows to 120 seconds. This cannot be changed.