Skip to content

Commit

Permalink
[v14] docs: update database faq (#47591)
Browse files Browse the repository at this point in the history
* docs: update database faq

* docs: verbiage update on db faq

Co-authored-by: Paul Gottschling <[email protected]>

---------

Co-authored-by: Paul Gottschling <[email protected]>
  • Loading branch information
stevenGravy and ptgott authored Oct 15, 2024
1 parent ce0fe10 commit e2c2fbb
Showing 1 changed file with 6 additions and 8 deletions.
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

0 comments on commit e2c2fbb

Please sign in to comment.