Update the TCP idle timeout for your Network Load Balancer listener
For each TCP request made through a Network Load Balancer, the state of that connection is tracked. If no data is sent through the connection by either the client or target for longer than the idle timeout, the connection is closed.
Considerations
-
The default idle timeout value for TCP flows is 350 seconds.
-
The connection idle timeout for TLS listeners is 350 seconds and can't be modified.
-
If you set the idle timeout higher than 350 seconds, verify that your targets' ENI connection tracking idle timeout (
TcpEstablishedTimeout) is equal to or greater than the Network Load Balancer idle timeout value. On Nitro V6+ instances, the default connection tracking timeout is 350 seconds. A mismatch causes the target's network interface to silently drop connection state before the load balancer closes the connection. For more information, see Best Practices for TCP Connection Management on EC2.