I have an Amazon VPC set up between AWS and my corporate LAN.
Originally, when I set it up, I specified static routing for the following CIDRs:
10.55.55.0/24 10.77.77.0/24 10.99.99.0/24
I set up the following CIDR in the VPC:
10.44.0.0/16
This all worked fine.
I now have a new network on my Corporate LAN: 10.55.54.0/24
I added a new route in the main routing table for this, pointing to the same vgw as the others.
When I know look at the routes, I see that the original 3 routes are propagated, but the 4th new one is not.
On a server instance in 10.44.0.0/16, I can still connect to hosts in the existing 3 CIDRs, but I am not seeing any routing for the new CIDR:
[server]$ traceroute 10.55.55.88
traceroute to 10.55.55.88 (10.55.55.88), 30 hops max, 60 byte packets
1 169.254.254.37 (169.254.254.37) 0.543 ms 0.524 ms 0.504 ms
2 169.254.254.5 (169.254.254.5) 1.278 ms 1.007 ms 0.985 ms
3 169.254.254.2 (169.254.254.2) 32.596 ms 169.254.254.6 (169.254.254.6) 35.244 ms 169.254.254.2 (169.254.254.2) 32.830 ms
4 ip-10-55-55-88.eu-west-1.compute.internal (10.55.55.88) 36.822 ms 37.338 ms 36.842 ms
[server]$ traceroute 10.55.54.88
traceroute to 10.55.54.88 (10.55.54.88), 30 hops max, 60 byte packets
<timeout>
What step am I missing here? Do I have to recreate the entire VPC/VPN to include the new CIDR?