Introducing NLB TCP configurable idle timeout
Networking & Content Delivery Blog
This article introduces a new feature for AWS Network Load Balancer (NLB): the ability to configure the TCP idle timeout for connections. It explains the importance of this feature and how it works.
Specifically, the article covers:
- An overview of how TCP connections are established and closed
- How NLB handles TCP connections and the default 350-second idle timeout
- Considerations when updating the TCP idle timeout value (between 60-6000 seconds)
- Steps to configure the TCP idle timeout using AWS APIs/CLI and the AWS Management Console
- New CloudWatch metrics to monitor rejected flows due to the flow table being full
- Conclusion on the benefits of configurable TCP idle timeout for NLB
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.
Related articles
Sep 3
2024
2024
Introducing configurable TCP idle timeout for Gateway Load Balancer
Sep 3
2024
2024
AWS Network Load Balancer now supports configurable TCP idle timeout
Sep 5
2024
2024
AWS Gateway Load Balancer now supports configurable TCP idle timeout
Oct 30
2024
2024
AWS Network Firewall now supports configurable TCP idle timeout
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.