Get started with AWS Wavelength - AWS Wavelength

Get started with AWS Wavelength

The following diagram shows the resources that you need to configure to get started using AWS Wavelength.


      AWS Wavelength getting started overview

You need to configure the following resources:

  • A VPC in your Region

  • A carrier gateway

    When you create the carrier gateway, you can also create the subnet. AWS automatically creates the route table, routes, and subnet association.

  • A public subnet in an Availability Zone in your Region

  • An instance in the public subnet

  • An instance in the Wavelength Zone subnet with a Carrier IP address

Before you begin, review Wavelength considerations and quotas, which includes information about available Wavelength Zones, service differences, and Service Quotas.

Step 1: Opt in to Wavelength Zones

Before you specify a Wavelength Zone for a resource or service, you must opt in to the zone.

You need to request access in order to use Wavelength Zones, before you opt in. For information about how to request Wavelength Zone access, see AWS Wavelength.

Step 2: Configure your network

After you opt in to the Wavelength Zone, create a VPC, a carrier gateway, and a public subnet in the Availability Zone.

Prerequisite

You must have opted in to the Wavelength Zone.

Step 1: Create a VPC

Create a VPC using the Amazon VPC Console.

To create a VPC using the console

  1. Open the Amazon VPC console at https://console.aws.amazon.com/vpc/.

  2. In the navigation pane, choose Your VPCs, Create VPC.

  3. Specify the following VPC details as necessary:

    • Name tag: Optionally provide a name for your VPC. Doing so creates a tag with a key of Name and the value that you specify.

    • IPv4 CIDR block: Specify an IPv4 CIDR block for the VPC. We recommend that you specify a CIDR block from the private (non-publicly routable) IP address ranges as specified in RFC 1918; for example, 10.0.0.0/16, or 192.168.0.0/16.

      Note

      You can specify a range of publicly routable IPv4 addresses. However, we currently do not support direct access to the internet from publicly routable CIDR blocks in a VPC. Windows instances cannot boot correctly if launched into a VPC with ranges from 224.0.0.0 to 255.255.255.255 (Class D and Class E IP address ranges).

  4. Choose Create.

Step 2: Create a carrier gateway and a subnet associated with the Wavelength Zone

After you create a VPC, create a carrier gateway, and then select the subnets that route traffic to the carrier gateway.

When you choose to automatically route traffic from subnets to the carrier gateway, we create the following resources:

  • A carrier gateway

  • A subnet. You can optionally assign all carrier gateway tags that do not have a Key value of Name to the subnet.

  • A network ACL with the following resources:

    • A subnet associated with the subnet in the Wavelength Zone

    • Default inbound and outbound rules for all of your traffic.

  • A route table with the following resources:

    • A route for all local traffic

    • A route that routes all non-local traffic to the carrier gateway

    • An associated with the subnet

To create a carrier gateway

  1. Open the Amazon VPC console at https://console.aws.amazon.com/vpc/.

  2. In the navigation pane, choose Carrier Gateways, and then choose Create carrier gateway.

  3. Optional: For Name, enter a name for the carrier gateway.

  4. For VPC, choose the VPC.

  5. Choose Route subnet traffic to carrier gateway, and under Subnets to route do the following.

    1. Under Existing subnets in Wavelength Zone, select the box for each Wavelength subnet to route to the carrier gateway.

    2. To create a subnet in the Wavelength Zone, choose Add new subnet, specify the following information, and then choose Add new subnet:

      • Name tag: Optionally provide a name for your subnet. Doing so creates a tag with a key of Name and the value that you specify.

      • VPC: Choose the VPC.

      • Availability Zone: Choose the Wavelength Zone.

      • IPv4 CIDR block: Specify an IPv4 CIDR block for your subnet, for example, 10.0.1.0/24.

      • To apply the carrier gateway tags to the subnet, select Apply same tags from this carrier gateway.

  6. (Optional) To add a tag to the carrier gateway, choose Add tag, and then do the following:

    • For Key, enter the key name.

    • For Value, enter the key value.

  7. Choose Create carrier gateway.

Step 3: Create a public subnet in an Availability Zone in the Region

Create a subnet in an Availability Zone in the Region.

To add a subnet

  1. Open the Amazon VPC console at https://console.aws.amazon.com/vpc/.

  2. In the navigation pane, choose Subnets, Create subnet.

  3. Specify the subnet details as necessary and choose Create.

    • Name tag: Optionally provide a name for your subnet. Doing so creates a tag with a key of Name and the value that you specify.

    • VPC: Choose the VPC for which you're creating the subnet.

    • Availability Zone: Select an Availability Zone that is in your Region, or select No Preference to have AWS choose one for you.

    • IPv4 CIDR block: Specify a public IPv4 CIDR block for your subnet.

Step 3: Launch an instance in your Availability Zone public subnet

Launch an EC2 instance in the subnet that you created in the Availability Zone. You will use this instance to test the connectivity from the Region to the Wavelength Zone.

