In Chapter 3, we discussed how mobile network operators (MNOs) are eager to build multi-access edge computing (MEC) offerings to develop new revenue streams for their 5G infrastructure investments. However, they are not cloud service providers (CSPs). They usually do not have the in-house expertise to operationalize a customer-facing multitenant service such as this. Enter AWS Wavelength. In 2019, AWS partnered with several MNOs to build a joint service offering that extends the reach of AWS regions into their network footprint. AWS Wavelength allows customers to deploy the same compute, storage, and managed database services they are used to right at the edge of these MNOs’ networks.

A Wavelength Zone is really just a special type of Local Zone. The only difference with a Wavelength Zone is that they are designed to be as close to an MNO’s packet core as possible. Wavelength Zones are available in cooperation with Verizon in the US, KDDI in Japan, SK Telecom in South Korea, Vodafone in the UK and Germany, British Telecom (BT) in the UK, and Bell in Canada.

This chapter will explain AWS Wavelength Zones and review architectural patterns that have proven successful with customers. In particular, we will look at the following topics:

Introduction to AWS Wavelength Zones

Connecting to AWS Wavelength from mobile devices

Extending a Virtual Private Cloud (VPC) into AWS Wavelength

Integrating AWS Wavelength with other services

Introduction to AWS Wavelength Zones

While AWS Local Zones bring AWS services closer to end users, AWS Wavelength Zones take it one step further, embedding these services within carrier networks themselves. This tight integration ensures that 5G clients experience ultra-low latencies, while even 4G/LTE clients benefit from significantly improved response times.

AWS Wavelength Zones represent a fusion of cloud computing with mobile edge computing, setting the stage for the next generation of latency-sensitive applications.