diff --git a/docs/pages/choose-an-edition/teleport-cloud/architecture.mdx b/docs/pages/choose-an-edition/teleport-cloud/architecture.mdx index 8fc9ca8311545..ea6f9e77af9a6 100644 --- a/docs/pages/choose-an-edition/teleport-cloud/architecture.mdx +++ b/docs/pages/choose-an-edition/teleport-cloud/architecture.mdx @@ -36,10 +36,10 @@ cluster state deleted between 7 and 30 days after the lapse. ## High Availability ### Auth Service -The Teleport [auth service](https://goteleport.com/docs/architecture/authentication/) is deployed within the AWS us-west-2 region in 4 availability zones, and can tolerate a single zone failure. AWS guarantees [99.99%](https://aws.amazon.com/compute/sla/) of monthly uptime. +The Teleport [auth service](../../architecture/authentication.mdx) is deployed within the AWS us-west-2 region in 4 availability zones, and can tolerate a single zone failure. AWS guarantees [99.99%](https://aws.amazon.com/compute/sla/) of monthly uptime. ### Proxies -The Teleport [proxy service](https://goteleport.com/docs/architecture/proxy/) can be deployed to multiple AWS regions around the world for low-latency access to distributed infrastructure. +The Teleport [proxy service](../../architecture/proxy.mdx) can be deployed to multiple AWS regions around the world for low-latency access to distributed infrastructure. - us-west-2 (default) - us-east-1 diff --git a/docs/pages/contributing/documentation/how-to-contribute.mdx b/docs/pages/contributing/documentation/how-to-contribute.mdx index b44bb1e4fa249..295e878d6b3e6 100644 --- a/docs/pages/contributing/documentation/how-to-contribute.mdx +++ b/docs/pages/contributing/documentation/how-to-contribute.mdx @@ -85,8 +85,7 @@ the most recent version of our documentation are reflected for the versions of Teleport we currently support. -You can find our list of currently supported versions in the FAQ: -https://goteleport.com/docs/faq/#which-version-of-teleport-is-supported +You can find our list of currently supported versions in the [FAQ](../../faq.mdx#which-version-of-teleport-is-supported). There are many ways to create a backport, and we will illustrate three common diff --git a/docs/pages/deploy-a-cluster/helm-deployments/digitalocean.mdx b/docs/pages/deploy-a-cluster/helm-deployments/digitalocean.mdx index 19769c3ef96d4..568b68f2daa33 100644 --- a/docs/pages/deploy-a-cluster/helm-deployments/digitalocean.mdx +++ b/docs/pages/deploy-a-cluster/helm-deployments/digitalocean.mdx @@ -27,7 +27,7 @@ Kubernetes. ## Prerequisites - DigitalOcean account. -- Your workstation configured with [kubectl](https://kubernetes.io/docs/tasks/tools/), [Helm](https://helm.sh/docs/intro/install/), [doctl](https://docs.digitalocean.com/reference/doctl/how-to/install/), and the Teleport [tsh](https://goteleport.com/docs/installation/) client. +- Your workstation configured with [kubectl](https://kubernetes.io/docs/tasks/tools/), [Helm](https://helm.sh/docs/intro/install/), [doctl](https://docs.digitalocean.com/reference/doctl/how-to/install/), and the Teleport [tsh](../../installation.mdx) client. ## Step 1/4. Create a DigitalOcean Kubernetes cluster diff --git a/docs/pages/machine-id/getting-started.mdx b/docs/pages/machine-id/getting-started.mdx index ccce6d1d4483c..92135add4468f 100644 --- a/docs/pages/machine-id/getting-started.mdx +++ b/docs/pages/machine-id/getting-started.mdx @@ -22,26 +22,6 @@ Here's an overview of what you will do: (!/docs/pages/includes/tctl.mdx!) - - -TLS Routing support was added to Machine ID in [Teleport -9.3](https://goteleport.com/docs/preview/upcoming-releases/#teleport-93). For -earlier versions, the Teleport Proxy Server will need to be configured with a -dedicated SSH listener. - -```yaml -version: v1 -proxy_service: - enabled: "yes" - listen_addr: "0.0.0.0:3023" - ... -``` - - ## Step 1/4. Download and install Teleport (=teleport.version=) In this step, you will be downloading and installing Teleport binaries onto the @@ -93,7 +73,7 @@ auditor no-login-6566121f-b602-47f1-a118-c9c618ee5aec session:list,r editor user:list,create,read,update,delete,... ``` -Machine ID can join with a token or the [IAM Method](https://goteleport.com/docs/setup/guides/joining-nodes-aws) on AWS. +Machine ID can join with a token or the [IAM Method](../management/guides/joining-nodes-aws-iam.mdx) on AWS. Assuming that you are using the default `access` role, ensure that you use the `--logins` flag when adding your bot to specify the SSH logins that you wish to diff --git a/docs/pages/machine-id/guides/ansible.mdx b/docs/pages/machine-id/guides/ansible.mdx index dfdcfbe2795c3..f5f3fa6a02a04 100644 --- a/docs/pages/machine-id/guides/ansible.mdx +++ b/docs/pages/machine-id/guides/ansible.mdx @@ -17,21 +17,6 @@ You will need the following tools to use Teleport with Ansible. - `ansible` >= (=ansible.min_version=) - Optional tool `jq` to process `JSON` output - -TLS Routing support will be added to Machine ID in [Teleport -9.3](https://goteleport.com/docs/preview/upcoming-releases/#teleport-93). Until -that time, the Teleport Proxy Server will need to be configured with a -dedicated SSH listener. - -```yaml -version: v1 -proxy_service: - enabled: "yes" - listen_addr: "0.0.0.0:3023" - ... -``` - - In addition, if you already have not done so, follow the [Machine ID Getting Started Guide](../getting-started.mdx) to create a bot user and start Machine ID. diff --git a/docs/pages/machine-id/guides/github-actions.mdx b/docs/pages/machine-id/guides/github-actions.mdx index aec63da0a0b84..b78a7d7343fe8 100644 --- a/docs/pages/machine-id/guides/github-actions.mdx +++ b/docs/pages/machine-id/guides/github-actions.mdx @@ -29,7 +29,7 @@ Actions runners as well as GitHub Enterprise Server. (!docs/pages/includes/tctl.mdx!) -- A node that is a part of the Teleport cluster with [Server Access](https://goteleport.com/docs/server-access/introduction/). +- A node that is a part of the Teleport cluster with [Server Access](../../server-access/introduction.mdx). - Your user should have the privileges to create token resources. - A GitHub repository with GitHub Actions enabled. This guide uses the example `gravitational/example` repo, however this value should be replaced with your own unique repo. diff --git a/docs/pages/machine-id/guides/host-certificate.mdx b/docs/pages/machine-id/guides/host-certificate.mdx index 8d69b8a393a17..0c1b4333f5a9a 100644 --- a/docs/pages/machine-id/guides/host-certificate.mdx +++ b/docs/pages/machine-id/guides/host-certificate.mdx @@ -6,7 +6,7 @@ description: Issuing Host Certificates with Machine ID for OpenSSH servers. Host certificates are generally created on Teleport for access to OpenSSH servers that can not otherwise join a Teleport cluster. While long-lived certificates may be applied for this purpose, short-lived and regularly rotated host certificates generated through Teleport help to provide a number of security benefits over their long-lived counterparts. Regular certificate rotation reduces risk by ensuring that any potentially stolen -certificates are usable for a shorter period of time. Additionally, when coupled with Teleport's [RBAC](https://goteleport.com/docs/access-controls/guides/role-templates/) +certificates are usable for a shorter period of time. Additionally, when coupled with Teleport's [RBAC](../../access-controls/guides/role-templates.mdx) support and host certificate **Principals** and **Predicates**, you can apply limitations to both the process of creating host certificates, as well as the host certificates themselves. @@ -402,4 +402,4 @@ to connect to OpenSSH with Teleport, see the following documentation: - [Using Teleport With OpenSSH](../../server-access/guides/openssh.mdx) - [Using SSH Host Certificates](https://goteleport.com/blog/how-to-ssh-properly/) - [Machine ID Configuration Reference](../reference/configuration.mdx) -- [Joining Nodes using the IAM method](https://goteleport.com/docs/setup/guides/joining-nodes-aws) +- [Joining Nodes using the IAM method](../../management/guides/joining-nodes-aws-iam.mdx) diff --git a/docs/pages/machine-id/guides/jenkins.mdx b/docs/pages/machine-id/guides/jenkins.mdx index 5ad59f1097eee..579bcc7144a02 100644 --- a/docs/pages/machine-id/guides/jenkins.mdx +++ b/docs/pages/machine-id/guides/jenkins.mdx @@ -19,21 +19,6 @@ You will need the following tools to use Teleport with Jenkins. - Jenkins - The `tctl` admin tool version >= (=teleport.version=) - -TLS Routing support will be added to Machine ID in [Teleport -9.3](https://goteleport.com/docs/preview/upcoming-releases/#teleport-93). Until -that time, the Teleport Proxy Server will need to be configured with a -dedicated SSH listener. - -```yaml -version: v1 -proxy_service: - enabled: "yes" - listen_addr: "0.0.0.0:3023" - ... -``` - - (!docs/pages/includes/tctl.mdx!) ## Architecture diff --git a/docs/pages/management/export-audit-events/fluentd.mdx b/docs/pages/management/export-audit-events/fluentd.mdx index 3d74ad01b0320..08268d60e7c7b 100644 --- a/docs/pages/management/export-audit-events/fluentd.mdx +++ b/docs/pages/management/export-audit-events/fluentd.mdx @@ -514,7 +514,7 @@ Teleport Cluster, ensure that: ## Next Steps Read more about -[impersonation](https://goteleport.com/docs/access-controls/guides/impersonation/) +[impersonation](../../access-controls/guides/impersonation.mdx) here. While this guide uses the `tctl auth sign` command to issue credentials for the diff --git a/docs/pages/reference/cli.mdx b/docs/pages/reference/cli.mdx index 1dd3a8df3f147..b2306ad0b6a4c 100644 --- a/docs/pages/reference/cli.mdx +++ b/docs/pages/reference/cli.mdx @@ -54,7 +54,7 @@ For more information on subcommands when working with the `teleport` cli, use th The `teleport start` command includes a large number of optional configuration flags. While configuration flags for `teleport start` can be used to set parameters for Teleport's configuration, -we recommend using a [configuration file](https://goteleport.com/docs/reference/config/) in production. +we recommend using a [configuration file](./config.mdx) in production. #### Flags @@ -1973,7 +1973,7 @@ The following flags are specific to Google Workspace: | `--google-acc-uri` | URI of your service account credentials file. Example: `file:///var/lib/teleport/gworkspace-creds.json`.| | `--google-acc` | String containing Google service account credentials. | | `--google-admin` | Email of a Google admin to impersonate. | -| `--google-legacy` | Flag to select groups with direct membership filtered by domain (legacy behavior).
Disabled by default. [More info](https://goteleport.com/docs/enterprise/sso/google-workspace/#how-teleport-uses-google-workspace-apis) | +| `--google-legacy` | Flag to select groups with direct membership filtered by domain (legacy behavior).
Disabled by default. [More info](../access-controls/sso/google-workspace.mdx#how-teleport-uses-google-workspace-apis) | | `--google-id` | Shorthand for setting the `--id` flag to `.apps.googleusercontent.com` |