You can launch EC2 instances in the public subnet that you created. For information about how to launch an instance in the Amazon EC2 console, see one of the following guides:

  • For Linux instances, see Launch an instance in the Amazon Elastic Compute Cloud User Guide for Linux Instances.

  • For Windows instances, see Launch an instance in the Amazon Elastic Compute Cloud User Guide for Windows Instances.

Step 4: Launch an instance for your Wavelength application

After you complete the networking configuration, launch an instance, and then allocate a Carrier IP address for the instance.

Option 1: Launch an instance in the Wavelength Zone subnet and auto assign the Carrier IP address using the AWS CLI

AWS recommends that you use the run-instances command, because you can use an option to automatically allocate and associate the Carrier IP address with the network interface.

To launch an instance in a Wavelength Zone

  • Use the run-instances command to launch an instance in the Wavelength Zone subnet. Use the following options:

    • subnet: Set the value to the ID of the subnet in the Wavelength Zone.

    • AssociateCarrierIpAddress: Set this value to true. This option assigns a Carrier IP address to the network interface for eth0.

    For more information about launching an instance, see run-instances in the AWS CLI Command Reference.

    Example

    aws ec2 --region us-east-1 run-instances --network-interfaces '[{"DeviceIndex":0, "AssociateCarrierIpAddress": true, "SubnetId": "subnet-036aa298f4EXAMPLE"}]' --image-id ami-04125ecea1EXAMPLE --instance-type t3.medium

Option 2: Launch an instance in the Wavelength Zone subnet and allocate and associate a Carrier IP address from the network border group

You can launch EC2 instances in the subnet that you created when you added the carrier gateway. For more information, see Step 2: Create a carrier gateway and a subnet associated with the Wavelength Zone. Security groups control inbound and outbound traffic for instances in a subnet, just as they do for instances in an Availability Zone subnet. To connect to an EC2 instance in a subnet, specify a key pair when you launch the instance, just as you do for instances in an Availability Zone subnet. For information about how to launch an instance in the Amazon EC2 console, see one of the following guides:

  • For Linux instances, see Launch an instance in the Amazon Elastic Compute Cloud User Guide for Linux Instances.

  • For Windows instances, see Launch an instance in the Amazon Elastic Compute Cloud User Guide for Windows Instances.

To allocate and associate a Carrier IP address

  1. Use allocate-address to allocate a Carrier IP address. For more information, see allocate-address in the AWS CLI Command Reference.

    Example

    aws ec2 allocate-address --region us-east-1 --domain vpc --network-border-group us-east-1-wl1-bos-wlz-1

    Output

    { "AllocationId": "eipalloc-05807b62acEXAMPLE", "PublicIpv4Pool": "amazon", "NetworkBorderGroup": "us-east-1-wl1-bos-wlz-1", "Domain": "vpc", "CarrierIp": "155.146.10.111" }
  2. Use associate-address to associate the Carrier IP address with the EC2 instance. For more information, see associate-address in the AWS CLI Command Reference.

    Example

    aws ec2 associate-address --allocation-id eipalloc-05807b62acEXAMPLE --network-interface-id eni-1a2b3c4d

    Output

    { "AssociationId": "eipassoc-02463d08ceEXAMPLE", }

Step 5: Test the connectivity

Before you test the connectivity, review Networking considerations.

Test the connectivity from the instance in the Region to the Wavelength Zone instance. Depending on your operating system, use ssh or rdp to connect to the Carrier IP address of your Region instance. You can use a secure bastion host.

Before you run these tests, configure the VPC security group to allow ICMP traffic. For more information, see Creating a security group in the Amazon VPC User Guide.

Run the ping command to the Wavelength Zone instance. In the following example, the IP address of the subnet in the Wavelength Zone is 10.0.3.112.

ping 10.0.3.112 Pinging 10.0.3.112 Reply from 10.0.3.112: bytes=32 time=<1ms TTL=128 Reply from 10.0.3.112: bytes=32 time=<1ms TTL=128 Reply from 10.0.3.112: bytes=32 time=<1ms TTL=128 Ping statistics for 10.0.3.112 Packets: Sent = 3, Received = 3, Lost = 0 (0% lost) Approximate round trip time in milliseconds Minimum = 0ms, Maximum = 0ms, Average = 0ms

Test the connectivity from the instance in the Wavelength Zone instance to the carrier network. Depending on your operating system, use ssh or rdp to connect to the Carrier IP address of your Wavelength Zone instance. You can use a secure bastion host.

You need a device on the carrier network in order to test the connectivity from the Wavelength Zone to the carrier network. In addition, Headspin, which is part of the AWS Partner Network, provides devices on carrier networks for functional testing. For more information, see Headspin.

Run the ping command to an address in the carrier network. In the following example, the carrier network IP address is 198.51.100.130.

ping 198.51.100.130 Pinging 198.51.100.130 Reply from 198.51.100.130: bytes=32 time=<1ms TTL=128 Reply from 198.51.100.130: bytes=32 time=<1ms TTL=128 Reply from 198.51.100.130: bytes=32 time=<1ms TTL=128 Ping statistics for 198.51.100.130 Packets: Sent = 3, Received = 3, Lost = 0 (0% lost) Approximate round trip time in milliseconds Minimum = 0ms, Maximum = 0ms, Average = 0ms