Launch an instance on your Outpost rack

Use the following procedure to create a custom route table with a route to the local gateway. You can't use the same route table as the Availability Zone subnets.

To apply route table routes to a particular subnet, you must associate the route table with the subnet. A route table can be associated with multiple subnets. However, a subnet can only be associated with one route table at a time. Any subnet not explicitly associated with a table is implicitly associated with the main route table by default.

You can create a custom route table for your local gateway (LGW) using the AWS Outposts console.

You must associate the VPCs with your LGW route table. They are not associated by default.

Use the following procedure to associate a VPC with a LGW route table.

You can optionally tag your association to help you identify it or categorize it according to your organization's needs.

Add a route entry in the Outpost subnet route table to enable traffic between the Outpost subnets and LGW.

Outpost subnets within a VPC, which is associated with Outpost LGW route tables, can have an additional target type of a Outpost Local gateway ID for their route tables. Consider the case where you want route traffic with a destination address of 172.16.100.0/24 to the customer network through the LGW. To do this, edit the Outpost subnet route table and add the following route with the destination network and a target of the LGW (lgw-xxxx).

VIF groups are logical groupings of virtual interfaces (VIFs). Associate the local gateway route table with the VIF group.

Edit the local gateway route table to add a static route that has the VIF Group as the target and your on-premise subnet CIDR range (or 0.0.0.0/0) as the destination.

If you configured your Outposts in the 3a. Create a custom local gateway route table to use a customer-owned IP (CoIP) address pool, you must allocate an Elastic IP address from the CoIP address pool and associate the Elastic IP address with the instance. For more information about CoIP, see Customer-owned IP addresses.

If you configured your Outposts to use Direct VPC routing (DVR), skip this step.

Shared customer-owned IP address pools

If you want to use a shared customer-owned IP address pool, the pool must be shared before you start the configuration. For information about how to share a customer-owned IPv4 address, see Sharing your AWS resources in the AWS RAM User Guide.

Consider the scenario where you have an Outpost, configured in Direct VPC mode, with two Outposts rack network devices connected by a local gateway VLAN to two customer local network devices. The following is configured:

In this scenario, the route advertised by:

As a result, the local gateway will send outbound traffic with destination network 172.16.100.0/24 to your customer devices. Ensure that your network has the correct routing configuration to deliver traffic to the destination host within your network.

For the specific commands and configuration required to check the state of the BGP sessions and the advertised routes within those sessions, see the documentation from your networking vendor. For troubleshooting, see AWS Outposts rack network troubleshooting checklist.

Consider the scenario where you have an Outpost with two Outposts rack network devices connected by a local gateway VLAN to two customer local network devices. The following is configured:

In this scenario the route advertised by:

As a result the local gateway will send outbound traffic with destination network 172.16.100.0/24 to your customer devices. Ensure that your network has the right routing configuration to deliver traffic to the destination host within your network.

For the specific commands and configuration required to check the state of the BGP sessions and the advertised routes within those sessions, see the documentation from your networking vendor. For troubleshooting, see AWS Outposts rack network troubleshooting checklist.

Test the connectivity from your local network to the Outpost

From a computer in your local network, run the ping command to the Outpost instance's customer-owned IP address.

ping 172.16.0.128

The following is example output.

Pinging 172.16.0.128

Reply from 172.16.0.128:  bytes=32 time=<1ms TTL=128
Reply from 172.16.0.128:  bytes=32 time=<1ms TTL=128
Reply from 172.16.0.128:  bytes=32 time=<1ms TTL=128

Ping statistics for 172.16.0.128
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 an Outpost instance to your local network

Depending on your operating system, use ssh or rdp to connect to the private IP address of your Outpost instance. For information about connecting to a Linux instance, see Connect to your Linux instance in the Amazon EC2 User Guide. For information about connecting to a Windows instance, see Connect to your Windows instance in the Amazon EC2 User Guide.

After the Outpost instance is running, run the ping command to an IP address of a computer in your local network.

ping 172.16.0.130

The following is example output.

Pinging 172.16.0.130

Reply from 172.16.0.130:  bytes=32 time=<1ms TTL=128
Reply from 172.16.0.130:  bytes=32 time=<1ms TTL=128
Reply from 172.16.0.130:  bytes=32 time=<1ms TTL=128

Ping statistics for 172.16.0.130
Packets:  Sent = 3,  Received = 3,  Lost = 0 (0% lost)

Approximate round trip time in milliseconds
Minimum = 0ms,  Maximum = 0ms,  Average = 0ms

Test connectivity between the AWS Region and the Outpost

Launch an instance in the subnet in the AWS Region. For example, use the run-instances command.

aws ec2 run-instances \
    --image-id ami-abcdefghi1234567898 \
    --instance-type c5.large \
    --key-name MyKeyPair \
    --security-group-ids sg-1a2b3c4d123456787 \
    --subnet-id subnet-6e7f829e123445678

After the instance is running, perform the following operations: