Carrier gateways
A carrier gateway serves two purposes. It allows inbound traffic from a carrier network in a specific location, and it allows outbound traffic to the carrier network and the internet. There is no inbound connection configuration from the internet to a Wavelength Zone through the carrier gateway.
A carrier gateway supports IPv4 traffic.
Carrier gateways are only available for VPCs that contain subnets in a Wavelength Zone. The carrier gateway provides connectivity between your Wavelength Zone and the telecommunication carrier, and devices on the telecommunication carrier network. The carrier gateway performs NAT of the Wavelength instances' IP addresses to the Carrier IP addresses from a pool that is assigned to the network border group. The carrier gateway NAT function is similar to how an internet gateway functions in a Region.
Enabling access to the telecommunication carrier network
To enable access to or from the telecommunication carrier network for instances in a Wavelength subnet, you must do the following:
-
Create a VPC.
-
Create a carrier gateway and attach the carrier gateway to your VPC. When you create the carrier gateway, you can optionally choose which subnets route to the carrier gateway. When you select this option, we automatically create the resources related to carrier gateways, such as route tables and network ACLs. If you do not choose this option, then you must perform the following tasks:
-
Select the subnets that route traffic to the carrier gateway.
-
Ensure that your subnet route tables have a route that directs traffic to the carrier gateway.
-
Ensure that instances in your subnet have a globally unique Carrier IP address.
-
Ensure that your network access control lists and security group rules allow the relevant traffic to flow to and from your instance.
-
Working with carrier gateways
The following sections describe how to manually create a carrier gateway for your VPC to support inbound traffic from the carrier network (for example, mobile phones), and to support outbound traffic to the carrier network and the internet.
Tasks
Create a VPC
You can create an empty Wavelength VPC using the Amazon VPC console, or the AWS CLI.
Create a carrier gateway
After you create a VPC, create a carrier gateway and then select the subnets that route traffic to the carrier gateway.
If you have not opted in to a Wavelength Zone, the Amazon VPC Console prompts you to opt in. For more information, see Manage Zones.
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 association with the subnet
-
Create a security group to access the telecommunication carrier network
By default, a VPC security group allows all outbound traffic. You can create a new security group and add rules that allow inbound traffic from the telecommunication carrier. Then, you associate the security group with instances in the subnet.
Allocate and associate a Carrier IP address with the instance in the Wavelength Zone subnet
If you used the Amazon EC2 console to launch the instance, or you did not use the
associate-carrier-ip-address
option in the AWS CLI, then you must allocate a
Carrier IP address and assign it to the instance:
To allocate and associate a Carrier IP address
-
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" }
-
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", }
View the carrier gateway details
You can view information about your carrier gateway, including the state and the tags.
Manage carrier gateway tags
Tags help you to identify your carrier gateways. You can add or remove tags.
Delete a carrier gateway
If you no longer need a carrier gateway, you can delete it.
If you do not delete the route that has the carrier gateway as the Target, the route is a blackhole route.
Manage 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