Introducing configurable TCP idle timeout for Gateway Load Balancer
Networking & Content Delivery Blog
This article introduces a new feature for the AWS Gateway Load Balancer (GWLB) that allows configuring the TCP idle timeout between 60 seconds and 6000 seconds. The configurable TCP idle timeout helps align GWLB's timeout with other applications and firewalls, preventing traffic disruption.
Specifically, the article covers:
- Background on GWLB and TCP idle timeout
- Why a configurable TCP idle timeout is needed for GWLB
- Step-by-step instructions on how to configure the TCP idle timeout using the AWS Management Console and API
- Recommendations for setting the timeout value for long-running and short-lived TCP flows
- Monitoring GWLB using new CloudWatch metrics
- Conclusion and additional resources
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.