
AWS now supports Gateway Load Balancer Endpoints as next-hop targets in Virtual Private Gateway route tables, enabling direct traffic inspection via third-party appliances or AWS Network Firewall for on-premises connections.


<div><p>This article announces AWS Virtual Private Gateway (VGW) Ingress Routing support for Gateway Load Balancer, enabling traffic inspection at VPC entry points.</p><ul><li>VGW Ingress Routing now supports Gateway Load Balancer Endpoints as next-hop targets</li><li>Inspect incoming traffic from VPN or Direct Connect before reaching protected subnets</li><li>Works with AWS Network Firewall and third-party virtual appliances like NGFWs and IDS/IPS</li><li>Eliminates need for Transit Gateway workarounds, reducing costs and latency</li><li>Supports three deployment scenarios: GWLB with third-party appliances, AWS Network Firewall, and combined IGW/VGW routing</li><li>GWLBE must be in same VPC as VGW; no additional costs; available in all AWS regions</li></ul><p>This enhancement simplifies centralized traffic inspection for hybrid connectivity by allowing direct steering of ingress traffic through security appliances without Transit Gateway overhead.</p></div>


Related articles