AWS Network Load Balancer now supports configurable TCP idle timeout
News
This announcement introduces a new feature in AWS Network Load Balancer (NLB) that allows configuring the TCP idle timeout value for long-lived traffic flows. Previously, NLB had a fixed TCP idle timeout of 350 seconds, which could cause connection retries and latency for applications with long-lived flows.
Specifically, the article covers:
- The new capability allows setting the TCP idle timeout value between 60 and 6000 seconds (default is still 350 seconds for backward compatibility)
- Benefits for applications with long-lived flows like telemetry reporting, databases, streaming services, and ERP systems
- Reduces connection retries and latency by maintaining optimal target stickiness duration
- Configuration via the 'tcp.idle_timeout.seconds' listener attribute on new and existing NLBs
- Available in all AWS commercial and GovCloud (US) regions
The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.
The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.