Skip to content

Commit 1388bbb

Browse files
marciocloudflaremarciocloudflare
committed
added hubs
1 parent c44dcf3 commit 1388bbb

File tree

1 file changed

+132
-51
lines changed

1 file changed

+132
-51
lines changed

‎src/content/partials/magic-cloud-networking/magic-wan-on-ramps.mdx‎

Lines changed: 132 additions & 51 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,9 @@ params:
55

66
import { Markdown } from "~/components";
77

8-
Magic Cloud Networking (beta) allows you to create on-ramps from your cloud networks to Magic WAN. Cloudflare will create virtual private network (VPN) tunnels between Magic WAN and your virtual private cloud (VPC), configuring both sides of the connection on your behalf. Cloudflare orchestrates the cloud provider's native VPN functionality, without requiring deployment of any additional compute virtual machines (VMs).
8+
Magic Cloud Networking (beta) allows you to create on-ramps from your cloud networks to Magic WAN. Cloudflare will create virtual private network (VPN) tunnels between Magic WAN and your cloud provider, configuring both sides of the connection on your behalf. Cloudflare orchestrates the cloud provider's native VPN functionality, without requiring deployment of any additional compute virtual machines (VMs).
9+
10+
There are two types of on-ramps: single virtual private cloud (VPC) and hubs.
911

1012
## Prerequisites
1113

@@ -19,78 +21,110 @@ Before creating on-ramps from your cloud networks to Magic WAN, make sure you:
1921

2022
Magic Cloud Networking has the following cloud on-ramps integrations:
2123

22-
- AWS
23-
- Azure
24-
- GCP
24+
- AWS (single VPC and hubs)
25+
- Azure (single VPC)
26+
- GCP (single VPC)
2527

2628
Refer to [Reference](/magic-cloud-networking/reference/) to learn more about how Cloudflare orchestrates VPN connectivity to your cloud networks.
2729

2830
---
2931

3032
## Set up on-ramps
3133

32-
### Create a Magic WAN cloud on-ramp
34+
### Single virtual private cloud
35+
36+
Choose this option if you have a single virtual private cloud (VPC) in your cloud to connect to Magic WAN. To set up a single-VPC on-ramp:
3337

