Tutorial: Communicate Between Two VPCs in AWS Using a Single Access Server⁠

Ensure the following resources are set up in AWS:

• VPC 1: my-first-vpc (Access Server's VPC)

• VPC 2: my-second-vpc (VPC hosting the Ubuntu machine)

Here is an example of the setup:

1. Sign in to your AWS portal and navigate to VPC.

2. Under Virtual private cloud, click Peering connections.

3. Click Create peering connection.

4. Create a name for the peering connection.

5. Select the local VPC to peer with (for this example, my-first-vpc).

6. Select the second VPC to peer with (for this example, my-second-vpc).

7. Review the information and click Create peering connection.

   • A new window shows that the VPC peering connection has been requested, and we need to accept it.

8. Click Actions.

9. Click Accept request.

10. In the pop-up window, click Accept request to finalize the peering connection.

1. Under Virtual private cloud, click Route tables.

2. Click the routing table ID associated with my-first-vpc under the VPC column.

3. Click Edit routes.

4. Add a route to forward the traffic from my-first-vpc to my-second-vpc through the peering connection. The configuration should look like this:

   • Destination: 198.51.100.0/16

   • Target: Peering Connection and ID (e.g., pcx-123abc)

5. Repeat the steps for my-second-vpc to ensure it can route traffic back to my-first-vpc:

   • Destination: 192.0.2.0/16

   • Target: Peering Connection and ID (e.g., pcx-123abc)

1. Sign in to your Access Server Admin Web UI.

2. Click Configuration> VPN Settings.

3. Set routing to Yes, using NAT.

4. Specify the private subnets. Example configuration:

   • 192.0.2.0/16

     198.51.100.0/16

5. Select Save Settings and Update Running Server.

After completing this step, the Ubuntu machine in my-second-vpc should be reachable from a VPN client through the peering connection between the two VPCs.

Once the configuration is complete, you can test connectivity by pinging the Ubuntu machine's private IP from your connected VPN client.

Example:

PS C:\Users\Kevin> ping 198.51.100.188

Pinging 198.51.100.188 with 32 bytes of data:
Reply from 198.51.100.188: bytes=32 time=30ms TTL=63
Reply from 198.51.100.188: bytes=32 time=30ms TTL=63
Reply from 198.51.100.188: bytes=32 time=29ms TTL=63
Reply from 198.51.100.188: bytes=32 time=30ms TTL=63
Reply from 198.51.100.188: bytes=32 time=31ms TTL=63

Ping statistics for 198.51.100.188:
    Packets: Sent = 5, Received = 5, Lost = 0 (0% loss)

If you encounter any issues or need further assistance, contact our support team or submit a ticket.