Skip to content

Commit d9aefb5

Browse files
stevenGravyptgott
andauthored
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>
1 parent acdda10 commit d9aefb5

File tree

1 file changed

+10
-10
lines changed

1 file changed

+10
-10
lines changed

docs/pages/reference/networking.mdx

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -36,21 +36,21 @@ following use cases:
3636
</TabItem>
3737
<TabItem scope={["cloud", "team"]} label="Cloud-Hosted">
3838

39-
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.
4346

4447
```yaml
45-
public_addr: ["service-one.example.com", "service-two.example.com"]
48+
public_addr: "myapp.example.teleport.sh"
4649
```
4750

48-
Specifying a public address for a Teleport agent may be useful in the
49-
following use cases:
51+
For TCP applications you can specify a fully qualified domain name outside of `teleport.sh` in combination
52+
with [VNet](../enroll-resources/application-access/guides/vnet.mdx) since that domain is served via your machine's local network.
5053

51-
- You have multiple identical services behind a load balancer.
52-
- You want Teleport to issue an SSH certificate for the service with additional
53-
principals, e.g., host names.
5454
</TabItem>
5555
</Tabs>
5656

0 commit comments

Comments
 (0)