Home Arrow Icon Knowledge base Arrow Icon Global Arrow Icon Can the idle timeout for TCP connections in Global Accelerator be customized like in AWS Network Firewall


Can the idle timeout for TCP connections in Global Accelerator be customized like in AWS Network Firewall


AWS Global Accelerator does not support customization of the TCP idle timeout for connections. The TCP idle timeout for Global Accelerator is fixed at approximately 340 seconds and cannot be changed by users. This means that once a TCP connection is idle for that period, Global Accelerator considers it timed out and may close or reset the connection accordingly[7].

In contrast, AWS Network Firewall allows you to customize the TCP idle timeout. You can set the `TcpIdleTimeoutSeconds` parameter to any value between 60 and 6000 seconds, with the default being 350 seconds. This configurable timeout controls how long the firewall waits without seeing TCP traffic before it considers the connection idle and removes it from its flow table[6][8].

Similarly, other AWS services like Network Load Balancer (NLB) and Gateway Load Balancer (GWLB) also support configurable TCP idle timeouts ranging from 60 to 6000 seconds. This flexibility helps align the load balancer or firewall timeout settings with the requirements of backend applications or third-party appliances, avoiding premature connection termination and traffic disruptions[3][5][9].

Summary:

- Global Accelerator: TCP idle timeout is fixed (~340 seconds), not customizable[7].
- Network Firewall: TCP idle timeout customizable between 60 and 6000 seconds, default 350 seconds[6][8].
- Network Load Balancer and Gateway Load Balancer: Also support configurable TCP idle timeouts in the same range (60–6000 seconds)[3][5][9].

Therefore, unlike AWS Network Firewall, AWS Global Accelerator does not offer the ability to customize the TCP idle timeout for connections.

Citations:
[1] https://aws.amazon.com/about-aws/whats-new/2024/10/aws-network-firewall-configurable-tcp-idle-timeout/
[2] https://docs.aws.amazon.com/network-firewall/latest/developerguide/troubleshooting-general-issues.html
[3] https://www.reddit.com/r/aws/comments/1f8bel9/aws_network_load_balancer_now_supports/
[4] https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-configurable-idle-timeout-for-connection-tracking/
[5] https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-configurable-tcp-idle-timeout-for-gateway-load-balancer/
[6] https://docs.aws.amazon.com/network-firewall/latest/APIReference/API_FlowTimeouts.html
[7] https://docs.aws.amazon.com/pdfs/global-accelerator/latest/dg/global-accelerator-guide.pdf
[8] https://aws-news.com/article/0192dec1-a4c4-06f0-a893-9ad13f718c48
[9] https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-nlb-tcp-configurable-idle-timeout/