Skip to content

Commit 5ef9679

Browse files
committed
more cloudflared edits
1 parent f8139af commit 5ef9679

File tree

1 file changed

+16
-53
lines changed
  • src/content/docs/workers-vpc/configuration/tunnel

1 file changed

+16
-53
lines changed

src/content/docs/workers-vpc/configuration/tunnel/index.mdx

Lines changed: 16 additions & 53 deletions
Original file line numberDiff line numberDiff line change
@@ -17,71 +17,34 @@ The tunnel maintains persistent connections to Cloudflare, eliminating the need
1717
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/).
1818
:::
1919

20-
## Quick setup
20+
## Create and run tunnel (`cloudflared`)
2121

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.
2323

24-
<Tabs>
25-
<TabItem label="Linux">
24+
Cloudflare Tunnels can be created one of two ways:
2625

27-
```sh
28-
curl -L https://github.com/cloudflare/cloudflared/releases/latest/download/cloudflared-linux-amd64 -o cloudflared
29-
chmod +x cloudflared
30-
sudo mv cloudflared /usr/local/bin/
31-
```
26+
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.
3228

33-
</TabItem>
34-
<TabItem label="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.
3530

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.
3933

40-
</TabItem>
41-
<TabItem label="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/).
4236

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.
4638

47-
</TabItem>
48-
<TabItem label="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.
4940

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:
67-
68-
```yaml
69-
tunnel: <YOUR_TUNNEL_ID>
70-
credentials-file: /home/user/.cloudflared/<YOUR_TUNNEL_ID>.json
41+
:::
7142

72-
ingress:
73-
- hostname: "*"
74-
service: http://localhost:8080
75-
originRequest:
76-
noTLSVerify: true
77-
- service: http_status:404
78-
```
43+
:::note
7944

80-
Start the tunnel:
45+
[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.
8146

82-
```sh
83-
cloudflared tunnel run workers-vpc-tunnel
84-
```
47+
:::
8548

8649
## Cloud platform setup guides
8750

0 commit comments

Comments
 (0)