I’ve successfully set up IPSec VPN connections to an AWS VPN gateway which I was pretty excited about. Unfortunately, I can’t seem to connect to an ec2 instance running in the VPC I’ve configured with the VPN. I suspect it’s something to do with a routing config, or that the Peplink VPN is just not configurable in the way that AWS require. I’m wondering if it’s something to do with the ‘inside’ IP addresses that the AWS generic VPN configuration describes. I haven’t found a way to configure the customer ‘inside’ address on my end of the VPN, but ignoring that, I’ve been able to set up a connection to the AWS VPN that apparently is connected - both ends show that the connection is up.
I configured my end of the tunnel with the subnet of my remote AWS VPC (10.2.0.0/24) and also confirmed that the firewall is configured to allow traffic to this subnet. At the AWS end, I’ve confirmed that the VPN is configured to route to my local subnet (192.168.100.0/24) and that subnet 10.2.0.0/24 has a routing table entry to 192.168.100.0/24 via the VPN gateway. However, when I try and access the instance at 10.2.0.78 from my local end, it just times out. Traceroute just stops at my Peplink router’s internal IP, ssh also just hangs as well. I also confirmed that the EC2 instance’s security group has open access on port 22 (for the purposes of this test).
Has anyone successfully been able to not only set up a successful IPSec connection to AWS, but also access their EC2 instances at the other end? Any help would be appreciated!
EDIT: Changed 192.168.0.0/24 to 192.168.100.0/24 and 10.3.0.0/16 to 10.2.0.0/16 as these are the correct values.