Client VPN access to VPC

0

We have a single VPC that up until now we controlled access to an EC2 instance via firewall rules permitting a static IP from specific company offices. We now have a need to have a freelance developer get access to the EC2 instance, but we do not want to give access to our corporate remote access nor do they have a static IP.

I'm attempting to setup client VPN into the VPC. We have gotten as far as connecting, but can't seem to get access to the EC2 instance via SSH (or even ping it).

Example IPs:
EC2 VPC IP 10.0.0.2
EC2 default gateway 10.0.0.1
Client VPN IP 10.0.1.2

I'm able to ping 10.0.0.1 (the VPC default gateway) from both the EC2 instance and the client VPN, so this gives me the impression that the routing is setup correctly. I cannot ping the EC2 instance 10.0.0.2 from the client VPN. The default route on the EC2 instance is 10.0.0.1, so it shouldn't require any routing back to the client VPN network.

We setup ingress rules on the security group associated with the VPC to allow ICMP and SSH from 10.0.1.0/24, but no joy.

Any suggestions on where to look next?

morleyz
已提問 3 年前檢視次數 467 次
1 個回答
0

Disregard. Turns out I had to add the VPC subnet to the ingress rules because the client VPN is NATed.

morleyz
已回答 3 年前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南