AWS Gateway Load Balancer now supports TCP Reset for faster failure recovery

AWS Gateway Load Balancer (GWLB) Updates

GWLB now supports sending TCP Reset (RST) packets when a target becomes unhealthy, is deregistered, or when a flow's idle timeout expires. This reduces traffic interruptions from minutes to seconds by enabling TCP endpoints to quickly detect failed connections and establish new TCP flows through healthy targets.

Previously, when a GWLB target failed, existing TCP connections would continue to be forwarded to the unhealthy target (fail-open behavior). Client and server applications could experience interruptions lasting several minutes due to TCP retry and exponential back-off mechanisms built in the TCP stacks of clients or servers. When this capability is enabled, GWLB sends TCP Resets in response to the incoming traffic, indicating to the sender that a TCP connection is no longer viable. This allows TCP endpoints to recover quickly.

What to do

• Enable TCP Reset per target group using the AWS Management Console, AWS CLI, or API.
• Three triggers are supported: target becomes unhealthy, target deregistration (after connection draining), and TCP idle timeout expiry.

This feature is available for all new and existing Gateway Load Balancers in all AWS Regions where GWLB is available. There is no additional charge for using this feature.

Source: AWS release notes

If you need further guidance on AWS, our experts are available at AWS@westloop.io. You may also reach us by submitting the Contact Us form.