DevFW-CICD/ingress-nginx-helm
6
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Docs: How to modify NLB TCP timeout. (#13249)

Browse source 
Co-authored-by: Hardik Mishra <hardmish@amazon.com>
This commit is contained in:
k8s-infra-cherrypick-robot 2025-04-22 05:37:41 -07:00 • committed by GitHub
parent bacba9deae
commit 43d26e5458
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 2 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

5
docs/deploy/index.md
View file

@ -308,12 +308,11 @@ This section explains how to do that on AWS using an NLB.
##### NLB Idle Timeouts
Idle timeout value for TCP flows is 350 seconds and
[cannot be modified](https://docs.aws.amazon.com/elasticloadbalancing/latest/network/network-load-balancers.html#connection-idle-timeout).
The default idle timeout value for TCP flows is 350 seconds and [can be modified to any value between 60-6000 seconds.](https://docs.aws.amazon.com/elasticloadbalancing/latest/network/network-load-balancers.html#connection-idle-timeout)
For this reason, you need to ensure the
[keepalive_timeout](https://nginx.org/en/docs/http/ngx_http_core_module.html#keepalive_timeout)
value is configured less than 350 seconds to work as expected.
value is configured less than your configured idle timeout to work as expected.
By default, NGINX `keepalive_timeout` is set to `75s`.