Network Load Balancer (NLB)
Distributes raw TCP, UDP, and TLS traffic at Layer 4, preserves source IP addresses natively, assigns a dedicated static Elastic IP per Availability Zone, and powers AWS PrivateLink endpoint services.
AWS Container Placement
SUBNET
Summary
High-performance Layer-4 load balancer handling millions of requests per second with ultra-low latency, static IP addresses, and TCP/UDP passthrough.
When to Use (SAA-C03)
Use for non-HTTP TCP/UDP protocols, static IP requirements, or sub-millisecond L4 passthrough.
Allowed Ingress Connections & Ports
| Source Service | Protocol | Port | Architectural Rationale |
|---|---|---|---|
| WEBCLIENT | TCP, UDP, TLS | 1-65535 | Public internet clients and mobile applications |
| ROUTE53 | DNS / IP | 53 | DNS resolution returning static IP per AZ |
| INTERFACE-ENDPOINT | PrivateLink | ALL | Private VPC Interface Endpoint ingress |
Allowed Egress Targets & Ports
| Target Service | Protocol | Port | Data Flow Rationale |
|---|---|---|---|
| EC2 | TCP, UDP | Dynamic Target Ports | Backend compute fleet instances |
| ECS | TCP | Dynamic Container Ports | Container microservices |
| ALB | TCP, TLS | 80, 443 | NLB in front of ALB for static IP addressing |
Key Configuration Parameters & AWS Best Practices
| Parameter | Format / Example | Purpose & Rationale |
|---|---|---|
| Load Balancer Scheme (scheme) (Required) | internet-facing | Specifies whether the NLB has public Elastic IPs reachable from the internet or private IPs within the VPC. Why: Determines whether AWS assigns internet-routable public IPs or internal VPC addresses. |
| Subnet Attachments (subnets) (Required) | subnet-12345678, subnet-87654321 | The subnets in which NLB network interfaces are spawned. Why: AWS provisions elastic network interfaces with static IPs in each selected subnet for traffic ingestion. |
| Cross-Zone Load Balancing (crossZoneLoadBalancing) | true | Distributes traffic evenly across all registered targets in all enabled Availability Zones. Why: Prevents target overload when traffic arrives unevenly across AZ IP endpoints. |
| Client IP Preservation | true | Preserves the original client IP address in packet headers without NAT rewriting. Why: Essential for firewall auditing, IP rate-limiting, and geolocation logging on backend servers. |
Practice Labs Using Network Load Balancer
Global Low-Latency Ingress: Global Accelerator Anycast Failover
Deploy AWS Global Accelerator with static Anycast IPs directing traffic to regional load balancers with instan…
BUILD-10Build: Enterprise Zero-Trust PrivateLink Service Connection
Build a two-VPC architecture with an Interface VPC Endpoint in the Consumer VPC and a Network Load Balancer in…
Frequently Asked Questions
Where does Network Load Balancer live inside an AWS VPC architecture?
Valid container placement: SUBNET. Distributes raw TCP, UDP, and TLS traffic at Layer 4, preserves source IP addresses natively, assigns a dedicated static Elastic IP per Availability Zone, and powers AWS PrivateLink endpoint services.
When should I use Network Load Balancer on the AWS SAA-C03 exam?
Use for non-HTTP TCP/UDP protocols, static IP requirements, or sub-millisecond L4 passthrough.
Can I simulate Network Load Balancer packet routing without an AWS account?
Yes. CloudTracer simulates Network Load Balancer along with 53 AWS services directly in your browser and exports production Terraform HCL.