opensource/teleport
3
0
Fork 0
mirror of https://github.com/gravitational/teleport.git synced 2026-09-24 16:17:11 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs: update networking ports

Browse Source
This commit is contained in:
Steven Martin
2023-10-10 15:08:56 -04:00
parent 3df04ecbad
commit 75231c4d1b
1 changed files with 16 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/pages/reference/networking.mdx
+16 -7
View File
@@ -149,6 +149,10 @@ In those cases, they can set up separate listeners in the config file.
| 3023 | All clients | SSH port clients connect to. The Proxy Service will forward this connection to port `3022` on the destination service. |
| 3024 | Auth Service | SSH port used to create reverse SSH tunnels from behind-firewall environments into a trusted Proxy Service instance. |
| 3080 or 443 | Proxy Service | HTTPS connection to authenticate `tsh` users into the cluster. The same connection is used to serve a Web UI. |
| 3036 | Database Service | Traffic to MySQL databases.|
| 5432 | Database Service | Traffic to Postgres databases.|
| 27017 | Database Service | Traffic to MongoDB instances.|
| 6379 | Database Service | Traffic to Redis instances.|
### Auth Service ports
@@ -225,6 +229,15 @@ meaning that you can expose ports on that service's host directly to clients.
This is useful when you need to connect to resources directly if the Proxy
Service becomes unavailable.
<Admonition
type="tip"
title="Note"
>
In Teleport Cloud, the Auth and Proxy Services run in Teleport-owned infrastructure.
For this reason, Teleport Cloud customers must connect their resources via reverse tunnels.
Exposing ports for direct dial is only supported in self-hosted deployments.
</Admonition>
The table below describes the ports that each Teleport Service opens for proxied
traffic:
@@ -232,12 +245,8 @@ traffic:
| - | - | - |
| 3022 | SSH Service | Incoming SSH connections.|
| 3026 | Kubernetes Service | HTTPS traffic to a Kubernetes API server.|
| 3036 | Database Service | Traffic to MySQL databases.|
| 5432 | Database Service | Traffic to Postgres databases.|
| 27017 | Database Service | Traffic to MongoDB instances.|
| 6379 | Database Service | Traffic to Redis instances.|
| 3028 | Windows Desktop Service | Teleport Desktop Protocol traffic from Teleport clients.|
Applications registered with the Teleport Application Service can only be
accessed via the Teleport Proxy Service, not directly via the Application
Service.
You can only access enrolled applications and databases through the Teleport Proxy Service.
The Teleport Application Service and Teleport Database Service use reverse tunnel
connections through the Teleport Proxy Service and cannot expose ports directly.