hi @TimHughSmith    We have a customer where we deployed two vMX100 on two different AZ. One of the vMX100 is shutdown, the other one is up and running and basically, CloudWatch executes a lambda script every one minute to monitor the estate of the vMX100 instances and to figure out if it needs to switch over because one of them failed for example. The customer is running this for like a year now and it is working OK.   The only thing that I would mention is that the switchover time is not that fast, because first, the secondary EC2 instance has to change its state to up, and second, the vMX100 takes some time to register to Meraki Cloud to establish the VPN connections and learn the routes. I think it takes like 1 or 2 minutes, but I don't remember the exact amount of time, so take this into account.   I hope this can help you.           ... View more

I've found these AWS papers about VPN monitor and seems like a viable solution to deploy vMX100 in HA on AWS:   https://docs.aws.amazon.com/solutions/latest/vpn-monitor/overview.html   https://docs.aws.amazon.com/aws-technical-content/latest/aws-vpc-connectivity-options/appendix-high-level-ha-architecture-for-software-vpn-instances.html   I have a customer that wants to deploy vMX100 appliances in HA on AWS but basically they want to have redundancy un case of a failure in a AZ that causes the termination of the instance.   Based on that this is what I'm thinking ... use the CloudWatch service to monitor the VMX100 EC2 instance and create a rule so that in the case of shutdown or termination of the primary vMX100 instance to trigger a function in Lambda to update the VPC: AWS route table to a secondary vMX100 in a different AZ.   What do you guys think, maybe too complicated ?                   ... View more