I know about VMWware on AWS solution and NSX-T you mentioned. Some of our customers are using VMC on AWS with Aviatrix today just to support their legacy, proprietary and old apps that cannot run in Cloud today. They know that VMC on AWS is a temporary or stop-gap solution for them.
In my opinion, running workloads on VMC on AWS is not the right approach. Like I said, our customers who are using VMC on AWS, are doing so just so that they can buy some time to port their legacy Apps/VM into Cloud Apps/VMs. We should have a detailed discussion on this topic. I will setup zoom with you.
Thanks for the reply.
As VMC has some challenges in terms of the full access to the environment and mostly driven by SRE team in VMware itself.
I was going through if the arch support the direct interaction between AVI Controller-GTW to NSX-T Edge ( CGW and MGW). I would be happy to have session but this I was checking from product support wise.
Yes, MCNA Arch. does support the direct interaction. The VMC is treated like another external site in the Cloud. So basically Aviatrix Controller can establish IPSec BGP connection back to NSX-T Edge. This is how it will look like
AVX-Ctrl -->AVX-Transit-GW ------IPSec/BGP Tunnel ----> NSX-T Edge
Unfortunately this tunnel is going to be limited in terms of performance because VMC is locked down architecture. As you mentioned, VMC team manages and control the VPCs. They wont allow other gateways to be installed in the VPC. Otherwise a better arch would be to deploy AVX Spoke GW inside the VPC to get full benefit of MCNA (Traffic Engineering / 70Gbps performance / etc.)
AVX-Ctrl -->AVX-Transit-GW ---|---> AVX-SPK-GW----->NSX-T Edge