Inteded to connect on prem infrastructure with AWS cloud to be able to share data from different locations across the organisation. We are using Meraki network with mash VPNs to cover all company locations across Australia. We also use AWS cloud as a central data storage and as hosting for our customer oriented applications. Data are shared from different (independend) locations and are stored in AWS. The challenge was to connect every physical location to AWS. AWS allows you to use IPSEC tunnel for VPN connection. The problem is that AWS sees MERAKI network as one location no matter how many physical locations are inside of the MERAKI network and therefore they let you to setup only one (two) tunnel to one particular location. After months of trying, fixing and bending existing tools we implementing vMX device as the only solution for our problem. The implementing of the vMX was its own 'journey' due to inconplete and almost non-existing documentation. it is hard to believe that 'Juniper vMX configuration guide for Azure' will help you to setup Meraki vMX in AWS. Meraki vMX is great appliance! I hope that MERAKI will focus on this appliance more in future. Develop more features which are standard on physical MX devices and also document them well to let others to use them.
... View more
Hi helgaali (referring your diagram) how did you setup routes back to MX from VPC-A linked through Transit GW? I can ping client behind the transit GW in VPC-A from vMX but cannot ping this client from MX thanks David
... View more