You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* new hubs options
* Apply suggestions from code review
Co-authored-by: Jun Lee <[email protected]>
* refined terraform message
---------
Co-authored-by: Jun Lee <[email protected]>
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.
9
11
10
12
## Prerequisites
11
13
@@ -19,34 +21,147 @@ Before creating on-ramps from your cloud networks to Magic WAN, make sure you:
19
21
20
22
Magic Cloud Networking has the following cloud on-ramps integrations:
21
23
22
-
- AWS
23
-
- Azure
24
-
- GCP
24
+
- AWS (single VPC and hubs)
25
+
- Azure (single VPC)
26
+
- GCP (single VPC)
25
27
26
28
Refer to [Reference](/magic-cloud-networking/reference/) to learn more about how Cloudflare orchestrates VPN connectivity to your cloud networks.
27
29
28
30
---
29
31
30
32
## Set up on-ramps
31
33
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:
37
+
38
+
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account.
39
+
2. Select **Magic WAN** > **Cloud on-ramps**.
40
+
3. Select **Add new on-ramp**.
41
+
4. Go to **Connect an existing VPC to Cloudflare** > **Select**.
42
+
5. Give your new on-ramp a name and a description (optional), then select **Continue**.
43
+
6. From the drop-down menu, choose your cloud provider. 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, such as 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**.
53
+
54
+
You have successfully created your Magic WAN on-ramp. However, on-ramp creation can take up to an hour before you can use it.
55
+
56
+
### Hubs
57
+
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.
59
+
60
+
Depending on how you have set up your cloud provider, you can:
61
+
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.
64
+
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:
66
+
67
+
-**Manage VPC peering:** If you enable this option, Cloudflare will attach your chosen VPCs 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 your chosen hubs to this hub.
69
+
70
+
#### Connect to an existing hub
71
+
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 a description (optional), then select **Continue**.
77
+
6. From the drop-down menu, choose your cloud provider. 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 your chosen VPCs 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 have chosen 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, such as 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**.
95
+
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.
97
+
98
+
#### Create a new hub
33
99
34
100
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account.
35
101
2. Select **Magic WAN** > **Cloud on-ramps**.
36
102
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**.
103
+
4. Go to **Create a new hub & connect it to Cloudflare** > **Select**.
104
+
5. Give your new on-ramp a name and a description (optional), then select **Continue**.
105
+
6. Configure your cloud in **Select your cloud details**:
106
+
1. From the drop-down menu, choose your cloud provider. 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 your chosen VPCs 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 have chosen 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, such as 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**.
47
126
48
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.
49
128
129
+
## Set up with Terraform
130
+
131
+
You can download a Terraform configuration for a cloud on-ramp. You might want to do this to:
132
+
133
+
- Review the proposed configuration for an on-ramp before deploying it with Cloudflare.
134
+
- Deploy the on-ramp using your own infrastructure-as-code pipeline instead of deploying it with Cloudflare.
135
+
136
+
The download will contain two files:
137
+
138
+
-`main.tf`: Terraform configuration for the new resources needed to create the on-ramp.
139
+
-`instructions.txt`: Instructions for modifying resources that already exist in your cloud environment.
140
+
141
+
If you intend to plan and apply the downloaded configuration using Terraform, you will need to use the [Cloudflare Terraform provider](/terraform/) (in addition to the Terraform provider for the on-ramp's cloud service provider). Use your Cloudflare [Global API Key](/fundamentals/api/get-started/keys/), not an API Token.
142
+
143
+
:::caution
144
+
Do not deploy the on-ramp using both Cloudflare and Terraform. If you plan to deploy your on-ramp with Cloudflare (meaning you are both planning to create an on-ramp and applying an on-ramp), Cloudflare creates resources that will result in conflicts when you run Terraform (and vice versa). The Cloudflare dashboard will warn you if it detects you might encounter a conflict.
145
+
:::
146
+
147
+
### Download Terraform configuration for a new on-ramp
148
+
149
+
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account.
150
+
2. Select **Magic WAN** > **Cloud on-ramps**.
151
+
3. Select **Add new on-ramp** and begin the **Create a Magic WAN cloud on-ramp** workflow as normal.
152
+
4. After the **Configure route propagation** step, select **View download options** instead of selecting **Continue**.
153
+
5. Select a download option:
154
+
1. Choose **Download file and continue** to download the Terraform configuration, review the configuration, and then continue deploying the on-ramp with Cloudflare.
155
+
2. Choose **Download file and exit** to download the Terraform configuration that you will apply yourself.
156
+
157
+
### Download Terraform configuration for an existing on-ramp
158
+
159
+
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account.
160
+
2. Select **Magic WAN** > **Cloud on-ramps**.
161
+
3. Select the three dots for the on-ramp you want to download > **Download as Terraform**.
162
+
163
+
## Edit on-ramps
164
+
50
165
### Edit a Magic WAN cloud on-ramp
51
166
52
167
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account.
@@ -71,7 +186,7 @@ You have successfully created your Magic WAN on-ramp. However, on-ramp creation
71
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.
72
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.
73
188
74
-
###Magic WAN Address Space
189
+
## Magic WAN Address Space
75
190
76
191
By default, Cloudflare installs the following summarized routes in your cloud route tables to direct traffic to Magic WAN:
77
192
@@ -92,40 +207,6 @@ To override the defaults with custom prefixes:
92
207
93
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`).
94
209
95
-
## Set up with Terraform
96
-
97
-
You can download a Terraform configuration for a cloud on-ramp. You might want to do this to:
98
-
99
-
- Review the proposed configuration for an on-ramp before deploying it with Cloudflare.
100
-
- Deploy the on-ramp using your own infrastructure-as-code pipeline instead of deploying it with Cloudflare.
101
-
102
-
The download will contain two files:
103
-
104
-
-`main.tf`: Terraform configuration for the new resources needed to create the on-ramp.
105
-
-`instructions.txt`: Instructions for modifying resources that already exist in your cloud environment.
106
-
107
-
If you intend to plan and apply the downloaded configuration using Terraform, you will need to use the [Cloudflare Terraform provider](/terraform/) (in addition to the Terraform provider for the on-ramp's cloud service provider). Use your Cloudflare [Global API Key](/fundamentals/api/get-started/keys/), not an API Token.
108
-
109
-
:::caution
110
-
Do not deploy the on-ramp using both Cloudflare and Terraform. If you plan to deploy your on-ramp with Cloudflare (meaning you are both planning to create an on-ramp and applying an on-ramp), Cloudflare creates resources that will result in conflicts when you run Terraform (and vice versa). The Cloudflare dashboard will warn you if it detects you might encounter a conflict.
111
-
:::
112
-
113
-
### Download Terraform configuration for a new on-ramp
114
-
115
-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account.
116
-
2. Select **Magic WAN** > **Cloud on-ramps**.
117
-
3. Select **Add new on-ramp** and begin the **Create a Magic WAN cloud on-ramp** workflow as normal.
118
-
4. After the **Configure route propagation** step, select **View download options** instead of selecting **Continue**.
119
-
5. Select a download option:
120
-
1. Choose **Download and continue** to download the Terraform configuration, review the configuration, and then continue deploying the on-ramp with Cloudflare.
121
-
2. Choose **Download and exit** to download the Terraform configuration that you will apply yourself.
122
-
123
-
### Download Terraform configuration for an existing on-ramp
124
-
125
-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account.
126
-
2. Select **Magic WAN** > **Cloud on-ramps**.
127
-
3. Select the three dots for the on-ramp you want to download > **Download as Terraform**.
128
-
129
210
## Cost estimates
130
211
131
212
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
134
215
2. Select **Magic WAN** > **Cloud on-ramps**.
135
216
3. Find the cloud on-ramp for which you want to check the estimated costs.
136
217
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