--- title: "Deploying the AWS Gateway Load Balancer" slug: "deploying-the-aws-gateway-load-balancer-2" tags: ["Product Usage"] updated: 2026-11-19T12:30:51Z published: 2026-11-19T12:30:51Z canonical: "docs.trellix.com/deploying-the-aws-gateway-load-balancer-2" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Deploying the AWS Gateway Load Balancer This document will focus on the most commonly used design patterns and optimal configuration settings as best practices to consider when deploying the GWLB: 1. Tune TCP keep-alive or timeout values to support long-lived TCP flows 2. Enable Appliance Mode on AWS Transit Gateway to maintain flow symmetry for inter-VPC traffic inspection 3. Understand when to use Cross-Zone Load Balancing 4. Understand appliance and AZ failure scenarios 5. Choose one-arm firewall deployment mode for egress traffic inspection 6. Choose one-arm firewall deployment mode for SSL/TLS traffic inspection 7. Jumbo Frame supports MTU 8500, but the protected AWS instances have a default MTU of 9001. You must update MTU on AWS instances to enable the traffic inspection. Else, GWLB will drop the traffic. If you have enabled SSL decryption on the Sensor, then MTU should not exceed 1500. If the MTU exceeds 1500, the Sensor does not decrypt jumbo traffic. For more information, see [Best practices for deploying Gateway Load Balancer](https://aws.amazon.com/blogs/networking-and-content-delivery/best-practices-for-deploying-gateway-load-balancer/) and [Traffic Mirroring limitations](https://docs.aws.amazon.com/vpc/latest/mirroring/traffic-mirroring-network-limitations.html#traffic-mirroring-mtu).