Networking · AWS SERVICE CHEATSHEET

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.

Open Interactive NLB Sandbox → Simulate in Architecture Studio

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 ServiceProtocolPortArchitectural Rationale
WEBCLIENTTCP, UDP, TLS1-65535Public internet clients and mobile applications
ROUTE53DNS / IP53DNS resolution returning static IP per AZ
INTERFACE-ENDPOINTPrivateLinkALLPrivate VPC Interface Endpoint ingress

Allowed Egress Targets & Ports

Target ServiceProtocolPortData Flow Rationale
EC2TCP, UDPDynamic Target PortsBackend compute fleet instances
ECSTCPDynamic Container PortsContainer microservices
ALBTCP, TLS80, 443NLB in front of ALB for static IP addressing

Key Configuration Parameters & AWS Best Practices

ParameterFormat / ExamplePurpose & Rationale
Load Balancer Scheme (scheme) (Required)internet-facingSpecifies 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-87654321The 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)trueDistributes 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 PreservationtruePreserves 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

SAA-GLOBAL-ACCELERATOR

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-10

Build: 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.

More Networking Cheatsheets

App Load Balancer → Virtual Private Cloud → VPC Subnet → VPC Route Table → Internet Gateway → NAT Gateway →