2개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
1
Do you have a rule set up in the security group that EC2 has to allow connections from the security group that AWS Client VPN has?
I don't think AWS Client VPN is doing anything to deny communication.
Also, make sure that all communications are allowed in the outbound rules of the AWS Client VPN security group.
0
AWS Client VPN does not block other ports.
Please check below guide, specifically step 5 "Provide access to the internet" and step 6 "Verify security group requirements".
https://docs.aws.amazon.com/vpn/latest/clientvpn-admin/cvpn-getting-started.html
답변함 일 년 전
Hi, I'm able to access the internet and also able to ssh to the same EC2 instance when ssh port is set to 22.
- Make sure port 56565 is being allowed on the EC2 security group, the target EC2.
- Make sure port 56565 is being allowed on the EC2 ACL.
- Make sure port 56565 is being allowed on the CVPN ENI subnet ACL. When you create your CVPN is going to be associated with one or more than one subnet, make sure port 56565 is being allowed on all the subnets ACL that are associated with CVPN ENI's, for instance, you may have 3 subnets for your CVPN (subnet A, subnet B, and subnet C) each of those subnets may have a different ACL, you would need to make sure those subnets allow port 56565.
- If all above being checked and still unable to connect, I suggest checking your EC2 VPC flow logs to see if traffic is reaching the EC2.
관련 콘텐츠
AWS 공식업데이트됨 8달 전- AWS 공식업데이트됨 2년 전
Hi, thanks for the suggestions! For EC2 instance security group, I have allowed the VPN external IP for All traffic and All ports(for testing purpose) AWS VPN security group also has All traffic allowed in the outbound rule. For the same EC2 instance, I'm able to ssh into it on Port 22 with VPN connected, but not able to connect when the ssh port is set to 56565. To me, looks like there is some default restrictions on the special ports.