While Regions, Availability Zones, and Edge Locations are typically considered the main components of the AWS global infrastructure, they are certainly not the only components. In this section, we examine more components (including connections) that you can work with when using AWS.

AWS Local Zones

AWS Local Zones are a relatively new concept for the AWS global infrastructure. These zones are an attempt by Amazon to place compute, storage, database, and other key service resources closer to large population and industry centers around the world. For example, because Chicago is such a bustling US city filled with industry, AWS created the Chicago local zone (us-east-1-chi-1a).

Notice for AWS Local Zones to be truly useful, they must support the most popular and foundational AWS services users tend to rely upon every day, including the following:

A hugely important aspect of AWS Local Zones is that customers do not pay extra for them. When you use Local Zones, you are still charged on demand for resources, just as you are for your typical AWS resources in typical Availability Zones. In fact, you can even still take advantage of On-Demand Capacity Reservations with AWS Local Zones in an attempt to save even more money.

AWS Wavelength Zones

AWS Wavelength Zones are another relatively new part of AWS Regions. These zones exist to carry the new AWS Wavelength infrastructure. AWS Wavelength allows developers to construct apps that deliver ultra-low latency to mobile devices and their end users. The idea here is to place AWS compute and storage resources close to the edge of communications service providers’ 5G networks to speed things up for end users. These components are also used with AWS Wavelength Zones:

AWS resources that can be used with Wavelength Zones currently include the following: