Skip to content

Commit

Permalink
Clarify target and infra app setup (#17243)
Browse files Browse the repository at this point in the history
* Clarify target and infra app setup

* Update ssh-infrastructure-access.mdx

Removing redundant link

* turn note into partial

* revise IP address note

---------

Co-authored-by: Ranbel Sun <ranbel@cloudflare.com>
  • Loading branch information
asamborski and ranbel authored Oct 4, 2024
1 parent 46a5f89 commit 1a18f9d
Show file tree
Hide file tree
Showing 4 changed files with 18 additions and 7 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -49,6 +49,11 @@ To connect your devices to Cloudflare:
Next, configure your SSH server to trust the Cloudflare SSH CA. This allows Access to authenticate using short-lived certificates instead of traditional SSH keys.

### Generate a Cloudflare SSH CA

<Render file="ssh/ssh-proxy-ca-note" />

To generate a Cloudflare SSH CA and get its public key:

<Render file="ssh/ssh-proxy-ca" />

### Save the public key
Expand All @@ -62,7 +67,7 @@ Next, configure your SSH server to trust the Cloudflare SSH CA. This allows Acce

## 8. Connect as a user

Users can use any SSH client to connect to the target, as long as they are logged into the WARP client on their device. Users do not need to modify any SSH configs on their device. For example, to SSH from a terminal:
Users can use any SSH client to connect to the target, as long as they are logged into the WARP client on their device. If the target is located within a particular virtual network, ensure that the WARP client is [connected to that virtual network](/cloudflare-one/connections/connect-networks/private-net/cloudflared/tunnel-virtual-networks/#connect-to-a-virtual-network) before initiating the connection. Users do not need to modify any SSH configs on their device. For example, to SSH from a terminal:

```sh
ssh <username>@<target IP>
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -31,10 +31,7 @@ Cloudflare Gateway will take the identity from a token and, using short-lived ce

Instead of traditional SSH keys, Gateway uses short-lived certificates to authenticate traffic between Cloudflare and your origin.

:::note

Other short-lived CAs, such as those used to [secure SSH servers behind Cloudflare Access](/cloudflare-one/applications/non-http/short-lived-certificates-legacy/), are incompatible with the Gateway SSH proxy. For SSH logging to work, you must create a new CA using the `gateway_ca` API endpoint.
:::
<Render file="ssh/ssh-proxy-ca-note" />

To generate a Gateway SSH proxy CA and get its public key:

Expand Down
4 changes: 2 additions & 2 deletions src/content/partials/cloudflare-one/access/add-target.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -13,14 +13,14 @@ To create a new target:
<TabItem label="Dashboard">
1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Network** > **Targets**.
2. Select **Add a target**.
3. In **Target hostname**, enter a user-friendly name for the target resource. We recommend using the server hostname, for example `production-server`. The hostname does not need to be unique and can be reused for multiple targets.
3. In **Target hostname**, enter a user-friendly name for the target resource. We recommend using the server hostname, for example `production-server`. The hostname does not need to be unique and can be reused for multiple targets. Hostnames are used to define the subset of targets included in an infrastructure application and are not used in DNS address resolution.
<Details header="Format restrictions">
- Case insensitive
- Contain no more than 255 characters
- Contain only alphanumeric characters, `-`, or `.` (no spaces allowed)
- Start and end with an alphanumeric character
</Details>
4. In **IP addresses**, enter the private IPv4 and/or IPv6 address of the target resource. If the IP address overlaps across multiple private networks, select the [virtual network](/cloudflare-one/connections/connect-networks/private-net/cloudflared/tunnel-virtual-networks/) where the resource is located.
4. In **IP addresses**, enter the private IPv4 and/or IPv6 address of the target resource. If the IP address overlaps across multiple private networks, select the [virtual network](/cloudflare-one/connections/connect-networks/private-net/cloudflared/tunnel-virtual-networks/) where the resource is located. This IP address and virtual network pairing is now assigned to this target and cannot be reused in another target by design.
:::note[IP address requirements]
- Public IPs are not currently supported.
- The IP address must be reachable through Cloudflare Tunnel.
Expand Down
9 changes: 9 additions & 0 deletions src/content/partials/cloudflare-one/ssh/ssh-proxy-ca-note.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
---
{}

---

:::note

Other short-lived CAs, such as those used to [secure SSH servers behind Cloudflare Access](/cloudflare-one/applications/non-http/short-lived-certificates-legacy/), are incompatible with the Gateway SSH proxy. For SSH logging to work, you must create a new CA using the `gateway_ca` API endpoint.
:::

0 comments on commit 1a18f9d

Please sign in to comment.