You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: update cloud networking on proxy service (#47506)
* docs: update cloud networking on proxy service
* docs: update verbiage for networking
Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com>
* docs: update cloud-hosted public address
* docs: update verbiage for app access for networking
* docs: update verbiage for public address for networks with cloud
Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com>
---------
Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com>
All Teleport services (e.g., the Application Service and Database Service) have
40
-
an optional `public_addr` property that you can modify in each service's
41
-
configuration file. The public address can take an IP or a DNS name. It can also
42
-
be a list of values:
39
+
On Teleport Enterprise (Cloud), you can choose the sub-domain of
40
+
the domain `teleport.sh` for your account. That fully qualified domain name
41
+
(e.g., `example.teleport.sh`) is managed by Teleport for your account
42
+
along with any sub-domains assigned to Teleport-protected applications (e.g., `grafana.example.teleport.sh`).
43
+
44
+
The public address (`public_addr`) for the Teleport Application Service is configurable. In the case of web applications, the public address must be a subdomain of the Teleport account URL
45
+
since the domain and TLS certificates are maintained by Teleport.
0 commit comments