AWS Gateway Load Balancer now supports configurable TCP idle timeout

This article announces a new capability for AWS Gateway Load Balancer (GWLB) that allows configuring the TCP idle timeout value. Previously, the timeout was fixed at 350 seconds, which could interrupt long-lived traffic flows for certain applications.

Specifically, the article covers:

• The new feature allows setting the TCP idle timeout between 60 and 6000 seconds (default remains 350 seconds for backward compatibility)
• This helps maintain target stickiness and reduce interruptions for applications with long-lived flows like financial apps, databases, and ERP systems
• The timeout value can be configured using the 'tcp.idle_timeout.seconds' listener attribute
• The feature is available in all AWS commercial and GovCloud (US) regions
• References are provided to an AWS blog post and product documentation for more information