Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[v16] docs: update database faq #47589

Merged
merged 2 commits into from
Oct 15, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 6 additions & 8 deletions docs/pages/enroll-resources/database-access/faq.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,7 @@ The Teleport Database Service currently supports the following protocols:
- MongoDB
- MySQL
- Oracle
- OpenSearch
- PostgreSQL
- Redis
- Snowflake
Expand Down Expand Up @@ -58,17 +59,14 @@ This is useful when the Teleport Web UI is running behind an L7 load balancer
(e.g. ALB in AWS), in which case the PostgreSQL/MySQL proxy needs to be exposed
on a plain TCP load balancer (e.g. NLB in AWS).

Using [TLS routing](../../reference/architecture/tls-routing.mdx) for the Teleport Proxy Service allows for all
database connections with the web public address.

</TabItem>
<TabItem scope={["cloud","team"]} label="Cloud-Hosted">

In Teleport Enterprise Cloud, the Proxy Service uses the following ports for
Database Service client traffic:

|Configuration setting|Port|
|---|---|
|`mysql_public_addr`|`3036`|
|`postgres_public_addr`|`443`|
|`mongo_public_addr`|`443`|
In Teleport Enterprise (Cloud), database connections use the web public address
since [TLS routing](../../reference/architecture/tls-routing.mdx) is applied.

</TabItem>
</Tabs>
Expand Down
Loading