Routing internet traffic into AWS Local Zones
So far, we’ve covered use cases that involve traffic to and from an existing on-premises data center. This section will review options to address situations where the traffic originates from various locations on the internet.
Application Load Balancer
When an Elastic Load Balancer is set up in an AWS Local Zone, it is done in much the same way as it is in any standard availability zone. First, unlike in a standard region, you only need to assign one subnet. Second, only the layer 7 Application Load Balancer (ALB) variant is available. Layer 4, or network load balancers (NLB), cannot be deployed to an AWS Local Zone.
Amazon Route53 for load balancing
Although ALB addresses layer 7 load-balancing use cases, some low-latency applications that get deployed in AWS Local Zones rely on UDP-based protocols, such as QUIC, WebRTC, and SRT, which can’t be load-balanced by layer 7 load balancers.