Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Amazon ECS clusters in Local Zones, Wavelength Zones, and Amazon Outposts

Amazon ECS supports workloads that use Local Zones, Wavelength Zones, and Amazon Outposts for when low latency or local data processing is a requirement.

For information about the differences between Local Zones, Wavelength Zones, and Amazon Outposts , see How should I think about when to use Amazon Wavelength, Amazon Local Zones, or Amazon Outposts for applications requiring low latency or local data processing in the Amazon Wavelength FAQs.

Local Zones

A Local Zone is an extension of an Amazon Web Services Region in close geographic proximity to your users. Local Zones have their own connections to the internet and support Amazon Direct Connect. Resources that are created in a Local Zone can serve local users with low-latency communications. For more information, see Amazon Local Zones.

A Local Zone is represented by a Region code followed by an identifier that indicates the location (for example, us-west-2-lax-1a).

To use a Local Zone, you must opt in to the zone. After you opt in, you must create an Amazon VPC and subnet in the Local Zone. Then, you can launch your Amazon EC2 instances, Amazon FSx file servers, and Application Load Balancers in the Local Zone to use for your Amazon ECS clusters and tasks. For more information, see Local Zones in the Amazon EC2 User Guide for Linux Instances.

Wavelength Zones

You can use Amazon Wavelength to build applications that deliver ultra-low latency to mobile devices and end users. Wavelength deploys standard Amazon compute and storage services to the edge of telecommunication carriers' 5G networks. You can extend an Amazon Virtual Private Cloud to one or more Wavelength Zones. Then, you can use Amazon resources such as Amazon EC2 instances to run applications that require ultra-low latency and a connection to Amazon Web Services in the Region.

A Wavelength Zone is an isolated Zone in the carrier location where the Wavelength infrastructure is deployed. Wavelength Zones are tied to an Amazon Web Services Region. A Wavelength Zone is a logical extension of a Region, and is managed by the control plane in the Region.

A Wavelength Zone is represented by a Region code followed by an identifier that indicates the Wavelength Zone (for example, us-east-1-wl1-bos-wlz-1).

To use a Wavelength Zone, you must opt in to the Zone. After you opt in, you must create an Amazon VPC and subnet in the Wavelength Zone. Then, you can launch your Amazon EC2 instances in the Zone to use for your Amazon ECS clusters and tasks. For more information, see Get started with Amazon Wavelength in the Amazon Wavelength Developer Guide.

Wavelength Zones aren't available in all Amazon Web Services Regions. For information about the Regions that support Wavelength Zones, see Available Wavelength Zones in the Amazon Wavelength Developer Guide.

Amazon Outposts

Amazon Outposts uses native Amazon Web Services, infrastructure, and operating models in on-premises facilities. In Amazon Outposts environments, you can use the same Amazon APIs, tools, and infrastructure that you use in the Amazon Cloud. Amazon ECS on Amazon Outposts is suitable for low-latency workloads that require to be run in close proximity to on-premises data and applications. For more information about Amazon Outposts, see Amazon Elastic Container Service on Amazon Outposts.