Network Load Balancer

Network Load Balancer operates at the connection level (Layer 4), routing connections to targets within ABT VPC, based on IP protocol data. Ideal for load balancing of both TCP and UDP traffic, Network Load Balancer is capable of handling millions of requests per second while maintaining ultra-low latencies. Network Load Balancer is optimized to handle sudden and volatile traffic patterns while using a single static IP address per Availability Zone.

Connection based Layer 4 Load Balancing
Connection-based Layer 4 Load Balancing

You can load balance both TCP and UDP traffic, routing connections to targets - ABT VPC instances.

TLS Offloading

Network Load Balancer supports client TLS session termination. This enables you to offload TLS termination tasks to the load balancer, while preserving the source IP address for your back-end applications.

Sticky Sessions

Sticky sessions (source IP affinity) are a mechanism to route requests from the same client to the same target. Stickiness is defined at the target group level.

Low Latency

Network Load Balancer offers extremely low latencies for latency-sensitive applications.

Preserve source IP address
Preserve source IP address

Network Load Balancer preserves the client side source IP allowing the back-end to see the IP address of the client. This can then be used by applications for further processing.

Static IP support
Static IP support

Network Load Balancer automatically provides a static IP per Availability Zone (subnet) that can be used by applications as the front-end IP of the load balancer.

DNS Fail over
DNS Fail-over

If there are no healthy targets registered with the Network Load Balancer or if the Network Load Balancer nodes in a given zone are unhealthy, then it will direct traffic to load balancer nodes in other Availability Zones.

Long-lived TCP Connections

Network Load Balancer supports long-lived TCP connections that are ideal for WebSocket type of applications.

Zonal Isolation

The Network Load Balancer is designed for application architectures in a single zone. If something in the Availability Zone fails, we will automatically fail-over to other healthy Availability Zones.