Cloud CNI privately connects your clouds to Cloudflare

Cloudflare has extended Cloudflare Network Interconnect (CNI) to support direct cloud interconnection, so customers on IBM Cloud, Google Cloud, Azure, Oracle Cloud Infrastructure and Amazon Web Services can open private links from their cloud instances straight into Cloudflare. The move makes Cloudflare the single interconnection point for a corporate network built on Cloudflare One, instead of one more provider to manage alongside cloud links and leased lines.

Public cloud compute is shared by design: VMs from different customers may run on the same hardware, and traffic from different customers can interleave on the same wire, with neither party aware of the other. That abstraction removes the need to run physical machines or buy connectivity, but it offers no guarantees about where data and compute actually live beyond a datacenter shared with millions of other users.

Enterprises often cannot accept that. Compute may hold payment data that must be reachable only over a private connection, compliance rules may forbid public Internet exposure, or the customer may simply want to limit exposure. The answer is a virtual private cloud reachable only by its owner, connected through the clouds' own private interconnect products: AWS DirectConnect, Azure ExpressRoute, Google Cloud Interconnect, OCI FastConnect and IBM Direct Link. These links tie a VPC to the customer's corporate network, giving air-gapped security while the cloud provider handles datacenter operations.

The gap when the corporate network goes away

Private links solved infrastructure migration, but they assume a corporate network to terminate into. Consider a company joining a data center, an office and an Azure instance. Remote users may be tunneled by VPN into the data center or office before reaching applications; office and data center are often joined by leased MPLS lines; and a private IBM instance is connected via IBM Direct Link. That is three connectivity providers to manage, before access policies, cross-building firewalls and MPLS routing on the provider underlay.

BLOG-1573 Embedded Image - lE2va2

Cloudflare One collapses this by becoming the network for every connectivity option, leaving customers to manage only their connections to Cloudflare. WARP handles remote users, Cloudflare Network Interconnect provides private connectivity from data centers and offices, Access policies police applications, and Magic WAN supplies the routing.

BLOG-1573 Embedded Image - fJTZRk

Before cloud support in CNI, customers with private clouds either exposed instances to the public Internet or kept them connected to their data centers, accepting suboptimal routing and extra operational work.

BLOG-1573 Embedded Image - 1xiDqj

With cloud environments supported, the same company can open a private cloud link directly into Cloudflare rather than into its data center. Cloudflare then acts as the intermediary between all resources and takes on firewalls, access policies and routing, reducing the routing vendors to one.

BLOG-1573 Embedded Image - weNPQS

Cross-resource routing and firewalls are managed through Magic WAN, user policies through Access, and egress policies out to the public Internet through Gateway across Cloudflare's 250+ data centers. Offices and clouds communicate over a sealed network with no public access or publicly shared peering links, and the security and privacy work is invisible to users.

Provisioning, the cloud-native way

Cloud connectivity should not involve waiting for cross-connects, obtaining LOAs or monitoring light levels. It should be provisioned from the cloud provider's own portal, following the steps already laid out for direct cloud connection. That is what CNI's cloud support enables: connections from IBM, AWS, Azure, Google Cloud and OCI are requested directly from the provider, and Cloudflare becomes the infrastructure, so cross-connect orders and light-level checks fall away.

In Google Cloud, for example, the request begins by selecting "Private Service Connect" in the VPC network details.

BLOG-1573 Embedded Image - 7kBsEu

The next step is to choose a partner connection rather than a direct one. After selecting a connecting region and datacenter site, Google Cloud issues a connection ID that both Google Cloud and Cloudflare use to identify the private connection to the VPC.

BLOG-1573 Embedded Image - Rs9lrG

Because the partner side must be configured, that key is used to provision a virtual connection on top of an existing link. The provisioning runs through five steps:

  1. Assign unique VLANs to the connection to keep it private.
  2. Assign unique IP addresses for a BGP point-to-point connection.
  3. Provision a BGP connection on the Cloudflare side.
  4. Pass the information back to Google Cloud and create the connection.
  5. Accept the connection and finish BGP provisioning on the VPC.

These steps complete automatically in seconds, so Cloudflare's end is ready by the time the customer receives the IP addresses and VLANs. Once the connection is accepted and configured, traffic can be privately routed through Cloudflare.

Integration with Cloudflare One

Magic WAN and private address space

Magic WAN connects VPCs directly to the private network it builds. Because routing is private, customers can advertise internal address spaces such as the 10.0.0.0/8 range. Previously a cloud VPC had to be publicly addressable; with Cloud CNI, Cloudflare assigns a point-to-point IP range, the customer advertises its internal spaces, and Magic WAN routes traffic to them.

Access without public exposure

Cloudflare Tunnel with Access is already used for secure paths to authentication servers in cloud providers. With Access and Cloud CNI, the authentication service does not need to be publicly accessible at all: Access routes authentication traffic over the private path back to the service, never touching the public Internet.

Gateway for cloud egress

Cloud services sometimes need to reach the public Internet even when they must never be reached from it. Through Cloud CNI they get a private path to Cloudflare, where Gateway applies egress policies, so outbound cloud traffic is monitored in the same place as all other traffic leaving the network.