Today Flow virtual networking is not supported on AWS

This is really unfortunate. I appreciate your timely reply.

Thanks,

Scott 

PM has view on this issue. Most of the current networking effort has been focused on Azure.

Sorry maybe I was not clear in my original post. We have 2 AHV clusters in 2 different data centers we own. So it is not shipping to a cloud resource, rather between my 2 clusters.

You posted in the NC2 fourm. You would have to strentch the network between both clusters on-prem 

My bad. Thanks for pointing that out. I can stretch the network via VXLan; however, it is unclear if I can share the managed network database of IP’s between the networks. So for example if I create a VM on Site A with a managed network and move it to Site B it should be fine as long as I have stretched the network. From what I understand of managed networks this VM will no longer be in the database so this IP will get handed out again. At this point I would have an IP conflict. I can move this to the correct forum as well if needed.

i am not expert but I believe you need to have 2 non overlapping dhcp pools, one on each cluster and it should work