1

I've set up an AWS Client VPN to remotely connect to a VPC within my AWS network.

Using this VPN, I am able to initiate remote TCP connections from my PC to an EC2 instance.

I also have a scenario when I want to connect in the reverse direction....EC2 instance to PC. This doesnt work at all and I cant seem to figure out what I need to add to get this to work. I see the packet leave the EC2 instance but it never arrives on my pc.

I have entries in my security group and network ACL right now to allow all inbound/outbound traffic so I think my issue is with the route table? I was thinking I need to add route for my VPN client CIDR block but I dont know what to use as a Target.

I'm new to this so any help would be appreciated. Thanks!

  • I used client VPN a couple of years ago but never connected outbound EC2 to PC. If packets get in OK I don't think it's routing, it's more likely to be security group, or perhaps it's by design. If you can't get it working a VPN set up within the VPC console might be more applicable, but it's more difficult to set up on the PC side. – Tim Aug 26 '22 at 01:53

2 Answers2

0

@Tim So what is the actual purpose of Client VPN if it doesn't allows two way communication. Just curious. Am stuck in the exact same situation

0

Hi @sam joel This is same issue i am face if you resolve this issue kindly help me please,I am waiting anyone can help me on AWS vpn client fault no provide two way communication

  • This does not really answer the question. If you have a different question, you can ask it by clicking [Ask Question](https://serverfault.com/questions/ask). To get notified when this question gets new answers, you can [follow this question](https://meta.stackexchange.com/q/345661). Once you have enough [reputation](https://serverfault.com/help/whats-reputation), you can also [add a bounty](https://serverfault.com/help/privileges/set-bounties) to draw more attention to this question. - [From Review](/review/late-answers/538234) – Dave M Dec 25 '22 at 19:57