Skip to content

Commit

Permalink
Address PR feedback
Browse files Browse the repository at this point in the history
  • Loading branch information
ptgott committed Apr 18, 2022
1 parent 5d97130 commit 451f720
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions docs/pages/setup/admin/trustedclusters.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -23,20 +23,20 @@ This guide will explain how to:

<Details title="Teleport Node Tunneling" scope={["enterprise", "oss"]} scopeOnly opened>

If you have a large number of devices on different networks, such as managed
IoT devices, you can configure your Teleport Nodes to connect to your cluster
via Teleport Node Tunneling. Instead of connecting to the Auth Service
directly, a Node connects to the Proxy Service, and the Auth Service creates a
reverse tunnel to the Node.
If your Nodes are deployed behind a firewall or otherwise not reachable by the
Teleport Proxy Service, you can connect them to your Teleport cluster via
Teleport Node Tunneling. Instead of connection to the Auth Service directly,
each Node connects to the Proxy Service, and the Auth Service creates a reverse
tunnel to the Node.

Learn more in [Adding Nodes to the Cluster](./adding-nodes.mdx).
Learn more in [Adding Nodes to the Cluster](./adding-nodes.mdx).

</Details>

## How Trusted Clusters work

Teleport can partition compute infrastructure into multiple clusters. A cluster
is a group of Teleport SSH Nodes connected to the cluster's Auth Service, which
is a group of Teleport resources connected to the cluster's Auth Service, which
acts as a certificate authority (CA) for all users and nodes in the cluster.

To retrieve an SSH certificate, users must authenticate with a cluster through a
Expand Down

0 comments on commit 451f720

Please sign in to comment.