AWS Load Balancer

handle TCP, TLS, UDP, HTTP/HTTPS all together

Classic LB will support TCP, TLS, and HTTP but will not support UDP

To handle all this traffic, you can just use NLB

# 1.NLB
client -> NLB -> TG

NLB support TCP, TLS, UDP, 
and HTTP/HTTPS is based on TCP so support all



# 2. NLB + ALB

client 
 |
\|/ 
NLB 
 |
\|/
NLB-TG <- register IP via Lambda (call Lambda function for resolving IP of ALB)          
 |
\|/
ALB 
 |
\|/
ALB-TG


take all traffic to NLB and 
in NLB-TG forward HTTP/HTTPS traffic to ALB
via direct IP of ALB (manually)

NLB + ALB + Lambda

Using static IP addresses for Application Load Balancers

Using AWS Lambda to enable static IP addresses for Application Load Balancers | Amazon Web ServicesAmazon Web Services

It is the first page when creating the NLB. You have to chose AZs and subnets. When doing that, there is an option for selecting the EIP