We have recently heard from many customers that the Transit VPC architecture is hard to manage and troubleshoot. On one hand, there is the management of the third-party software at the hub and Amazon’s VGW from every spoke. On the other hand, there is the troubleshooting of multiple software, vendors, routing tables and lack of visibility overall. And on top of that, as cloud adoption increases, customer are now dealing with tens or hundreds of tunnels between all their VPCs, manual and complex solutions are not the right approach. This blog only discusses the hub and spoke architecture, the full mesh architecture…
IT organizations have consistently overlooked one risk category that has haunted their cloud projects and agility aspirations: Operational connectivity to your cloud provider. An analyst put it this way: “Cloud providers built a beautiful highway, but left the on-ramps for the drivers to figure out.”
Amid all the excitement around Cloud-powered scalability, Network Engineers are still responsible for operating this organically growing animal that started off as a small pet (project).
Have you noticed that while cloud is all about infrastructure agility, the networking to the cloud is static and not agile at all. This means while it takes minutes to provision compute and storage in a VPC (virtual private cloud), it can take months to network to the same VPC. This is an impedance mismatch and often leads to performance issue, architectural challenges, slowdown in cloud projects and overall poor experience for hybrid cloud networking.