Moving Past the “Denial Phase” of Cloud Networking Problems

karthik
By Karthik Balachandran
Cloud System Engineer, Aviatrix
June 6, 2017

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). I have heard hours of grievances from networking professionals about Public Cloud implementations. The most common ones are:

  • Having to operate in a networking model built by an elite group of software engineers.
  • Lack of a networking console/CLI/UI for all-things cloud (across providers and regions).
  • Poor visibility for troubleshooting (like packet captures or advanced logging).

Does our industry acknowledge that we have a case of “lopsided Cloud agility” where networking is left far behind App development, Compute and Storage? There is a long list of capabilities that will help make Connectivity to the Public Clouds more reliable and consumable for enterprises. Numerous blogs document the unofficial wish-list of IT professionals. Here a few recurring questions:

  • How to design networks where the center of gravity is shifting to the public cloud? (CIDR allocations, multi Availability Zone implementations, cross-region strategy etc.)
  • How to handle overlapping IP addresses during migration to the cloud? (Application owners want to preserve IP addresses into the cloud)
  • How do we manage and monitor this framework with agility that the business demands?

I was pleasantly surprised last week when a series of incidents and announcements started addressing this issue:

Are we finally moving past the denial phase of the problem? Is this the beginning-of-the-end of lopsided agility? Comment below with your thoughts. Let’s share our collective learning and build connectivity and networking models that don’t get in the way of business goals.


Comments

Comments are closed for this post.

Latest Posts


Understanding AWS VPC Egress Filtering Methods
By Khash Nakhostin, November 14, 2018

Implementing a Secure Transit DMZ Architecture with Next-Gen Firewalls
By Josh Hammer, October 16, 2018

Talking Innovation, Disruption and Software Defined Cloud Routing with Steve Mullaney
By Frank Cabri, September 28, 2018

Why the Economics of Adding a Network Engineer to the Cloud Engineering Team Doesn’t Add Up
By Neel Kamal, September 18, 2018

Navigating the New Networking Landscape In the Era of Public Cloud Computing
By Frank Cabri, September 7, 2018


Top Tags


Active Directory (AD)Amazon Partner Network (APN)Amazon Virtual Private Cloud (Amazon VPC)Amazon Web Services (AWS)Amazon WorkSpacesApplication VisibilityAviatrix Cloud InterconnectAviatrix ControllerAviatrix FlightPathAviatrix Hosted ServiceAWS Direct ConnectAWS Egress ControlAWS VPNAzure ExpressRouteCasachekChefCiscoCisco Live 2018Cloud Architectscloud burstingCloud ComputingCloud GatewayCloud MigrationCloud NetworkingCloudOpsCSRDevOpsEgress TrafficElon MuskEnterprise Strategy Group (ESG)GartnerGCP Next 16Google Cloud PlatformHub-and-Spoke NetworkHybrid CloudHyperFlex Multi-Cloud EcosystemInternational Data Corporation (IDC)Intrusion Detection System (IDS)Intrusion Preventions Systems (IPS)IPmotionJenkinsMalware DetectionMesh NetworkMicrosoft AzureMulticloudNetworking as a Servicenetworking infrastructureNiciraNoOpsNutanixNutanix CalmOpenVPN Access ServerPalo Alto NetworksPCI CompliancePci DssPublic CloudPublic Cloud NetworkingPuppetRemote AccessSD Cloud RouterSD-WANSoftware Defined Cloud RoutingSoftware-Defined Cloud RoutersSquidSSL VPN to AWSstorage and computeTransit DMZ Architecturetransit networkTransit VPCURL FilteringVirtual Cloud NetworkVirtual Desktop Infrastructure (VDI)Virtual RoutersVLANVMwareVPCVPC PeeringVPN