AWS elasticloadbalancing documentation change
Summary
Added troubleshooting section for IP fragmented packets not being routed to targets, clarifying NLB limitations for non-UDP traffic
Security assessment
The change documents a functional limitation of Network Load Balancers (NLB) regarding IP fragmented packets but does not address a security vulnerability or introduce security features. It is a clarification of existing behavior.
Diff
diff --git a/elasticloadbalancing/latest/network/load-balancer-troubleshooting.md b/elasticloadbalancing/latest/network/load-balancer-troubleshooting.md index 17fd54500..a8ec2de07 100644 --- a//elasticloadbalancing/latest/network/load-balancer-troubleshooting.md +++ b//elasticloadbalancing/latest/network/load-balancer-troubleshooting.md @@ -5 +5 @@ -A registered target is not in serviceRequests are not routed to targetsTargets receive more health check requests than expectedTargets receive fewer health check requests than expectedUnhealthy targets receive requests from the load balancerTarget fails HTTP or HTTPS health checks due to host header mismatchUnable to associate a security group with a load balancerUnable to remove all security groupsIncrease in TCP_ELB_Reset_Count metricConnections time out for requests from a target to its load balancerPerformance decreases when moving targets to a Network Load BalancerPort allocation errors for backend flowsIntermittent TCP connection establishment failure or TCP connection establishment delaysPotential failure when the load balancer is being provisionedTraffic is distributed unevenly between targetsDNS name resolution contains fewer IP addresses than enabled Availability ZonesTroubleshoot unhealthy targets using the resource map +A registered target is not in serviceRequests are not routed to targetsTargets receive more health check requests than expectedTargets receive fewer health check requests than expectedUnhealthy targets receive requests from the load balancerTarget fails HTTP or HTTPS health checks due to host header mismatchUnable to associate a security group with a load balancerUnable to remove all security groupsIncrease in TCP_ELB_Reset_Count metricConnections time out for requests from a target to its load balancerPerformance decreases when moving targets to a Network Load BalancerPort allocation errors for backend flowsIntermittent TCP connection establishment failure or TCP connection establishment delaysPotential failure when the load balancer is being provisionedTraffic is distributed unevenly between targetsDNS name resolution contains fewer IP addresses than enabled Availability ZonesIP fragmented packets are not routed to targetsTroubleshoot unhealthy targets using the resource map @@ -151,0 +152,4 @@ For example, suppose your Network Load Balancer has three Availability Zones ena +## IP fragmented packets are not routed to targets + +Network Load Balancers do not support IP fragmented packets for non-UDP traffic. +