"The reason is that the vMX (and any MX for that matter) will not route from a Meraki Auto-VPN connection to a 3rd party site to site connection." Meraki support has confirmed this, but it's a shame this isn't documented anywhere. Regardless, our only options seem to be: Add Meraki vMXs to each VPC that we need to connect to...using Auto-VPN to connect all hardware and virtual MXs. OR Link hardware MXs to each other via Auto-VPN and then also create an individual VPN connection between every office and every VPC. ... View more

Has anyone tried this?       office MX(s)> <AUTOVPN> <vMX in VPC-A> <IPsec Tunnel> <AWS Managed VPN in VPC-B   I can't really find much on this approach, but in theory it should work...Even with tunnels from the vMX to multiple VPCs right? ... View more

Here's our plan that we are about to test:   We'll have our vMX living in a VPC that will connect to branch office Meraki hardware via Auto-VPN We'll have our vMX connect to other VPCs via IPSec/AWS VPN Gateways in each VPC.   Anyone else doing this type of thing?   ... View more