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.
In the datacenter, a VLAN can cross physical switches and form a logical L2 domain. Machines, VMs or hosts on this VLAN can communicate with each other irrespective of its physical location with private IP addresses. All is secure.
The question is: Can you stretch this VLAN to AWS or Azure?