Tutorial: Connect VPN Clients to Another EC2 Instance in AWS When Access Server Uses Route Mode⁠

Sign in to the AWS Management Console.

Navigate to VPC.

Under Virtual private cloud, select Route tables.

Select the route table associated with the Ubuntu EC2 instance.

Under Routes, select Edit routes.

Select Add route.

Configure the route:

• Destination: 198.51.100.0/24

• Target: Select the Access Server EC2 instance.

Select Save changes.

Navigate to your Access Server EC2 instance.

Select Actions → Networking → Change source/destination check.

Select the Stop checkbox under Source / destination checking.

Select Save to disable the check.

Sign in to the Admin Web UI.

Select Access Controls.

Select the Global Access Rules tab.

Verify the routing mode is Route.

Add the Ubuntu subnet (192.0.2.128/25) to Subnets.

Select Save and Restart.

Connect to the VPN.

Ping the Ubuntu EC2 instance:

ping 192.0.2.135

• Expected result example from a Windows client:

  Pinging 192.0.2.135 with 32 bytes of data:
  Reply from 192.0.2.135: bytes=32 time=30ms TTL=63
  Reply from 192.0.2.135: bytes=32 time=30ms TTL=63
  Reply from 192.0.2.135: bytes=32 time=29ms TTL=63
  Reply from 192.0.2.135: bytes=32 time=30ms TTL=63
  Reply from 192.0.2.135: bytes=32 time=31ms TTL=63
  Ping statistics for 192.0.2.135:
      Packets: Sent = 5, Received = 5, Lost = 0 (0% loss)