Skip to content

Commit 3efb8fa

Browse files
refined text
1 parent 68cdaf5 commit 3efb8fa

File tree

1 file changed

+13
-0
lines changed

1 file changed

+13
-0
lines changed

src/content/docs/network-interconnect/cloud-cni.mdx

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -26,3 +26,16 @@ Azure ExpressRoute support is coming soon.
2626
## Cloud CNI Setup
2727

2828
Enterprise customers using Magic WAN or Magic Transit can get started with Cloud CNI by contacting their account team.
29+
30+
### AWS DirectConnect
31+
32+
If you are a Magic WAN customer you can use Cloud Interconnect to connect to AWS DirectConnect. Currently, Cloud Interconnect only supports Dedicated DirectConnect, not Hosted DirectConnect. A Dedicated AWS DirectConnect involves a full physical port allocation in AWS, whereas a Hosted AWS DirectConnect uses a VLAN on a shared port between AWS and Cloudflare.
33+
34+
For your AWS DirectConnect, you can choose between connection speeds of 10 Gbps or 1 Gbps.
35+
36+
To connect to AWS DirectConnect:
37+
38+
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.
39+
2. Log in to your AWS portal and order a DirectConnect.
40+
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.
41+
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 for the process to finish.

0 commit comments

Comments
 (0)