From 43d26e5458b8464ee58af6d03764513dd0e88c18 Mon Sep 17 00:00:00 2001 From: k8s-infra-cherrypick-robot <90416843+k8s-infra-cherrypick-robot@users.noreply.github.com> Date: Tue, 22 Apr 2025 05:37:41 -0700 Subject: [PATCH] Docs: How to modify NLB TCP timeout. (#13249) Co-authored-by: Hardik Mishra --- docs/deploy/index.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/deploy/index.md b/docs/deploy/index.md index f01e0edc0..bc36a1fce 100644 --- a/docs/deploy/index.md +++ b/docs/deploy/index.md @@ -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`.