Your question is too vague to give a clear answer. If the VPN is showing that it has one or more tunnels up in the console, then it is likely that you have configured the VPN correctly.
On a high level, you now need to ensure that you have:
- Attached the VGW to the VPC in which your EC2 instance lies
- Ensure that you either enable route propagation into the route table being used by the subnet in which your AWS resource is, or create a static route that covers the local IP address prefix on your customers side as a destination to the VGW in the route-table used by your subnet.
- On the customer gateway side, you need to make sure that you have a route entry to the VPN that covers at least the prefix used by the subnet in AWS in which you have the resource you would like to reach
- Make sure that the security groups of the resource that you want to reach allows ingress traffic from the on premise network to the ports and protocols that you want to use. By default egress is allowed from ec2 resources - if you have changed that - you need to also cater to egress traffic back to on premise network.
- asked 3 years ago
- Accepted Answerasked 2 months ago
- Accepted Answerasked 7 months ago
- AWS OFFICIALUpdated 2 years ago
- Why is my AWS Site-to-Site VPN connection in the DOWN IPSEC UP status when the customer gateway is UP?AWS OFFICIALUpdated 9 months ago
- Why can't I connect to my VPC when using an AWS Site-to-Site VPN connection that terminates on a virtual private gateway?AWS OFFICIALUpdated 10 months ago