Static IP and Elastic IP Support
What you'll learn: How to configure Network Load Balancers with fixed IP addresses that never change, enabling firewall rules and predictable endpoints.
The Problem with Dynamic Addresses
By default, load balancers can have IP addresses that change over time. This creates challenges when:
- Partner organizations need to whitelist your endpoints in their firewalls
- Compliance requires documenting exact IP addresses
- Legacy systems can't use DNS and need hardcoded IPs
Static IPs and Elastic IPs for NLBs
Network Load Balancers uniquely support static IP addresses — one per availability zone. You have two options:
- AWS-assigned static IPs: AWS automatically assigns a fixed IP per AZ that never changes
- Elastic IP attachment: You bring your own Elastic IPs (one per AZ), giving you complete control over the exact addresses
Think of it like this: A traditional load balancer is like a mobile food truck that parks in different spots. An NLB with Elastic IPs is like a restaurant with a permanent street address — customers (and firewall admins) always know exactly where to find you.
Why This Matters
- Firewall whitelisting: Partners can add your NLB's IPs to their allow-lists without worry
- IP portability: Move Elastic IPs between NLBs during migrations or failovers
- Predictable endpoints: Hard-coded integrations remain stable
- Compliance documentation: Fixed IPs simplify audit trails
Unlike Application Load Balancers (which only provide DNS names with changing IPs), NLBs give you the addressing stability that enterprise networks often require.
Key Takeaway: Network Load Balancers support static IPs (AWS-assigned) or Elastic IPs (customer-provided) for each availability zone, providing predictable, whitelist-friendly endpoints that never change.