Posted On: Oct 30, 2024
We're excited to announce a new capability for the Gateway Load Balancer (GWLB) and Network Load Balancer (NLB) that allows you to configure the TCP idle timeout value.
With this new capability, you can now configure the TCP idle timeout value for your GWLB and NLB between 60 to 6000 seconds, in addition to the default value of 350 seconds. This allows you to better align the GWLB and NLB TCP idle timeout with the requirements of your target applications, such as databases and ERP systems, that use long-lived traffic flows. By configuring the TCP idle timeout, you can now perform uninterrupted stateful inspection and reduce latency of these applications in the cloud. To configure the TCP idle timeout value for your newly created or existing GWLB and NLB, you can set the 'tcp.idle_timeout.timeout_seconds' listener attribute.
This capability is available in Amazon Web Services China (Beijing) Region, operated by Sinnet and Amazon Web Services China (Ningxia) Region, operated by NWCD at no additional charge.
For more information on how to use this feature, see this post.