Skip to content

[CNI] AWS Direct Connect #21873

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Apr 22, 2025
Merged

[CNI] AWS Direct Connect #21873

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
3efb8fa
refined text
marciocloudflare Apr 22, 2025
8099d99
refined text
marciocloudflare Apr 22, 2025
5bb3a11
refined naming
marciocloudflare Apr 22, 2025
72d8b57
Apply suggestions from code review
marciocloudflare Apr 22, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 19 additions & 6 deletions src/content/docs/network-interconnect/cloud-cni.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,23 +6,36 @@ sidebar:

---

Cloud CNI allows you to connect your virtual private cloud (VPC) virtual networks directly with Cloudflare – for a more reliable and secure experience.
Cloud Interconnect allows you to connect your virtual private cloud (VPC) virtual networks directly with Cloudflare – for a more reliable and secure experience.

Connecting to Cloudflare directly with a Cloud CNI reduces latency, makes your network more stable by bypassing Internet performance potential bottlenecks, and will often reduce your cloud provider network egress bandwidth charges.
Connecting to Cloudflare directly with a Cloud Interconnect reduces latency, makes your network more stable by bypassing Internet performance potential bottlenecks, and will often reduce your cloud provider network egress bandwidth charges.

The use case for Cloud CNI is Magic Transit or Magic WAN. If you have publicly routable origins that are behind Magic Transit over a Cloud CNI, then all Cloudflare services that work with public origins will run over the CNI (e.g. Load Balancer, WAF, Cache etc).
The use case for Cloud Interconnect is Magic Transit or Magic WAN. If you have publicly routable origins that are behind Magic Transit over a Cloud Interconnect, then all Cloudflare services that work with public origins will run over the CNI (e.g. Load Balancer, WAF, Cache etc).

## Supported cloud providers

Cloudflare supports interconnect with:

- Amazon Web Services (AWS) DirectConnect
- Amazon Web Services (AWS) Direct Connect
- Google Cloud (GCP) Interconnect
- IBM Cloud Direct Link
- Oracle Cloud Infrastructure (OCI) FastConnect

Azure ExpressRoute support is coming soon.

## Cloud CNI Setup
## Cloud Interconnect Setup

Enterprise customers using Magic WAN or Magic Transit can get started with Cloud CNI by contacting their account team.
Enterprise customers using Magic WAN or Magic Transit can get started with Cloud Interconnect by contacting their account team.

### AWS Direct Connect

If you are a Magic WAN customer, you can connect to [AWS Direct Connect](https://docs.aws.amazon.com/directconnect/) using Cloud Interconnect. Currently, Cloud Interconnect only supports Dedicated Direct Connect, not Hosted Direct Connect. A Dedicated AWS Direct Connect involves a full physical port allocation in AWS, whereas a Hosted AWS Direct Connect uses a VLAN on a shared port between AWS and Cloudflare.

For your AWS Direct Connect, you can choose between connection speeds of 10 Gbps or 1 Gbps.

To connect to AWS Direct Connect:

1. Contact your account team to start the Cloud Interconnect provisioning process. Your team will let you know of available interconnect locations so you can choose the best one for you, as well as all the details involved in this process.
2. Log in to your AWS portal and order a Direct Connect.
3. AWS will provide you a Letter of Agency (LOA) — sometimes referred to as a Letter of Authorization — and a VLAN ID that you need to send to your account team.
4. Your account team will continue the process of provisioning your Cloud Interconnect with the AWS documents you have provided. Overall, this process should take around four weeks to finish.
Loading