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년 전

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