3438
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account.
3539
2. Select **Magic WAN** > **Cloud on-ramps**.
3640
3. Select **Add new on-ramp**.
37-
4. Give your new on-ramp a descriptive name.
38-
5. Select the network you want to connect to, and select **Continue**.
39-
6. **Configure on-ramp** shows where Cloudflare will install the new routes. Installing these routes is required to correctly configure both Magic WAN and your cloud provider, and ensure successful communication between them:
40-
- **Add routes for your Magic WAN address space to your cloud network**: Select this option to install routes for reaching Magic WAN in your cloud network's route tables (refer to [Magic WAN Address Space](#magic-wan-address-space) to learn what routes are installed and how to customize them). If you prefer to do this manually, unselect this option.
41-
:::caution
42-
Cloudflare recommends that you leave this option selected. If you unselect **Add routes for your Magic WAN address space to your cloud network**, you will need to manually create all the required configurations to allow Magic WAN to connect to your cloud, like routing tables, transit gateways, and VPNs. Refer to the [Magic WAN How to](/magic-wan/configuration/manually/how-to/) section, or consult the documentation for your cloud provider for more information.
43-
:::
44-
- **Add routes for your cloud network to Magic WAN**: Select this option to create routes for reaching your cloud network in Magic WAN.
45-
7. Select **Continue**. Applying your settings might take a few seconds to complete.
46-
8. Review the changes in your cloud environment, and select **Approve changes**.
41+
4. Go to **Connect an existing VPC to Cloudflare** > **Select**.
42+
5. Give your new on-ramp a name and, optionally, a description, and select **Continue**.
43+
6. From the drop-down menu, choose your cloud type. You can choose between AWS, GCP and Azure. Then, select **Continue**.
44+
7. Select the network that you want to connect to. This list comes from the [cloud integrations](/magic-cloud-networking/get-started/#2-set-up-cloud-integrations) you have already set up. When you are done, select **Continue**.
45+
8. **Configure route propagation** shows where Cloudflare will install the new routes. Installing these routes is required to correctly configure both Magic WAN and your cloud provider, and ensure successful communication between them:
46+
- **Add routes for your Magic WAN address space to your cloud network**: Select this option to install routes for reaching Magic WAN in your cloud network's route tables (refer to [Magic WAN Address Space](#magic-wan-address-space) to learn what routes are installed and how to customize them). If you prefer to do this manually, unselect this option.
47+
:::caution[Warning]
48+
Cloudflare recommends that you leave this option selected. If you unselect **Add routes for your Magic WAN address space to your cloud network**, you will need to manually create all the required configurations to allow Magic WAN to connect to your cloud, like routing tables, transit gateways, and VPNs. Refer to the [Magic WAN How to](/magic-wan/configuration/manually/how-to/) section, or consult the documentation for your cloud provider for more information.
49+
:::
50+
- **Add routes for your cloud network to Magic WAN**: Select this option to create routes for reaching your cloud network in Magic WAN.
51+
9. Select **Continue**. Applying your settings might take a few seconds to complete.
52+
10. Review the changes in your cloud environment, and select **Approve changes**.
4753

4854
You have successfully created your Magic WAN on-ramp. However, on-ramp creation can take up to an hour before you can use it.
4955

50-
### Edit a Magic WAN cloud on-ramp
56+
### Hubs
5157

52-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account.
53-
2. Select **Magic WAN** > **Cloud on-ramps**.
54-
3. Select the on-ramp you want to edit.
55-
4. Select **Edit** in the side panel.
56-
5. In **Basic information**, you can change the name and description of your on-ramp. Select **Save** when you are finished.
57-
6. In **Configurations**, you can modify where the required routes are installed. Select **Continue**.
58-
1. Select **Save and review** after making changes.
59-
2. Review your settings, and select **Approve changes**.
60-
:::caution
61-
If you uncheck any of the Propagation settings, you will have to manually configure Magic WAN or your cloud provider to ensure successful communication between them. Refer to the [How to](/magic-wan/configuration/manually/how-to/) section of Magic WAN, or consult the documentation for your cloud provider for more information.
62-
:::
58+
If you want to connect multiple VPCs to Magic WAN, the best way to connect them is using a hub. A hub is a cloud VPN gateway that peers with multiple VPCs, allowing them to share a VPN tunnel to Magic WAN. Each cloud provider has their own term for hubs, so refer to your cloud provider for more information.
6359

64-
### Delete a Magic WAN cloud on-ramp
60+
Depending on how you have set up your cloud provider you can:
6561

66-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account.
67-
2. Select **Magic WAN** > **Cloud on-ramps**.
68-
3. Select the on-ramp you want to delete.
69-
4. Select **Edit** in the side panel.
70-
5. Choose **Detach** or **Destroy** to proceed:
71-
- **Detach**: Cloudflare will stop managing the cloud resources that were created to build this on-ramp, but will leave them in place. On-ramp connectivity will not be impacted.
72-
- **Destroy**: Cloudflare will delete the resources that were created to build this on-ramp in the cloud provider, if possible. Resources cannot be deleted if other resources depend upon them. For example, if an AWS Customer Gateway was created for this on-ramp, but was subsequently used in a second on-ramp, destroying this on-ramp will not destroy the AWS Customer Gateway.
62+
- **Connect to an existing hub**: Choose this option if you already have a VPN hub in your cloud and you want to connect it to Magic WAN.
63+
- **Create a new hub**: Choose this option if you want to create a new hub and connect it to Magic WAN.
7364

74-
### Magic WAN Address Space
65+
When you configure a hub on-ramp, Cloudflare always manages the VPN tunnel between Magic WAN and the hub. Optionally, you can also choose to have Cloudflare manage peering with VPCs and/or with other hubs:
7566

76-
By default, Cloudflare installs the following summarized routes in your cloud route tables to direct traffic to Magic WAN:
67+
- **Manage VPC peering:** If you enable this option, Cloudflare will attach VPCs you choose to the hub.
68+
- **Manage hub peering:** Hubs are regional, so in order to connect VPCs attached to hubs in different regions, those hubs need to be peered. If you enable this option, Cloudflare will peer hubs you choose to this hub.
7769

78-
```txt
79-
10.0.0.0/8
80-
172.16.0.0./12
81-
192.168.0.0/16
82-
100.64.0.0./10
83-
```
70+
#### Connect to an existing hub
8471

85-
To override the defaults with custom prefixes:
72+
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account.
73+
2. Select **Magic WAN** > **Cloud on-ramps**.
74+
3. Select **Add new on-ramp**.
75+
4. Go to **Connect an existing hub to Cloudflare** > **Select**.
76+
5. Give your new on-ramp a name and, optionally, a description, and select **Continue**.
77+
6. From the drop-down menu, choose your cloud type. You can choose between AWS, GCP and Azure. Then, select **Continue**.
78+
7. Choose an existing hub. This list comes from the [cloud integrations](/magic-cloud-networking/get-started/#2-set-up-cloud-integrations) you have already set up. When you are done, select **Continue**.
79+
8. (*Optional*) In **VPC peering configuration**, you can enable **Manage VPC peering**. This allows Cloudflare to attach VPCs you choose to the hub:
80+
1. Select **Manage VPC peering** to enable this feature.
81+
2. Choose the VPCs you want Cloudflare to attach to the hub.
82+
9. Select **Continue**.
83+
10. (*Optional*) In **Configure hub peering**, you can enable **Manage hub peering**. Enabling this option allows Cloudflare to attach remote hubs you choose to this hub (establishing connectivity between VPCs attached to any of the peered hubs):
84+
1. Select **Manage hub peering** to enable this feature.
85+
2. Select the remote hubs you want Cloudflare to attach to this hub.
86+
11. Select **Continue**.
87+
12. **Configure route propagation** shows where Cloudflare will install the new routes. Installing these routes is required to correctly configure both Magic WAN and your cloud provider, and ensure successful communication between them:
88+
1. **Add routes for your Magic WAN address space to your cloud network**: Select this option to install routes for reaching Magic WAN in your cloud network's route tables (refer to [Magic WAN Address Space](#magic-wan-address-space) to learn what routes are installed and how to customize them). If you prefer to do this manually, unselect this option.
89+
:::caution[Warning]
90+
Cloudflare recommends that you leave this option selected. If you unselect **Add routes for your Magic WAN address space to your cloud network**, you will need to manually create all the required configurations to allow Magic WAN to connect to your cloud, like routing tables, transit gateways, and VPNs. Refer to the [Magic WAN How to](/magic-wan/configuration/manually/how-to/) section, or consult the documentation for your cloud provider for more information.
91+
:::
92+
2. **Add routes for your cloud network to Magic WAN**: Select this option to create routes for reaching your cloud network in Magic WAN.
93+
13. Select **Continue**. Applying your settings might take a few seconds to complete.
94+
14. Review the changes in your cloud environment, and select **Approve changes**.
8695

87-
1. Log in to the Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account.
88-
2. Select **Magic WAN** > **Configuration**.
89-
3. Select **Magic WAN Address Space**.
90-
4. Delete the prefixes, and enter your custom ones.
91-
5. When you are finished, select **Save changes**.
96+
You have successfully created your Magic WAN on-ramp. However, on-ramp creation can take up to an hour before you can use it.
9297

93-
To install a default route to send all traffic to Magic WAN, enter `0.0.0.0/0` (on Azure, enter `0.0.0.0/1` and `128.0.0.0/1`).
98+
#### Create a new hub
99+
100+
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account.
101+
2. Select **Magic WAN** > **Cloud on-ramps**.
102+
3. Select **Add new on-ramp**.
103+
4. Go to **Create a new hub & connect it to Cloudflare** > **Select**.
104+
5. Give your new on-ramp a name and, optionally, a description, and select **Continue**.
105+
6. Configure your cloud in **Select your cloud details**:
106+
1. From the drop-down menu, choose your cloud type. You can choose between AWS, GCP and Azure.
107+
2. Choose an existing integration. This list comes from the [cloud integrations](/magic-cloud-networking/get-started/#2-set-up-cloud-integrations) you have already set up.
108+
3. Choose a region in which to create the new hub.
109+
4. Select **Continue**.
110+
7. (*Optional*) In **VPC peering configuration**, you can enable **Manage VPC peering**. This allows Cloudflare to attach VPCs you choose to the hub:
111+
1. Select **Manage VPC peering** to enable this feature.
112+
2. Choose the VPCs you want Cloudflare to attach to the hub.
113+
8. Select **Continue**.
114+
9. (*Optional*) In **Configure hub peering**, you can enable **Manage hub peering**. Enabling this option allows Cloudflare to attach remote hubs you choose to this hub (establishing connectivity between VPCs attached to any of the peered hubs):
115+
1. Select **Manage hub peering** to enable this feature.
116+
2. Select the remote hubs you want Cloudflare to attach to this hub.
117+
10. Select **Continue**.
118+
11. **Configure route propagation** shows where Cloudflare will install the new routes. Installing these routes is required to correctly configure both Magic WAN and your cloud provider, and ensure successful communication between them:
119+
1. **Add routes for your Magic WAN address space to your cloud network**: Select this option to install routes for reaching Magic WAN in your cloud network’s route tables (refer to [Magic WAN Address Space](#magic-wan-address-space) to learn what routes are installed and how to customize them). If you prefer to do this manually, unselect this option.
120+
:::caution[Warning]
121+
Cloudflare recommends that you leave this option selected. If you unselect **Add routes for your Magic WAN address space to your cloud network**, you will need to manually create all the required configurations to allow Magic WAN to connect to your cloud, like routing tables, transit gateways, and VPNs. Refer to the [Magic WAN How to](/magic-wan/configuration/manually/how-to/) section, or consult the documentation for your cloud provider for more information.
122+
:::
123+
2. **Add routes for your cloud network to Magic WAN**: Select this option to create routes for reaching your cloud network in Magic WAN.
124+
12. Select **Continue**. Applying your settings might take a few seconds to complete.
125+
13. Review the changes in your cloud environment, and select **Approve changes**.
126+
127+
You have successfully created your Magic WAN on-ramp. However, on-ramp creation can take up to an hour before you can use it.
94128

95129
## Set up with Terraform
96130

@@ -126,6 +160,53 @@ Do not deploy the on-ramp using both Cloudflare and Terraform. If you plan to de
126160
2. Select **Magic WAN** > **Cloud on-ramps**.
127161
3. Select the three dots for the on-ramp you want to download > **Download Terraform**.
128162

163+
## Edit on-ramps
164+
165+
### Edit a Magic WAN cloud on-ramp
166+
167+
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account.
168+
2. Select **Magic WAN** > **Cloud on-ramps**.
169+
3. Select the on-ramp you want to edit.
170+
4. Select **Edit** in the side panel.
171+
5. In **Basic information**, you can change the name and description of your on-ramp. Select **Save** when you are finished.
172+
6. In **Configurations**, you can modify where the required routes are installed. Select **Continue**.
173+
1. Select **Save and review** after making changes.
174+
2. Review your settings, and select **Approve changes**.
175+
:::caution
176+
If you uncheck any of the Propagation settings, you will have to manually configure Magic WAN or your cloud provider to ensure successful communication between them. Refer to the [How to](/magic-wan/configuration/manually/how-to/) section of Magic WAN, or consult the documentation for your cloud provider for more information.
177+
:::
178+
179+
### Delete a Magic WAN cloud on-ramp
180+
181+
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account.
182+
2. Select **Magic WAN** > **Cloud on-ramps**.
183+
3. Select the on-ramp you want to delete.
184+
4. Select **Edit** in the side panel.
185+
5. Choose **Detach** or **Destroy** to proceed:
186+
- **Detach**: Cloudflare will stop managing the cloud resources that were created to build this on-ramp, but will leave them in place. On-ramp connectivity will not be impacted.
187+
- **Destroy**: Cloudflare will delete the resources that were created to build this on-ramp in the cloud provider, if possible. Resources cannot be deleted if other resources depend upon them. For example, if an AWS Customer Gateway was created for this on-ramp, but was subsequently used in a second on-ramp, destroying this on-ramp will not destroy the AWS Customer Gateway.
188+
189+
## Magic WAN Address Space
190+
191+
By default, Cloudflare installs the following summarized routes in your cloud route tables to direct traffic to Magic WAN:
192+
193+
```txt
194+
10.0.0.0/8
195+
172.16.0.0./12
196+
192.168.0.0/16
197+
100.64.0.0./10
198+
```
199+
200+
To override the defaults with custom prefixes:
201+
202+
1. Log in to the Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account.
203+
2. Select **Magic WAN** > **Configuration**.
204+
3. Select **Magic WAN Address Space**.
205+
4. Delete the prefixes, and enter your custom ones.
206+
5. When you are finished, select **Save changes**.
207+
208+
To install a default route to send all traffic to Magic WAN, enter `0.0.0.0/0` (on Azure, enter `0.0.0.0/1` and `128.0.0.0/1`).
209+
129210
## Cost estimates
130211

131212
You can view estimated costs associated with your cloud resources in the Cloudflare dashboard.
@@ -134,4 +215,4 @@ You can view estimated costs associated with your cloud resources in the Cloudfl
134215
2. Select **Magic WAN** > **Cloud on-ramps**.
135216
3. Find the cloud on-ramp for which you want to check the estimated costs.
136217
4. Select the three dots > **Associated Resources**.
137-
5. In the **Associated Resources** page, you can view the estimated monthly costs for all the resources associated with the on-ramp you chose. You can also search for a specific resource using the search box.
218+
5. In the **Associated Resources** page, you can view the estimated monthly costs for all the resources associated with the on-ramp you chose. You can also search for a specific resource using the search box.

0 commit comments

Comments
 (0)