Migrating vMX from one account to another on AWS

[merakiuser3265]

Hello Everyone,

We need assistance on the following : We have a pair of vMX configured in passthrough mode on AWS (AZ1 & AZ2). We are planning to move vMX from current account/vpc to another account. I have questions on following

1. Moving vMX from 1 account to another possible on AWS?
2. There will be change of IPs (private/public) after migration to new account , will that cause disruption - like vpn connection going down and anything else?
3. Any other changes needed on vMX?
4. Any other changes needed on AWS side?

A quick reply is highly appreciated.

[PhilipDAth]

To move the VMX between AWS accounts you'll need to first delete it, and deploy then it get into the new account.

The public IPs will definately change.  The new AWS account wont have access to the IPs in the old account.  If the VPC is using the exact same private IP address then you could specify to use the same private IP address - but more than likely - it wont be the same.

There will be considerable disruption during the change.

[merakiuser3265]

Hi @PhilipDAth Thanks for you reply.

Meanwhile i got reply from Meraki support that we just need to move vMX to another account and then need to reauthenticate vMX from their. But as we know Meraki support is totally unreliable.

So, I am planning to still follow Meraki suggestion and if it doesnt work then deleting the network (we are planning on standby Meraki first) as it must free the license as well and then building secondary from scratch  in new vMX. On basis of this, planning of primary vMX migration by failing over prod traffic to secondary vMX.

Let me know your view on this.

[TyShawn]

In this case they are correct. The device is tied to the key the Meraki portal vs the account that the VM I assigned to.