Once you have created your VPN gateway and customer gateway, you are then in a position where you can begin to add routing configuration to your subnets to allow you to route traffic across to your corporate site via the VPN site-to-site connection.
Let’s take a look at an example:
As you can see, AWS VPC has a 10.0.1.0/24 subnet within the VPC CIDR block of 10.0.0.0/16. The main route table has a manually added static route pointing to the network address space within the corporate data center on the other side of the VPN connection. You will notice that this route has been added with the destination pointing to our VPN gateway (vgw-wxyz6789). As a result of this route, any traffic destined for this network will go via the VPN gateway.
A key point of understanding AWS routing in general is the principle of the longest prefix match. Understanding this can really help you troubleshoot routing issues. Longest prefix match determines...
