Network Load Balancer arrives in the Phoenix Local Zone, no more detours to the parent Region
Hi everyone, it's Shii-chan! Today's news is about Local Zones.
AWS What's NewWhat was announced?
According to AWS What's New, AWS Network Load Balancer is now available in the Phoenix Local Zone (us-west-2-phx-2a).
AWS Local Zones place compute, storage, database, and other select services closer to large population, industry, and IT centers where no AWS Region exists today.
The story so far
Even if your targets ran in the Phoenix Local Zone, the load balancer had to be in an Availability Zone in the parent Region. Connections and traffic traveled to the parent Region and back, adding latency and routing traffic outside the zone where your application runs.
What changes
- Connection routing stays local to your targets
- Lower and more consistent latency for users in the Phoenix metro area
- Traffic stays within the Local Zone
AWS says this is especially valuable for latency-sensitive workloads such as real-time gaming, media streaming, and live financial applications.
Dive Deep
- You can create a Network Load Balancer directly in the Phoenix Local Zone
- Enable Local Zones from the Local Zones tab in the AWS Global View console, or with the ModifyAvailabilityZoneGroup API
- The Locations page lists available and announced Local Zones
Wrap-up
- Network Load Balancer is available in the Phoenix Local Zone
- No more round trips to the parent Region, so lower latency
- Suited to gaming, streaming, and finance
This is for anyone serving users around Phoenix!