Available Wavelength Zones and considerations for AWS Wavelength - AWS Wavelength

Available Wavelength Zones and considerations for AWS Wavelength

This topic provides a list of available Wavelength Zones as well as considerations for working with AWS Wavelength.

Available Wavelength Zones

The following table lists the Wavelength Zones that an AWS account provides.

AWS Region Location Carrier Wavelength Zone ID Network Border Group
US East (N. Virginia) Atlanta Verizon us-east-1-wl1-atl-wlz-1 us-east-1-wl1-atl-wlz-1
US East (N. Virginia) Boston Verizon us-east-1-wl1-bos-wlz-1 us-east-1-wl1-bos-wlz-1
US East (N. Virginia) Charlotte Verizon us-east-1-wl1-clt-wlz-1 us-east-1-wl1-clt-wlz-1
US East (N. Virginia) Chicago Verizon us-east-1-wl1-chi-wlz-1 us-east-1-wl1-chi-wlz-1
US East (N. Virginia) Dallas Verizon us-east-1-wl1-dfw-wlz-1 us-east-1-wl1-dfw-wlz-1
US East (N. Virginia) Detroit Verizon us-east-1-wl1-dtw-wlz-1 us-east-1-wl1-dtw-wlz-1
US East (N. Virginia) Houston Verizon us-east-1-wl1-iah-wlz-1 us-east-1-wl1-iah-wlz-1
US East (N. Virginia) Miami Verizon us-east-1-wl1-mia-wlz-1 us-east-1-wl1-mia-wlz-1
US East (N. Virginia) Minneapolis Verizon us-east-1-wl1-msp-wlz-1 us-east-1-wl1-msp-wlz-1
US East (N. Virginia) Nashville Verizon us-east-1-wl1-bna-wlz-1 us-east-1-wl1-bna-wlz-1
US East (N. Virginia) New York City Verizon us-east-1-wl1-nyc-wlz-1 us-east-1-wl1-nyc-wlz-1
US East (N. Virginia) Tampa Verizon us-east-1-wl1-tpa-wlz-1 us-east-1-wl1-tpa-wlz-1
US East (N. Virginia) Washington DC Verizon us-east-1-wl1-was-wlz-1 us-east-1-wl1-was-wlz-1
US West (Oregon) Denver Verizon us-west-2-wl1-den-wlz-1 us-west-2-wl1-den-wlz-1
US West (Oregon) Las Vegas Verizon us-west-2-wl1-las-wlz-1 us-west-2-wl1-las-wlz-1
US West (Oregon) Los Angeles Verizon us-west-2-wl1-lax-wlz-1 us-west-2-wl1-lax-wlz-1
US West (Oregon) Phoenix Verizon us-west-2-wl1-phx-wlz-1 us-west-2-wl1-phx-wlz-1
US West (Oregon) San Francisco Bay area Verizon us-west-2-wl1-sfo-wlz-1 us-west-2-wl1-sfo-wlz-1
US West (Oregon) Seattle Verizon us-west-2-wl1-sea-wlz-1 us-west-2-wl1-sea-wlz-1
Asia Pacific (Seoul) Daejeon SKT ap-northeast-2-wl1-cjj-wlz-1 ap-northeast-2-wl1-cjj-wlz-1
Asia Pacific (Seoul) Seoul SKT ap-northeast-2-wl1-sel-wlz-1 ap-northeast-2-wl1-sel-wlz-1
Asia Pacific (Tokyo) Osaka KDDI ap-northeast-1-wl1-kix-wlz-1 ap-northeast-1-wl1-kix-wlz-1
Asia Pacific (Tokyo) Tokyo KDDI ap-northeast-1-wl1-nrt-wlz-1 ap-northeast-1-wl1-nrt-wlz-1
Canada (Central) Toronto Bell ca-central-1-wl1-yto-wlz-1 ca-central-1-wl1-yto-wlz-1
Europe (Frankfurt) Berlin Vodafone eu-central-1-wl1-ber-wlz-1 eu-central-1-wl1-ber-wlz-1
Europe (Frankfurt) Dortmund Vodafone eu-central-1-wl1-dtm-wlz-1 eu-central-1-wl1-dtm-wlz-1
Europe (Frankfurt) Munich Vodafone eu-central-1-wl1-muc-wlz-1 eu-central-1-wl1-muc-wlz-1
Europe (London) London Vodafone eu-west-2-wl1-lon-wlz-1 eu-west-2-wl1-lon-wlz-1

For more information, see AWS Global Infrastructure.

