NLB Target Types
You'll learn: How to configure different target types for Network Load Balancers and when to use each option.
What Are Target Types?
When you create a Network Load Balancer, you must tell it where to send traffic. These destinations are called "targets," and NLBs support three different target types: instances, IP addresses, and Application Load Balancers (ALBs).
Think of target types like choosing how to address a package: by building name (instance), by street address (IP), or by sending it to another distribution center first (ALB).
The Three Target Types
Instance Targets
You point directly to EC2 instances by their instance ID. The NLB routes traffic using the instance's primary private IP. This is the simplest approach when your backend servers are standard EC2 instances in your VPC.
IP Targets
You specify exact IP addresses (IPv4 or IPv6). This gives you flexibility to target:
- Instances by any of their IPs, not just the primary
- On-premises servers (via VPN or Direct Connect)
- Resources in peered VPCs
- Containerized applications with specific IPs
ALB Targets
You can route NLB traffic to an Application Load Balancer. This creates a two-tier setup: NLB handles Layer 4 (TCP/UDP) with static IPs, while ALB provides Layer 7 features like path-based routing. Use this when you need both NLB's performance characteristics AND ALB's advanced routing.
When to Use Each Type
Choose instances for straightforward EC2 deployments. Choose IPs when you need flexibility beyond VPC boundaries or precise IP control. Choose ALB when you need static IPs with advanced HTTP routing capabilities.
Key Takeaway: NLB target types determine how you register backend resources—instances for simplicity, IPs for flexibility across networks, and ALBs for combining Layer 4 and Layer 7 benefits.