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
Copy file name to clipboardExpand all lines: src/content/docs/workers-vpc/configuration/tunnel/index.mdx
+16-53Lines changed: 16 additions & 53 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,71 +17,34 @@ The tunnel maintains persistent connections to Cloudflare, eliminating the need
17
17
This section provides tunnel configuration specific to Workers VPC use cases. For comprehensive tunnel documentation including monitoring and advanced configurations, refer to the [full Cloudflare Tunnel documentation](/cloudflare-one/connections/connect-networks/).
18
18
:::
19
19
20
-
## Quick setup
20
+
## Create and run tunnel (`cloudflared`)
21
21
22
-
### Install cloudflared
22
+
Cloudflare Tunnel requires the installation of a lightweight and highly scalable server-side daemon, `cloudflared`, to connect your infrastructure to Cloudflare.
23
23
24
-
<Tabs>
25
-
<TabItemlabel="Linux">
24
+
Cloudflare Tunnels can be created one of two ways:
1.**Remotely-managed tunnels (recommended):** Remotely-managed configurations are stored on Cloudflare, allowing you to manage the tunnel from any machine using the dashboard, API, or Terraform.
27
+
2.**Locally-managed tunnels:** A locally-managed tunnel is created by running `cloudflared tunnel create <NAME>` on the command line. Tunnel configuration is stored in your local cloudflared directory.
32
28
33
-
</TabItem>
34
-
<TabItemlabel="macOS">
29
+
For Workers VPC, we recommend creating a remotely-managed tunnel through the dashboard. Follow the [Tunnels for Workers VPC dashboard setup guide](/workers-vpc/get-started/) to create your tunnel with provided installation commands shown in the dashboard.
35
30
36
-
```sh
37
-
brew install cloudflared
38
-
```
31
+
For locally-managed tunnels, refer to the [`cloudflared` locally-managed tunnels](/cloudflare-one/connections/connect-networks/do-more-with-tunnels/local-management/) guide.
32
+
For manual installation, refer to the [`cloudflared` downloads page](/cloudflare-one/connections/connect-networks/downloads/) for platform-specific installation instructions.
39
33
40
-
</TabItem>
41
-
<TabItemlabel="Windows">
34
+
:::note[Important Note]
35
+
Cloudflare Tunnels can either be configured for usage with [Cloudflare Zero Trust](/cloudflare-one/) or [Workers VPC](/workers-vpc/).
42
36
43
-
```powershell
44
-
choco install cloudflared
45
-
```
37
+
Use Tunnels with Zero Trust when you are exposing internal applications securely to your employees with Cloudflare Access and hostnames.
46
38
47
-
</TabItem>
48
-
<TabItemlabel="Docker">
39
+
Use Tunnels with Workers VPC when you want to access private APIs, private databases, internal services or other HTTP services within your cloud or on-premise private network from Workers.
49
40
50
-
```sh
51
-
docker pull cloudflare/cloudflared:latest
52
-
```
53
-
54
-
</TabItem>
55
-
</Tabs>
56
-
57
-
### Create and run tunnel
58
-
59
-
Authenticate with Cloudflare, create your tunnel, and run it with a basic configuration that routes all traffic to your local services:
60
-
61
-
```sh
62
-
cloudflared tunnel login
63
-
cloudflared tunnel create workers-vpc-tunnel
64
-
```
65
-
66
-
Create `~/.cloudflared/config.yml` with your tunnel configuration:
[Ingress configurations](/cloudflare-one/connections/connect-networks/do-more-with-tunnels/local-management/configuration-file/) for locally-managed tunnels are specific to Zero Trust are not required for Workers VPC as routing is handled by the VPC Service configuration.
0 commit comments