The number and mapping of Wavelength Zones per Region might vary between AWS accounts. To get a list of the Wavelength Zones that are available to your account, you can use the Amazon EC2 console or the command line interface.

Networking considerations

The following controls are enabled by the carrier gateway for internet flows by default and cannot be removed:

Protocol Between EC2 instance and the internet Between EC2 instance and a device on the carrier network
TCP outbound and the response allowed
UDP denied allowed
ICMP allowed allowed
  • TCP is allowed for outbound and response

  • UDP from the internet is denied

    UDP traffic from a device on the carrier network is allowed to route to an EC2 instance in a Wavelength Zone.

  • ICMP is allowed

In addition, inbound routing from the carrier network is optimized for devices in the location of the Wavelength Zone. For example, a Wavelength Zone in the San Francisco Bay area allows low latency access only from devices that are in that metro area and carrier network.

Multiple Wavelength Zone considerations

EC2 instances that are in two different Wavelength Zones in the same VPC are not allowed to communicate with each other. If you need communication from one Wavelength Zone to another Wavelength Zone, we recommends that you use multiple VPCs, one for each Wavelength Zone. You can use a transit gateway to connect the VPCs. This configuration enables communication between instances in the Wavelength Zones. For information about how to configure multiple Wavelength Zones, see Extend your VPC resources to Local Zones in theAmazon VPC User Guide.

Amazon EC2 considerations

Take the following information into consideration when you launch EC2 instances in Wavelength Zones:

  • The following instance types are supported:

    • t3.medium

    • t3.xlarge

    • r5.2xlarge

    • g4dn.2xlarge

  • You cannot use dedicated instances or hosts.

  • EC2 quotas are controlled by the quotas for the home Region.

You can find the EC2 instance types available by using the describe-instance-type-offerings command.

aws ec2 describe-instance-type-offerings --location-type availability-zone --filters Name=location,Values=us-east-1-wl1-bos-wlz-1 --region us-east-1

Output

{ "InstanceTypeOfferings": [ { "InstanceType": "t3.xlarge", "LocationType": "availability-zone", "Location": "us-east-1-wl1-bos-wlz-1" }, { "InstanceType": "t3.medium", "LocationType": "availability-zone", "Location": "us-east-1-wl1-bos-wlz-1" }, { "InstanceType": "r5.2xlarge", "LocationType": "availability-zone", "Location": "us-east-1-wl1-bos-wlz-1" }, { "InstanceType": "g4dn.2xlarge", "LocationType": "availability-zone", "Location": "us-east-1-wl1-bos-wlz-1" } ] }

Amazon EBS considerations

Take the following information into consideration when you use Amazon Elastic Block Store for EC2 instances that are in Wavelength Zones:

  • Snapshots of EBS volumes and AMIs are stored in the AWS Region.

  • You can only use gp2 volumes.

  • The default limit for gp2 storage is 30 TB.

    You can request an increase for this value.

Amazon Elastic Kubernetes Service considerations

Take the following information into consideration when you run an Amazon EKS cluster:

  • You must run Kubernetes 1.17 or later.

  • When you create your Amazon EKS cluster, you must select an Availability Zone in the VPC, and not a Wavelength Zone.

  • When you create your Amazon EKS cluster for private subnets only, you need to add VPC endpoints for Amazon ECR and Amazon Simple Storage Service. For more information, see Amazon VPC considerations.

  • To create node groups in Wavelength Zones for your Amazon EKS cluster, see Launching self-managed Amazon Linux 2 nodes in the Amazon EKS User Guide.

  • To apply the aws-auth ConfigMap to your Amazon EKS cluster, see Managing users or IAM roles for your cluster in the Amazon EKS User Guide.

Amazon VPC considerations

Take the following information into consideration when you run Amazon VPC:

  • If you want to use VPC endpoints, you must create the endpoint in an Availability Zone in the VPC. You cannot create the endpoint in a Wavelength Zone.

  • You cannot assign IPv6 addresses to subnets that are in Wavelength Zones.

Application Load Balancer considerations

You can use an Application Load Balancer only in a Wavelength Zone in the United States. You cannot use an Application Load Balancer in Wavelength Zones that are in AWS Regions outside of the United States. For more information, see the User Guide for Application Load Balancer.

Service quota considerations

Wavelength VPCs and Wavelength subnets count toward your Amazon VPC service quotas. For more information about Amazon VPC quotas, see Amazon VPC quotas in the Amazon VPC User Guide.

You can use the Service Quotas console (https://console.aws.amazon.com/servicequotas/) to view your EC2, EBS, and VPC quotas. For more information about how to view your service quotas, see Viewing service quotas in the Service Quotas User Guide.