The idle timeout for TCP connections varies among Global Accelerator, Network Load Balancer (NLB), and Gateway Load Balancer (GWLB).
**Global Accelerator: The default idle timeout for TCP connections in AWS Global Accelerator is 90 seconds[9]. AWS Global Accelerator reduces setup time by terminating TCP connections at the edge of the AWS network[6].
**Network Load Balancer (NLB): NLB has a configurable TCP idle timeout, which can be set to any value between 60 and 6000 seconds[7][10]. The default timeout for TCP connections is 350 seconds[7].
**Gateway Load Balancer (GWLB): GWLB also has a configurable TCP idle timeout, with the same range as NLB (60 to 6000 seconds)[8]. Previously, GWLB had a fixed TCP idle timer of 350 seconds[8]. The ability to configure the TCP idle timeout allows users to align the timeout value of firewalls and applications with GWLB, ensuring continuous traffic flow and reducing disruptions[8].
Citations:
[1] https://docs.aws.amazon.com/global-accelerator/latest/dg/introduction-how-it-works.html
[2] https://docs.aws.amazon.com/pdfs/global-accelerator/latest/dg/global-accelerator-guide.pdf
[3] https://repost.aws/questions/QUuNiUCKYUSkKScntMG8MMeA/timeout-aws-global-accelerator
[4] https://docs.aws.amazon.com/global-accelerator/latest/dg/about-endpoints.avoid-connection-collisions.html
[5] https://aws.amazon.com/global-accelerator/features/
[6] https://www.linkedin.com/posts/karthik-sakthivel-techie_introducing-nlb-tcp-configurable-idle-timeout-activity-7237106073189408769-WqR4
[7] https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-configurable-tcp-idle-timeout-for-gateway-load-balancer/
[8] https://hands-on.cloud/aws-services/global-accelerator/
[9] https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-nlb-tcp-configurable-idle-timeout/
[10] https://learn.microsoft.com/en-us/azure/load-balancer/load-balancer-tcp-idle-timeout
[11] https://docs.oracle.com/en-us/iaas/Content/NetworkLoadBalancer/NetworkLoadBalancers/configure-idle-timeout.htm