mirror of
https://github.com/gravitational/teleport.git
synced 2026-10-11 22:49:54 +00:00
Consolidate Reference docs section contents (#58248)
* Consolidate Reference docs section contents Closes #56206 Reduce the number of first-level children in the Reference section of the docs from 23 to 9, not counting the index page available at `/docs/reference/`. This makes the Reference section easier to navigate, since a user can more readily form a mental model of the content available in the section with fewer items and a more thematic organization. - Add a section for deployment references, consolidating reference guides for configuring and architecting a Teleport deployment. - Move the Predicate Language and User Types references into the Access Controls section of References. - Add a section for API reference guides, consolidating the Terraform, MWI Terraform, and Operator sections. - Move Cloud FAQ to Quick Links. This places the guide next to the main FAQ in the sidebar to make it more discoverable, since the guide is currently rather hidden. This also helps pave the way to merge the two FAQs in the future. * Add an MWI reference section The MWI Terraform module reference does not belong with reference guides for API clients. Add a section to the reference guide for Machine & Workload Identity. * Rename "API" to "Infrastructure as Code" Teleport users expect tctl, Operator, and Terraform Provider docs to be in an Infrastructure as Code reference section, rather than the more vague "API" section. Responds to **ravicious** feedback.
This commit is contained in:
Paul Gottschling
+8
-8
@@ -166,7 +166,7 @@ During the migration from v15 to v16, the options mentioned above should be remo
|
||||
#### DynamoDB permission requirements have changed
|
||||
|
||||
Teleport clusters using the dynamodb backend must now have the `dynamodb:ConditionCheckItem`
|
||||
permission. For a full list of all required permissions see the Teleport [Backend Reference](docs/pages/reference/backends.mdx#dynamodb).
|
||||
permission. For a full list of all required permissions see the Teleport [Backend Reference](docs/pages/reference/deployment/backends.mdx#dynamodb).
|
||||
|
||||
#### Disabling multi-factor authentication_type
|
||||
|
||||
@@ -176,7 +176,7 @@ Support for disabling multi-factor authentication has been removed
|
||||
|
||||
Users with custom `ssh_config` should modify their ProxyCommand to use the new,
|
||||
more performant, `tbot ssh-proxy-command`. See the
|
||||
[v16 upgrade guide](docs/pages/reference/machine-id/v16-upgrade-guide.mdx) for
|
||||
[v16 upgrade guide](docs/pages/reference/machine-workload-identity/machine-id/v16-upgrade-guide.mdx) for
|
||||
more details.
|
||||
|
||||
#### Default keyboard shortcuts in Teleport Connect have been changed
|
||||
@@ -500,7 +500,7 @@ that supports efficient searching, sorting, and filtering operations. Teleport
|
||||
Enterprise (Cloud) customers will have their audit log automatically migrated to
|
||||
this new backend.
|
||||
|
||||
See the documentation [here](docs/pages/reference/backends.mdx#athena).
|
||||
See the documentation [here](docs/pages/reference/deployment/backends.mdx#athena).
|
||||
|
||||
#### Access lists
|
||||
|
||||
@@ -593,7 +593,7 @@ In Teleport 14, `tbot` can now be configured to write artifacts such as
|
||||
credentials and configuration files directly to a Kubernetes secret rather than
|
||||
a directory on the local file system.
|
||||
|
||||
For more information, see [docs](docs/pages/reference/machine-id/configuration.mdx).
|
||||
For more information, see [docs](docs/pages/reference/machine-workload-identity/machine-id/configuration.mdx).
|
||||
|
||||
### Breaking changes and deprecations
|
||||
|
||||
@@ -2057,7 +2057,7 @@ connections if the HTTP proxy is set in their environment and does not allow
|
||||
connections to the Teleport Proxy Service.
|
||||
|
||||
Refer to the
|
||||
[documentation](docs/pages/reference/networking.mdx#http-connect-proxies)
|
||||
[documentation](docs/pages/reference/deployment/networking.mdx#http-connect-proxies)
|
||||
for more details.
|
||||
|
||||
#### New APT repos
|
||||
@@ -2105,7 +2105,7 @@ s3://bucket/path?region=us-east-1&use_fips_endpoint=false
|
||||
```
|
||||
|
||||
See the [S3/DynamoDB backend
|
||||
documentation](docs/pages/reference/backends.mdx) for more information.
|
||||
documentation](docs/pages/reference/deployment/backends.mdx) for more information.
|
||||
|
||||
## 9.3.9
|
||||
|
||||
@@ -2344,7 +2344,7 @@ Teleport build infrastructure was updated to use Go v1.17.9 to fix CVE-2022-2467
|
||||
|
||||
Teleport users can now use PostgreSQL or CockroachDB for storing Auth Service data.
|
||||
|
||||
See the [documentation](docs/pages/reference/backends.mdx) for more information.
|
||||
See the [documentation](docs/pages/reference/deployment/backends.mdx) for more information.
|
||||
|
||||
### Server-side filtering and pagination
|
||||
|
||||
@@ -3624,7 +3624,7 @@ permissions](./docs/pages/enroll-resources/kubernetes-access/controls.mdx).
|
||||
|
||||
##### Path prefix for etcd
|
||||
|
||||
The [etcd backend](docs/pages/reference/backends.mdx#etcd) now correctly uses
|
||||
The [etcd backend](docs/pages/reference/deployment/backends.mdx#etcd) now correctly uses
|
||||
the “prefix” config value when storing data. Upgrading from 4.2 to 4.3 will
|
||||
migrate the data as needed at startup. Make sure you follow our Teleport
|
||||
[upgrade guidance](docs/pages/upgrading/upgrading.mdx).
|
||||
|
||||
+614
-19
@@ -101,7 +101,7 @@
|
||||
},
|
||||
{
|
||||
"source": "/reference/operator-resources/resources.teleport.dev_accesslists/",
|
||||
"destination": "/reference/operator-resources/resources-teleport-dev-accesslists/",
|
||||
"destination": "/reference/infrastructure-as-code/operator-resources/resources-teleport-dev-accesslists/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
@@ -111,62 +111,62 @@
|
||||
},
|
||||
{
|
||||
"source": "/reference/operator-resources/resources.teleport.dev_githubconnectors/",
|
||||
"destination": "/reference/operator-resources/resources-teleport-dev-githubconnectors/",
|
||||
"destination": "/reference/infrastructure-as-code/operator-resources/resources-teleport-dev-githubconnectors/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/operator-resources/resources.teleport.dev_loginrules/",
|
||||
"destination": "/reference/operator-resources/resources-teleport-dev-loginrules/",
|
||||
"destination": "/reference/infrastructure-as-code/operator-resources/resources-teleport-dev-loginrules/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/operator-resources/resources.teleport.dev_oidcconnectors/",
|
||||
"destination": "/reference/operator-resources/resources-teleport-dev-oidcconnectors/",
|
||||
"destination": "/reference/infrastructure-as-code/operator-resources/resources-teleport-dev-oidcconnectors/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/operator-resources/resources.teleport.dev_oktaimportrules/",
|
||||
"destination": "/reference/operator-resources/resources-teleport-dev-oktaimportrules/",
|
||||
"destination": "/reference/infrastructure-as-code/operator-resources/resources-teleport-dev-oktaimportrules/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/operator-resources/resources.teleport.dev_openssheiceserversv2/",
|
||||
"destination": "/reference/operator-resources/resources-teleport-dev-openssheiceserversv2/",
|
||||
"destination": "/reference/infrastructure-as-code/operator-resources/resources-teleport-dev-openssheiceserversv2/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/operator-resources/resources.teleport.dev_opensshserversv2/",
|
||||
"destination": "/reference/operator-resources/resources-teleport-dev-opensshserversv2/",
|
||||
"destination": "/reference/infrastructure-as-code/operator-resources/resources-teleport-dev-opensshserversv2/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/operator-resources/resources.teleport.dev_provisiontokens/",
|
||||
"destination": "/reference/operator-resources/resources-teleport-dev-provisiontokens/",
|
||||
"destination": "/reference/infrastructure-as-code/operator-resources/resources-teleport-dev-provisiontokens/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/operator-resources/resources.teleport.dev_roles/",
|
||||
"destination": "/reference/operator-resources/resources-teleport-dev-roles/",
|
||||
"destination": "/reference/infrastructure-as-code/operator-resources/resources-teleport-dev-roles/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/operator-resources/resources.teleport.dev_rolesv6/",
|
||||
"destination": "/reference/operator-resources/resources-teleport-dev-rolesv6/",
|
||||
"destination": "/reference/infrastructure-as-code/operator-resources/resources-teleport-dev-rolesv6/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/operator-resources/resources.teleport.dev_rolesv7/",
|
||||
"destination": "/reference/operator-resources/resources-teleport-dev-rolesv7/",
|
||||
"destination": "/reference/infrastructure-as-code/operator-resources/resources-teleport-dev-rolesv7/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/operator-resources/resources.teleport.dev_samlconnectors/",
|
||||
"destination": "/reference/operator-resources/resources-teleport-dev-samlconnectors/",
|
||||
"destination": "/reference/infrastructure-as-code/operator-resources/resources-teleport-dev-samlconnectors/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/operator-resources/resources.teleport.dev_users/",
|
||||
"destination": "/reference/operator-resources/resources-teleport-dev-users/",
|
||||
"destination": "/reference/infrastructure-as-code/operator-resources/resources-teleport-dev-users/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
@@ -221,12 +221,12 @@
|
||||
},
|
||||
{
|
||||
"source": "/machine-id/reference/telemetry/",
|
||||
"destination": "/reference/machine-id/telemetry/",
|
||||
"destination": "/reference/machine-workload-identity/machine-id/telemetry/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/machine-id/reference/v16-upgrade-guide/",
|
||||
"destination": "/reference/machine-id/v16-upgrade-guide/",
|
||||
"destination": "/reference/machine-workload-identity/machine-id/v16-upgrade-guide/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
@@ -286,7 +286,7 @@
|
||||
},
|
||||
{
|
||||
"source": "/reference/operator-resources/resources.teleport.dev_trustedclustersv2/",
|
||||
"destination": "/reference/operator-resources/resources-teleport-dev-trustedclustersv2/",
|
||||
"destination": "/reference/infrastructure-as-code/operator-resources/resources-teleport-dev-trustedclustersv2/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
@@ -736,17 +736,17 @@
|
||||
},
|
||||
{
|
||||
"source": "/enroll-resources/workload-identity/workload-attestation/",
|
||||
"destination": "/reference/workload-identity/workload-identity-api-and-workload-attestation/",
|
||||
"destination": "/reference/machine-workload-identity/workload-identity/workload-identity-api-and-workload-attestation/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/machine-workload-identity/workload-identity/workload-attestation/",
|
||||
"destination": "/reference/workload-identity/workload-identity-api-and-workload-attestation/",
|
||||
"destination": "/reference/machine-workload-identity/workload-identity/workload-identity-api-and-workload-attestation/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/machine-workload-identity/machine-id/deployment/bound-keypair/",
|
||||
"destination": "/reference/machine-id/bound-keypair/getting-started/",
|
||||
"destination": "/reference/machine-workload-identity/machine-id/bound-keypair/getting-started/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
@@ -1683,6 +1683,601 @@
|
||||
"source": "/zero-trust-access/sso/azuread/",
|
||||
"destination": "/zero-trust-access/sso/entra-id/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/backends/",
|
||||
"destination": "/reference/deployment/backends/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/cloud-faq/",
|
||||
"destination": "/cloud-faq/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/config/",
|
||||
"destination": "/reference/deployment/config/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/identity-security-config/",
|
||||
"destination": "/reference/deployment/identity-security-config/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/join-methods/",
|
||||
"destination": "/reference/deployment/join-methods/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/machine-id/bound-keypair/admin-guide/",
|
||||
"destination": "/reference/machine-workload-identity/machine-id/bound-keypair/admin-guide/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/machine-id/bound-keypair/",
|
||||
"destination": "/reference/machine-workload-identity/machine-id/bound-keypair/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/machine-id/bound-keypair/concepts/",
|
||||
"destination": "/reference/machine-workload-identity/machine-id/bound-keypair/concepts/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/machine-id/bound-keypair/getting-started/",
|
||||
"destination": "/reference/machine-workload-identity/machine-id/bound-keypair/getting-started/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/machine-id/configuration/",
|
||||
"destination": "/reference/machine-workload-identity/machine-id/configuration/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/machine-id/diagnostics-service/",
|
||||
"destination": "/reference/machine-workload-identity/machine-id/diagnostics-service/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/machine-id/github-actions/",
|
||||
"destination": "/reference/machine-workload-identity/machine-id/github-actions/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/machine-id/gitlab/",
|
||||
"destination": "/reference/machine-workload-identity/machine-id/gitlab/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/machine-id/",
|
||||
"destination": "/reference/machine-workload-identity/machine-id/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/machine-id/telemetry/",
|
||||
"destination": "/reference/machine-workload-identity/machine-id/telemetry/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/machine-id/v16-upgrade-guide/",
|
||||
"destination": "/reference/machine-workload-identity/machine-id/v16-upgrade-guide/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/managed-updates-v2/",
|
||||
"destination": "/reference/deployment/managed-updates-v2/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/monitoring/audit/",
|
||||
"destination": "/reference/deployment/monitoring/audit/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/monitoring/metrics/",
|
||||
"destination": "/reference/deployment/monitoring/metrics/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/monitoring/",
|
||||
"destination": "/reference/deployment/monitoring/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/monitoring/tracing-service-configuration/",
|
||||
"destination": "/reference/deployment/monitoring/tracing-service-configuration/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/networking/",
|
||||
"destination": "/reference/deployment/networking/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/operator-resources/",
|
||||
"destination": "/reference/infrastructure-as-code/operator-resources/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/operator-resources/resources-teleport-dev-accesslists/",
|
||||
"destination": "/reference/infrastructure-as-code/operator-resources/resources-teleport-dev-accesslists/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/operator-resources/resources-teleport-dev-appsv3/",
|
||||
"destination": "/reference/infrastructure-as-code/operator-resources/resources-teleport-dev-appsv3/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/operator-resources/resources-teleport-dev-autoupdateconfigsv1/",
|
||||
"destination": "/reference/infrastructure-as-code/operator-resources/resources-teleport-dev-autoupdateconfigsv1/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/operator-resources/resources-teleport-dev-autoupdateversionsv1/",
|
||||
"destination": "/reference/infrastructure-as-code/operator-resources/resources-teleport-dev-autoupdateversionsv1/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/operator-resources/resources-teleport-dev-botsv1/",
|
||||
"destination": "/reference/infrastructure-as-code/operator-resources/resources-teleport-dev-botsv1/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/operator-resources/resources-teleport-dev-databasesv3/",
|
||||
"destination": "/reference/infrastructure-as-code/operator-resources/resources-teleport-dev-databasesv3/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/operator-resources/resources-teleport-dev-githubconnectors/",
|
||||
"destination": "/reference/infrastructure-as-code/operator-resources/resources-teleport-dev-githubconnectors/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/operator-resources/resources-teleport-dev-loginrules/",
|
||||
"destination": "/reference/infrastructure-as-code/operator-resources/resources-teleport-dev-loginrules/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/operator-resources/resources-teleport-dev-oidcconnectors/",
|
||||
"destination": "/reference/infrastructure-as-code/operator-resources/resources-teleport-dev-oidcconnectors/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/operator-resources/resources-teleport-dev-oktaimportrules/",
|
||||
"destination": "/reference/infrastructure-as-code/operator-resources/resources-teleport-dev-oktaimportrules/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/operator-resources/resources-teleport-dev-openssheiceserversv2/",
|
||||
"destination": "/reference/infrastructure-as-code/operator-resources/resources-teleport-dev-openssheiceserversv2/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/operator-resources/resources-teleport-dev-opensshserversv2/",
|
||||
"destination": "/reference/infrastructure-as-code/operator-resources/resources-teleport-dev-opensshserversv2/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/operator-resources/resources-teleport-dev-provisiontokens/",
|
||||
"destination": "/reference/infrastructure-as-code/operator-resources/resources-teleport-dev-provisiontokens/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/operator-resources/resources-teleport-dev-roles/",
|
||||
"destination": "/reference/infrastructure-as-code/operator-resources/resources-teleport-dev-roles/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/operator-resources/resources-teleport-dev-rolesv6/",
|
||||
"destination": "/reference/infrastructure-as-code/operator-resources/resources-teleport-dev-rolesv6/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/operator-resources/resources-teleport-dev-rolesv7/",
|
||||
"destination": "/reference/infrastructure-as-code/operator-resources/resources-teleport-dev-rolesv7/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/operator-resources/resources-teleport-dev-rolesv8/",
|
||||
"destination": "/reference/infrastructure-as-code/operator-resources/resources-teleport-dev-rolesv8/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/operator-resources/resources-teleport-dev-samlconnectors/",
|
||||
"destination": "/reference/infrastructure-as-code/operator-resources/resources-teleport-dev-samlconnectors/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/operator-resources/resources-teleport-dev-trustedclustersv2/",
|
||||
"destination": "/reference/infrastructure-as-code/operator-resources/resources-teleport-dev-trustedclustersv2/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/operator-resources/resources-teleport-dev-users/",
|
||||
"destination": "/reference/infrastructure-as-code/operator-resources/resources-teleport-dev-users/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/operator-resources/resources-teleport-dev-workloadidentitiesv1/",
|
||||
"destination": "/reference/infrastructure-as-code/operator-resources/resources-teleport-dev-workloadidentitiesv1/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/predicate-language/",
|
||||
"destination": "/reference/access-controls/predicate-language/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/resources/",
|
||||
"destination": "/reference/infrastructure-as-code/resources/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/signals/",
|
||||
"destination": "/reference/deployment/signals/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/signature-algorithms/",
|
||||
"destination": "/reference/deployment/signature-algorithms/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider-mwi/data-sources/",
|
||||
"destination": "/reference/machine-workload-identity/terraform-provider-mwi/data-sources/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider-mwi/data-sources/kubernetes/",
|
||||
"destination": "/reference/machine-workload-identity/terraform-provider-mwi/data-sources/kubernetes/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider-mwi/ephemeral-resources/",
|
||||
"destination": "/reference/machine-workload-identity/terraform-provider-mwi/ephemeral-resources/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider-mwi/ephemeral-resources/kubernetes/",
|
||||
"destination": "/reference/machine-workload-identity/terraform-provider-mwi/ephemeral-resources/kubernetes/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider-mwi/",
|
||||
"destination": "/reference/machine-workload-identity/terraform-provider-mwi/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/data-sources/access_list/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/data-sources/access_list/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/data-sources/access_list_member/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/data-sources/access_list_member/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/data-sources/access_monitoring_rule/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/data-sources/access_monitoring_rule/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/data-sources/app/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/data-sources/app/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/data-sources/auth_preference/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/data-sources/auth_preference/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/data-sources/autoupdate_config/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/data-sources/autoupdate_config/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/data-sources/autoupdate_version/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/data-sources/autoupdate_version/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/data-sources/cluster_maintenance_config/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/data-sources/cluster_maintenance_config/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/data-sources/cluster_networking_config/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/data-sources/cluster_networking_config/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/data-sources/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/data-sources/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/data-sources/database/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/data-sources/database/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/data-sources/dynamic_windows_desktop/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/data-sources/dynamic_windows_desktop/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/data-sources/github_connector/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/data-sources/github_connector/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/data-sources/health_check_config/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/data-sources/health_check_config/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/data-sources/installer/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/data-sources/installer/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/data-sources/login_rule/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/data-sources/login_rule/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/data-sources/oidc_connector/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/data-sources/oidc_connector/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/data-sources/okta_import_rule/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/data-sources/okta_import_rule/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/data-sources/provision_token/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/data-sources/provision_token/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/data-sources/role/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/data-sources/role/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/data-sources/saml_connector/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/data-sources/saml_connector/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/data-sources/session_recording_config/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/data-sources/session_recording_config/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/data-sources/static_host_user/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/data-sources/static_host_user/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/data-sources/trusted_cluster/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/data-sources/trusted_cluster/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/data-sources/trusted_device/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/data-sources/trusted_device/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/data-sources/user/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/data-sources/user/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/data-sources/workload_identity/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/data-sources/workload_identity/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/resources/access_list/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/resources/access_list/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/resources/access_list_member/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/resources/access_list_member/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/resources/access_monitoring_rule/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/resources/access_monitoring_rule/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/resources/app/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/resources/app/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/resources/auth_preference/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/resources/auth_preference/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/resources/autoupdate_config/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/resources/autoupdate_config/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/resources/autoupdate_version/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/resources/autoupdate_version/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/resources/bot/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/resources/bot/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/resources/cluster_maintenance_config/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/resources/cluster_maintenance_config/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/resources/cluster_networking_config/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/resources/cluster_networking_config/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/resources/database/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/resources/database/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/resources/dynamic_windows_desktop/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/resources/dynamic_windows_desktop/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/resources/github_connector/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/resources/github_connector/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/resources/health_check_config/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/resources/health_check_config/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/resources/installer/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/resources/installer/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/resources/login_rule/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/resources/login_rule/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/resources/oidc_connector/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/resources/oidc_connector/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/resources/okta_import_rule/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/resources/okta_import_rule/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/resources/provision_token/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/resources/provision_token/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/resources/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/resources/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/resources/role/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/resources/role/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/resources/saml_connector/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/resources/saml_connector/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/resources/server/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/resources/server/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/resources/session_recording_config/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/resources/session_recording_config/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/resources/static_host_user/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/resources/static_host_user/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/resources/trusted_cluster/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/resources/trusted_cluster/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/resources/trusted_device/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/resources/trusted_device/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/resources/user/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/resources/user/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/resources/workload_identity/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/resources/workload_identity/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/terraform-provider/",
|
||||
"destination": "/reference/infrastructure-as-code/terraform-provider/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/user-types/",
|
||||
"destination": "/reference/access-controls/user-types/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/workload-identity/attributes/",
|
||||
"destination": "/reference/machine-workload-identity/workload-identity/attributes/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/workload-identity/configuration-resource-migration/",
|
||||
"destination": "/reference/machine-workload-identity/workload-identity/configuration-resource-migration/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/workload-identity/issuer-override/",
|
||||
"destination": "/reference/machine-workload-identity/workload-identity/issuer-override/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/workload-identity/revocations/",
|
||||
"destination": "/reference/machine-workload-identity/workload-identity/revocations/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/workload-identity/sigstore-attestation/",
|
||||
"destination": "/reference/machine-workload-identity/workload-identity/sigstore-attestation/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/workload-identity/workload-identity-api-and-workload-attestation/",
|
||||
"destination": "/reference/machine-workload-identity/workload-identity/workload-identity-api-and-workload-attestation/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/workload-identity/workload-identity-resource/",
|
||||
"destination": "/reference/machine-workload-identity/workload-identity/workload-identity-resource/",
|
||||
"permanent": true
|
||||
},
|
||||
{
|
||||
"source": "/reference/workload-identity/",
|
||||
"destination": "/reference/machine-workload-identity/workload-identity/",
|
||||
"permanent": true
|
||||
}
|
||||
]
|
||||
}
|
||||
|
||||
+2
-2
@@ -1106,8 +1106,8 @@
|
||||
"hte"
|
||||
],
|
||||
"ignorePaths": [
|
||||
"**/reference/terraform-provider/**",
|
||||
"**/reference/operator-resources/**",
|
||||
"**/reference/infrastructure-as-code/terraform-provider/**",
|
||||
"**/reference/infrastructure-as-code/operator-resources/**",
|
||||
"**/includes/reference/code-blocks-no-cspell/**"
|
||||
]
|
||||
}
|
||||
|
||||
@@ -9,7 +9,7 @@ tags:
|
||||
|
||||
This page provides answers to frequently asked questions about Teleport
|
||||
Enterprise (Cloud). For a list of frequently asked questions about Teleport in
|
||||
general, see [Frequently Asked Questions](../faq.mdx).
|
||||
general, see [Frequently Asked Questions](faq.mdx).
|
||||
|
||||
## Billing and usage
|
||||
|
||||
@@ -29,7 +29,7 @@ If you plan to use S3 and DynamoDB as storage backends, we can provide data for
|
||||
|
||||
### How long will Teleport Enterprise Cloud retain my data?
|
||||
|
||||
See our documentation on [data retention](architecture/teleport-cloud-architecture.mdx).
|
||||
See our documentation on [data retention](reference/architecture/teleport-cloud-architecture.mdx).
|
||||
|
||||
### Is an independent security audit available?
|
||||
|
||||
@@ -51,18 +51,18 @@ for customer data including session recordings and user records.
|
||||
|
||||
### Can I get a list of IP addresses that my infrastructure will need to allow connections to?
|
||||
|
||||
See the [Public IP Address Allowlist](../ips.mdx) for the list of IP addresses used for inbound connections to Teleport Enterprise Cloud.
|
||||
See the [Public IP Address Allowlist](ips.mdx) for the list of IP addresses used for inbound connections to Teleport Enterprise Cloud.
|
||||
|
||||
### Can I configure a list of IP addresses which are allowed to connect to Teleport Enterprise Cloud?
|
||||
|
||||
We do not have plans to offer support for inbound connection IP allowlists.
|
||||
|
||||
We believe mTLS with strong user and [device identity](../identity-governance/device-trust/guide.mdx) provides the best available
|
||||
We believe mTLS with strong user and [device identity](identity-governance/device-trust/guide.mdx) provides the best available
|
||||
security for client authentication.
|
||||
|
||||
For customers that require IP-based control for compliance purposes, we do
|
||||
support IP Pinning. For more information see `pin_source_ip` in our [Teleport
|
||||
Access Controls Reference](access-controls/roles.mdx).
|
||||
Access Controls Reference](reference/access-controls/roles.mdx).
|
||||
|
||||
### Are internal connections encrypted / authenticated?
|
||||
|
||||
@@ -74,7 +74,7 @@ S3, are established using encryption provided by AWS, both at rest and in transi
|
||||
|
||||
You can connect servers, Kubernetes clusters, databases, desktops, and
|
||||
applications using [reverse
|
||||
tunnels](../enroll-resources/agents/agents.mdx).
|
||||
tunnels](enroll-resources/agents/agents.mdx).
|
||||
|
||||
There is no need to open any ports on your infrastructure for inbound traffic.
|
||||
|
||||
@@ -88,7 +88,7 @@ If you plan on connecting more than 10,000 nodes or agents, please contact your
|
||||
### Are dynamic node tokens available?
|
||||
|
||||
After [connecting](#how-can-i-access-the-tctl-admin-tool) `tctl` to Teleport Enterprise Cloud, users can generate
|
||||
[dynamic tokens](../enroll-resources/agents/join-token.mdx):
|
||||
[dynamic tokens](enroll-resources/agents/join-token.mdx):
|
||||
|
||||
```code
|
||||
$ tctl nodes add --ttl=5m --roles=node,proxy --token=$(uuid)
|
||||
@@ -98,7 +98,7 @@ $ tctl nodes add --ttl=5m --roles=node,proxy --token=$(uuid)
|
||||
|
||||
### How can I access the `tctl` admin tool?
|
||||
|
||||
Find the appropriate download at [Installation](../installation/installation.mdx).
|
||||
Find the appropriate download at [Installation](installation/installation.mdx).
|
||||
|
||||
After downloading the tools, first log in to your cluster using `tsh`, then use `tctl` remotely:
|
||||
|
||||
@@ -120,11 +120,11 @@ $ tctl tokens add --type=node
|
||||
|
||||
### Is there a way to forward Teleport Enterprise Cloud audit events to my company's internal Security Information and Event Management (SIEM)?
|
||||
|
||||
Yes. We recommend Teleport's [event handler plugin](../zero-trust-access/export-audit-events/fluentd.mdx) to export Teleport Enterprise Cloud audit events.
|
||||
Yes. We recommend Teleport's [event handler plugin](zero-trust-access/export-audit-events/fluentd.mdx) to export Teleport Enterprise Cloud audit events.
|
||||
|
||||
### Is it possible to store audit logs and session recordings in my own S3 bucket?
|
||||
|
||||
Yes, you can configure [External Audit Storage](../zero-trust-access/management/external-audit-storage.mdx).
|
||||
Yes, you can configure [External Audit Storage](zero-trust-access/management/external-audit-storage.mdx).
|
||||
|
||||
### Is it possible to enable proxy recording mode?
|
||||
|
||||
@@ -141,12 +141,12 @@ The ability to download recordings for offline viewing will be available in a fu
|
||||
If you have Teleport Agents connected to a Teleport Enterprise Cloud cluster
|
||||
that are more than one major version behind, you might experience compatibility
|
||||
issues unless your Teleport Agents are enrolled in automatic updates. See the [Upgrading
|
||||
Overview](../upgrading/overview.mdx) for more information.
|
||||
Overview](upgrading/overview.mdx) for more information.
|
||||
|
||||
To get version information for your Teleport Agents, see [How can I find version information on
|
||||
connected agents?](#how-can-i-find-version-information-on-connected-agents).
|
||||
|
||||
If you want more details about cluster updates, see [Cloud Cluster Updates](../upgrading/cloud-cluster-updates.mdx).
|
||||
If you want more details about cluster updates, see [Cloud Cluster Updates](upgrading/cloud-cluster-updates.mdx).
|
||||
|
||||
For more information about automatic updates and compatibility issues, contact
|
||||
[Teleport support](https://goteleport.com/support/).
|
||||
@@ -165,7 +165,7 @@ connected agents?](#how-can-i-find-version-information-on-connected-agents) for
|
||||
|
||||
### Are updates times configurable for Teleport Enterprise Cloud?
|
||||
|
||||
Yes, see [Cloud Cluster Updates](../upgrading/cloud-cluster-updates.mdx#maintenance-windows) for further instruction.
|
||||
Yes, see [Cloud Cluster Updates](upgrading/cloud-cluster-updates.mdx#maintenance-windows) for further instruction.
|
||||
|
||||
### When are agents automatically updated?
|
||||
|
||||
@@ -177,7 +177,7 @@ update the software when new versions are found.
|
||||
If you enroll in automatic agent updates, Teleport Agents are automatically
|
||||
updated after your Teleport cluster is updated during your scheduled maintenance
|
||||
period. For more information, read the [Automatic Agent
|
||||
Updates](../upgrading/agent-managed-updates.mdx) guide.
|
||||
Updates](upgrading/agent-managed-updates.mdx) guide.
|
||||
|
||||
### How can I find version information on connected agents?
|
||||
|
||||
@@ -239,7 +239,7 @@ than through a port allocated to that service.
|
||||
In this case, you can see that TLS routing is enabled, and that the Proxy
|
||||
Service's public web address (`ssh.public_addr`) is `example.teleport.sh:443`.
|
||||
|
||||
Read more in our [TLS Routing](architecture/tls-routing.mdx) guide.
|
||||
Read more in our [TLS Routing](reference/architecture/tls-routing.mdx) guide.
|
||||
|
||||
### How does Teleport manage web certificates? Can I upload my own?
|
||||
|
||||
@@ -250,7 +250,7 @@ certificate or use a custom domain name.
|
||||
### Where does Teleport Enterprise Cloud run?
|
||||
|
||||
Teleport Cloud runs on Amazon Web Services (AWS). We run proxies in a variety
|
||||
of regions all over the world, and allow customers to [select the region](architecture/teleport-cloud-architecture.mdx) where the data is stored.
|
||||
of regions all over the world, and allow customers to [select the region](reference/architecture/teleport-cloud-architecture.mdx) where the data is stored.
|
||||
|
||||
### Are you using AWS-managed encryption keys, or CMKs via KMS?
|
||||
|
||||
@@ -260,7 +260,7 @@ We use AWS-managed keys. Currently there is no option to provide your own key.
|
||||
|
||||
It's a Teleport-managed S3 bucket with AWS-managed keys by default.
|
||||
|
||||
Configuring [External Audit Storage](../zero-trust-access/management/external-audit-storage.mdx) will allow
|
||||
Configuring [External Audit Storage](zero-trust-access/management/external-audit-storage.mdx) will allow
|
||||
you to use your own S3 bucket.
|
||||
|
||||
### Is IPv6 Supported for connections to Teleport Enterprise Cloud?
|
||||
@@ -313,7 +313,7 @@ When you sign up for a Teleport Enterprise (Cloud) account and set up your first
|
||||
user within the account, the Teleport Web UI displays a set of recovery codes:
|
||||
|
||||
|
||||
codes](../img/cloud/recovery-codes.png)
|
||||
|
||||
Save the recovery codes into a safe location, such as your organization's
|
||||
password manager. You can use these codes to reset your account if you lose
|
||||
@@ -1134,7 +1134,7 @@ proxy_templates:
|
||||
In the configuration above, `query` accepts an predicate expression. This has
|
||||
priority over search but will be ignored if a host is provided. See the
|
||||
[predicate language
|
||||
documentation](../reference/predicate-language.mdx#resource-filtering) for
|
||||
documentation](../reference/access-controls/predicate-language.mdx#resource-filtering) for
|
||||
predicate expression examples.
|
||||
|
||||
`tsh -J {{proxy}} ssh` and `tsh -J {{proxy}} proxy ssh` will attempt to match the
|
||||
|
||||
@@ -194,7 +194,7 @@ A **configuration resource** is a document stored on the **Teleport Auth
|
||||
Service** backend that specifies settings for your **Teleport cluster**.
|
||||
Examples include **roles**, **local users**, and **authentication connectors**
|
||||
|
||||
Read more in our [resource reference](./reference/resources.mdx).
|
||||
Read more in our [resource reference](reference/infrastructure-as-code/resources.mdx).
|
||||
|
||||
### Role
|
||||
|
||||
|
||||
@@ -252,9 +252,9 @@ While this guide shows you how to create a token using `tctl`, you can also
|
||||
manage tokens using the Teleport Terraform provider or Kubernetes operator. See
|
||||
the following documentation for information on the token resource:
|
||||
- [Terraform
|
||||
provider](../../reference/terraform-provider/resources/provision_token.mdx)
|
||||
provider](../../reference/infrastructure-as-code/terraform-provider/resources/provision_token.mdx)
|
||||
- [Kubernetes
|
||||
operator](../../reference/operator-resources/resources-teleport-dev-provisiontokens.mdx)
|
||||
operator](../../reference/infrastructure-as-code/operator-resources/resources-teleport-dev-provisiontokens.mdx)
|
||||
|
||||
You can set up a system to automate the process of assigning join tokens to
|
||||
agents, ensuring that all Teleport services you run have the correct join
|
||||
|
||||
@@ -151,7 +151,7 @@ Here's how it works in detail:
|
||||
|
||||
For more information about Discovery Service configuration, refer to
|
||||
[one of the guides above](#supported-clouds) or the
|
||||
[Discovery Service Config File Reference](../../../reference/config.mdx).
|
||||
[Discovery Service Config File Reference](../../../reference/deployment/config.mdx).
|
||||
|
||||
## How the Database Service works
|
||||
|
||||
|
||||
@@ -314,4 +314,4 @@ logs can be found on the targeted VM at
|
||||
- Read [Joining Nodes via Azure Managed Identity](../../agents/azure.mdx)
|
||||
for more information on Azure tokens.
|
||||
- Full documentation on Azure discovery configuration can be found through the [
|
||||
config file reference documentation](../../../reference/config.mdx).
|
||||
config file reference documentation](../../../reference/deployment/config.mdx).
|
||||
|
||||
@@ -304,4 +304,4 @@ for details on alternate methods.
|
||||
- Read [Joining Services via GCP](../../agents/gcp.mdx)
|
||||
for more information on GCP tokens.
|
||||
- Full documentation on GCP discovery configuration can be found through the [
|
||||
config file reference documentation](../../../reference/config.mdx).
|
||||
config file reference documentation](../../../reference/deployment/config.mdx).
|
||||
|
||||
@@ -151,4 +151,4 @@ Learn more about protecting MCP servers with Teleport in the following topics:
|
||||
|
||||
- [MCP Access Control](rbac.mdx).
|
||||
- Configuration and CLI [reference](../../reference/agent-services/mcp-access.mdx).
|
||||
- Audit events [reference](../../reference/monitoring/audit.mdx#event-types).
|
||||
- Audit events [reference](../../reference/deployment/monitoring/audit.mdx#event-types).
|
||||
|
||||
@@ -376,7 +376,7 @@ further Getting Started exercises.
|
||||
sign-on provider. Read the
|
||||
[documentation](../../zero-trust-access/sso/sso.mdx) to learn more.
|
||||
- Learn more about Teleport `tsh` through the [reference documentation](../../reference/cli/tsh.mdx#tsh-ssh).
|
||||
- For a complete list of ports used by Teleport, read the [Networking Guide](../../reference/networking.mdx).
|
||||
- For a complete list of ports used by Teleport, read the [Networking Guide](../../reference/deployment/networking.mdx).
|
||||
|
||||
## Resources
|
||||
|
||||
|
||||
@@ -408,4 +408,4 @@ ends will also include the `"enhanced_recording": true` field, similar to the fo
|
||||
- Read more about
|
||||
[session recording](../../../reference/architecture/session-recording.mdx).
|
||||
- See all configuration options for Enhanced Session Recording in our
|
||||
[Configuration Reference](../../../reference/config.mdx).
|
||||
[Configuration Reference](../../../reference/deployment/config.mdx).
|
||||
|
||||
@@ -483,5 +483,5 @@ on the hosts.
|
||||
|
||||
- Configure automatic user provisioning for [database access](../../database-access/auto-user-provisioning/auto-user-provisioning.mdx).
|
||||
- Configure automatic user provisioning for [desktop access](../../../reference/agent-services/desktop-access-reference/user-creation.mdx).
|
||||
- Configure automatic user provisioning with [Terraform](../../../reference/terraform-provider/resources/role.mdx).
|
||||
- Configure automatic user provisioning with [Terraform](../../../reference/infrastructure-as-code/terraform-provider/resources/role.mdx).
|
||||
Note when using the terraform provider that some values may be different than described in this guide.
|
||||
|
||||
+1
-1
@@ -108,7 +108,7 @@ Yes. You can copy and paste using a mouse.
|
||||
|
||||
## What TCP ports does Teleport use?
|
||||
|
||||
Please refer to our [Networking](./reference/networking.mdx) guide.
|
||||
Please refer to our [Networking](reference/deployment/networking.mdx) guide.
|
||||
|
||||
## Does Teleport support authentication via OIDC, SAML, or Active Directory?
|
||||
|
||||
|
||||
@@ -93,7 +93,7 @@ across distributed infrastructures.
|
||||
| [Dual Authorization](identity-governance/access-requests/access-requests.mdx) | ✔ | ✔ | ✖ |
|
||||
| [Session Sharing & Moderation](zero-trust-access/authentication/joining-sessions.mdx) | ✔ | ✔ | ✖ |
|
||||
|**Identity-based audit events:** ||||
|
||||
| [Structured Audit Logs](./reference/monitoring/audit.mdx) | ✔ | ✔ | ✔ |
|
||||
| [Structured Audit Logs](reference/deployment/monitoring/audit.mdx) | ✔ | ✔ | ✔ |
|
||||
| [Export to SIEM](zero-trust-access/export-audit-events/export-audit-events.mdx) | ✔ | ✔ | ✔ |
|
||||
|**Regulatory standards and frameworks:**||||
|
||||
| [FedRAMP Control](zero-trust-access/compliance-frameworks/fedramp.mdx) | ✖ | ✔ | ✖ |
|
||||
@@ -164,7 +164,7 @@ and non-human identities.
|
||||
| **Management and licensing:** ||||
|
||||
| Annual or multi-year contracts, volume discounts | ✔ | ✔ | ✖ |
|
||||
| Anonymized Usage Tracking | ✔ | ✔ | Opt-in |
|
||||
| [Backend support](./reference/backends.mdx) | All data is stored in DynamoDB and S3 with server-side encryption. | Any S3-compatible storage for session records, many managed backends for custom audit log storage | Any S3-compatible storage for session records, many managed backends for custom audit log storage. |
|
||||
| [Backend support](reference/deployment/backends.mdx) | All data is stored in DynamoDB and S3 with server-side encryption. | Any S3-compatible storage for session records, many managed backends for custom audit log storage | Any S3-compatible storage for session records, many managed backends for custom audit log storage. |
|
||||
| Multi-region failover using Cockroach DB | ✔ | ✔ | ✖ |
|
||||
| Data storage location | Data is stored in Teleport's AWS infrastructure with audit logs/sessions optionally in customer AWS accounts. Proxy Service instances are deployed across the world for low-latency access. | Can store data anywhere in the world, on most managed cloud backends | Can store data anywhere in the world, on most managed cloud backends |
|
||||
| License | Commercial | Commercial | Commercial for binaries, with restrictions: Free usage for companies with \<100 employees and \<US$10M annual revenue. Code on GitHub distributed via AGPL-3.0 |
|
||||
|
||||
@@ -341,7 +341,7 @@ with Terraform will inherit the grants of the existing Access List.
|
||||
|
||||
- Learn how [nested Access Lists](./nested-access-lists.mdx) grants inheritance work.
|
||||
- Familiarize yourself with
|
||||
[teleport_access_list](../../reference/terraform-provider/resources/access_list.mdx) and
|
||||
[teleport_access_list_member](../../reference/terraform-provider/resources/access_list_member.mdx)
|
||||
[teleport_access_list](../../reference/infrastructure-as-code/terraform-provider/resources/access_list.mdx) and
|
||||
[teleport_access_list_member](../../reference/infrastructure-as-code/terraform-provider/resources/access_list_member.mdx)
|
||||
Terraform resources.
|
||||
|
||||
|
||||
@@ -28,7 +28,7 @@ Users are able to write their own custom access monitoring queries by querying t
|
||||
|
||||
## Prerequisites
|
||||
(!docs/pages/includes/edition-prereqs-tabs.mdx!)
|
||||
- For self-hosted Teleport the [Amazon Athena Backend](../reference/backends.mdx) is required.
|
||||
- For self-hosted Teleport the [Amazon Athena Backend](../reference/deployment/backends.mdx) is required.
|
||||
|
||||
|
||||
### Configuration
|
||||
@@ -504,7 +504,7 @@ ORDER BY
|
||||
event_date
|
||||
```
|
||||
|
||||
**Suggestion:** Use short-lived tokens to reduce risk of compromise or [delegated](../reference/join-methods.mdx) joining when possible.
|
||||
**Suggestion:** Use short-lived tokens to reduce risk of compromise or [delegated](../reference/deployment/join-methods.mdx) joining when possible.
|
||||
|
||||
### Root SSH sessions
|
||||
|
||||
|
||||
@@ -395,7 +395,7 @@ the request has met the criteria specified in one of the thresholds in
|
||||
`allow.request.thresholds` associated with that role.
|
||||
|
||||
The value of `filter` is an expression that uses the Teleport [predicate
|
||||
language](../../reference/predicate-language.mdx).
|
||||
language](../../reference/access-controls/predicate-language.mdx).
|
||||
|
||||
For example, the following configuration includes four thresholds, three of which
|
||||
have filters:
|
||||
|
||||
@@ -189,7 +189,7 @@ both an approval rule and a denial rule, the denial rule takes precedence.
|
||||
resource. For more details about the `access_monitoring_rule` resource, refer to the
|
||||
[Access Monitoring Rules Reference](../../reference/access-controls/access-monitoring-rules.mdx).
|
||||
- For configuration with Teleport Terraform Provider, refer to the
|
||||
[Terraform Resources Index](../../reference/terraform-provider/resources/access_monitoring_rule.mdx)
|
||||
[Terraform Resources Index](../../reference/infrastructure-as-code/terraform-provider/resources/access_monitoring_rule.mdx)
|
||||
- For configuration options with SSO, refer to the
|
||||
[Single Sign-On Guides](../../zero-trust-access/sso/sso.mdx).
|
||||
- For more details about managing resource labels, refer to the
|
||||
|
||||
@@ -11,7 +11,7 @@ tags:
|
||||
Attribute mapping configures Teleport SAML Identity Provider to assert custom user attributes in SAML response.
|
||||
The Teleport SAML IdP supports three configurable fields for attribute mapping:
|
||||
- `name`: Name of the outgoing attribute. Required. Name should be unique across attribute mapping.
|
||||
- `value`: Value defined using a [predicate expression](../../reference/predicate-language.mdx), which can reference
|
||||
- `value`: Value defined using a [predicate expression](../../reference/access-controls/predicate-language.mdx), which can reference
|
||||
Teleport usernames, roles or traits. Required.
|
||||
- `name_format`: SAML attribute name format. Optional. The following formats are supported:
|
||||
- `unspecified`: value equals to `urn:oasis:names:tc:SAML:2.0:attrname-format:unspecified`. Used as a default value.
|
||||
|
||||
@@ -27,7 +27,7 @@ A lock can target the following objects or attributes:
|
||||
- a Windows desktop by the desktop's name
|
||||
- an [Access Request](access-requests/access-requests.mdx) by UUID
|
||||
- a bot instance ID (for Machine & Workload Identity bots)
|
||||
- a join token name (for Machine & Workload Identity bots using a [delegated join method](../reference/join-methods.mdx#delegated-join-methods))
|
||||
- a join token name (for Machine & Workload Identity bots using a [delegated join method](../reference/deployment/join-methods.mdx#delegated-join-methods))
|
||||
|
||||
## How it works
|
||||
|
||||
@@ -101,7 +101,7 @@ with one of the following options:
|
||||
The most appropriate locking target for a Machine & Workload Identity bot
|
||||
depends on its join method.
|
||||
|
||||
For [delegated join methods](../reference/join-methods.mdx#secret-vs-delegated),
|
||||
For [delegated join methods](../reference/deployment/join-methods.mdx#secret-vs-delegated),
|
||||
it's best to target the specific join token the bot is using to join:
|
||||
```code
|
||||
$ tctl lock --join-token=example-token-name
|
||||
@@ -197,7 +197,7 @@ spec:
|
||||
```
|
||||
|
||||
The `kind: lock` resources can also be created and updated using `tctl create`
|
||||
as per usual. See the [Admin Guide](../reference/resources.mdx) for more
|
||||
as per usual. See the [Admin Guide](../reference/infrastructure-as-code/resources.mdx) for more
|
||||
details.
|
||||
</details>
|
||||
|
||||
|
||||
@@ -180,11 +180,11 @@ To create the required configuration resources:
|
||||
```
|
||||
|
||||
For full description of the inference configuration resources, see appropriate
|
||||
sections of [Teleport Resources Reference](../reference/resources.mdx):
|
||||
sections of [Teleport Resources Reference](../reference/infrastructure-as-code/resources.mdx):
|
||||
|
||||
- [`inference_model`](../reference/resources.mdx#inference-model)
|
||||
- [`inference_secret`](../reference/resources.mdx#inference-secret)
|
||||
- [`inference_policy`](../reference/resources.mdx#inference-policy)
|
||||
- [`inference_model`](../reference/infrastructure-as-code/resources.mdx#inference-model)
|
||||
- [`inference_secret`](../reference/infrastructure-as-code/resources.mdx#inference-secret)
|
||||
- [`inference_policy`](../reference/infrastructure-as-code/resources.mdx#inference-policy)
|
||||
|
||||
## Step 3/4: Configure access to session summaries
|
||||
|
||||
@@ -412,5 +412,5 @@ Teleport exposes a couple of useful Prometheus metrics that can be used to
|
||||
monitor the session summarizer. Metrics are labeled by inference model name,
|
||||
and in case of OpenAI errors — additionally with the OpenAI API error code. See
|
||||
the [Teleport Metrics
|
||||
reference](../reference/monitoring/metrics.mdx#session-recording-summarizer)
|
||||
reference](../reference/deployment/monitoring/metrics.mdx#session-recording-summarizer)
|
||||
for details.
|
||||
|
||||
@@ -5,4 +5,4 @@ for more information on IAM Invite Tokens.
|
||||
Manager can be found in the [AWS Cloud Operations & Migrations Blog
|
||||
](https://aws.amazon.com/blogs/mt/applying-managed-instance-policy-best-practices/).
|
||||
- Full documentation on EC2 discovery configuration can be found through the [
|
||||
config file reference documentation](../../reference/config.mdx).
|
||||
config file reference documentation](../../reference/deployment/config.mdx).
|
||||
@@ -17,6 +17,6 @@
|
||||
- To authenticate a Web UI session you need [Teleport Connect](
|
||||
../../connect-your-client/teleport-connect.mdx#installation--upgrade)
|
||||
- Correct end-user IP propagation to your Teleport deployment:
|
||||
[X-Forwarded-For header](../../reference/config.mdx#proxy-service) (L7 load
|
||||
[X-Forwarded-For header](../../reference/deployment/config.mdx#proxy-service) (L7 load
|
||||
balancer) or [PROXY protocol](
|
||||
../../zero-trust-access/management/security/proxy-protocol.mdx) (L4 load balancer)
|
||||
|
||||
@@ -91,7 +91,7 @@ device web authentication ceremony failed. In this case it's likely that
|
||||
end-user IPs are not propagated correctly to your Teleport deployment.
|
||||
|
||||
* L7 load balancer: make sure it propagates the [X-Forwarded-For header](
|
||||
../../reference/config.mdx#proxy-service)
|
||||
../../reference/deployment/config.mdx#proxy-service)
|
||||
* L4 load balancer: enable [PROXY protocol](
|
||||
../../zero-trust-access/management/security/proxy-protocol.mdx)
|
||||
|
||||
|
||||
@@ -251,7 +251,7 @@ teleportAuthAddress: "teleport-auth.teleport-namespace.svc.cluster.local:3025"
|
||||
| `string` | `"kubernetes"` |
|
||||
|
||||
`tbot.joinMethod` describes how tbot joins the Teleport cluster.
|
||||
See [the join method reference](../../reference/join-methods.mdx) for a list fo supported values and detailed explanations.
|
||||
See [the join method reference](../../reference/deployment/join-methods.mdx) for a list fo supported values and detailed explanations.
|
||||
|
||||
## `annotations`
|
||||
|
||||
|
||||
@@ -216,7 +216,7 @@ teleportAuthAddress: "teleport-auth.teleport-namespace.svc.cluster.local:3025"
|
||||
| `string` | `"kubernetes"` |
|
||||
|
||||
`tbot.joinMethod` describes how tbot joins the Teleport cluster.
|
||||
See [the join method reference](../../reference/join-methods.mdx) for a list fo supported values and detailed explanations.
|
||||
See [the join method reference](../../reference/deployment/join-methods.mdx) for a list fo supported values and detailed explanations.
|
||||
|
||||
## `annotations`
|
||||
|
||||
|
||||
@@ -336,7 +336,7 @@ teleportAuthAddress: "teleport-auth.teleport-namespace.svc.cluster.local:3025"
|
||||
| `string` | `"kubernetes"` |
|
||||
|
||||
`tbot.joinMethod` describes how tbot joins the Teleport cluster.
|
||||
See [the join method reference](../../reference/join-methods.mdx) for a list fo supported values and detailed explanations.
|
||||
See [the join method reference](../../reference/deployment/join-methods.mdx) for a list fo supported values and detailed explanations.
|
||||
|
||||
## `annotations`
|
||||
|
||||
|
||||
@@ -284,7 +284,7 @@ teleportAuthAddress: "teleport-auth.teleport-namespace.svc.cluster.local:3025"
|
||||
| `string` | `"kubernetes"` |
|
||||
|
||||
`tbot.joinMethod` describes how tbot joins the Teleport cluster.
|
||||
See [the join method reference](../../reference/join-methods.mdx) for a list fo supported values and detailed explanations.
|
||||
See [the join method reference](../../reference/deployment/join-methods.mdx) for a list fo supported values and detailed explanations.
|
||||
|
||||
## `annotations`
|
||||
|
||||
|
||||
@@ -212,7 +212,7 @@ teleportAuthAddress: "teleport-auth.teleport-namespace.svc.cluster.local:3025"
|
||||
| `string` | `"kubernetes"` |
|
||||
|
||||
`tbot.joinMethod` describes how tbot joins the Teleport cluster.
|
||||
See [the join method reference](../../reference/join-methods.mdx) for a list fo supported values and detailed explanations.
|
||||
See [the join method reference](../../reference/deployment/join-methods.mdx) for a list fo supported values and detailed explanations.
|
||||
|
||||
## `annotations`
|
||||
|
||||
|
||||
@@ -248,7 +248,7 @@ teleportAuthAddress: "teleport-auth.teleport-namespace.svc.cluster.local:3025"
|
||||
| `string` | `"kubernetes"` |
|
||||
|
||||
`tbot.joinMethod` describes how tbot joins the Teleport cluster.
|
||||
See [the join method reference](../../reference/join-methods.mdx) for a list fo supported values and detailed explanations.
|
||||
See [the join method reference](../../reference/deployment/join-methods.mdx) for a list fo supported values and detailed explanations.
|
||||
|
||||
## `annotations`
|
||||
|
||||
|
||||
@@ -204,7 +204,7 @@ teleportAuthAddress: "teleport-auth.teleport-namespace.svc.cluster.local:3025"
|
||||
| `string` | `"kubernetes"` |
|
||||
|
||||
`tbot.joinMethod` describes how tbot joins the Teleport cluster.
|
||||
See [the join method reference](../../reference/join-methods.mdx) for a list fo supported values and detailed explanations.
|
||||
See [the join method reference](../../reference/deployment/join-methods.mdx) for a list fo supported values and detailed explanations.
|
||||
|
||||
## `annotations`
|
||||
|
||||
|
||||
@@ -216,7 +216,7 @@ teleportAuthAddress: "teleport-auth.teleport-namespace.svc.cluster.local:3025"
|
||||
| `string` | `"kubernetes"` |
|
||||
|
||||
`tbot.joinMethod` describes how tbot joins the Teleport cluster.
|
||||
See [the join method reference](../../reference/join-methods.mdx) for a list fo supported values and detailed explanations.
|
||||
See [the join method reference](../../reference/deployment/join-methods.mdx) for a list fo supported values and detailed explanations.
|
||||
|
||||
## `annotations`
|
||||
|
||||
|
||||
@@ -217,7 +217,7 @@ Ignored if `tbotConfig` is set.
|
||||
| `string` | `"kubernetes"` |
|
||||
|
||||
`joinMethod` describes how tbot joins the Teleport cluster.
|
||||
See [the join method reference](../../reference/join-methods.mdx) for a list fo supported values and detailed explanations.
|
||||
See [the join method reference](../../reference/deployment/join-methods.mdx) for a list fo supported values and detailed explanations.
|
||||
Ignored if `tbotConfig` is set.
|
||||
|
||||
## `token`
|
||||
|
||||
@@ -93,7 +93,7 @@ Its usage should be preferred.
|
||||
`joinParams.method` controls which join method will be used by the
|
||||
instance to join the Teleport cluster.
|
||||
|
||||
See [the join method reference](../../reference/join-methods.mdx) for the list of possible
|
||||
See [the join method reference](../../reference/deployment/join-methods.mdx) for the list of possible
|
||||
values, the implications of each join method, and guides to set up each method.
|
||||
|
||||
Common join-methods for the `teleport-kube-agent` are:
|
||||
@@ -112,7 +112,7 @@ Common join-methods for the `teleport-kube-agent` are:
|
||||
`joinParams.tokenName` controls which token is used by the agent to
|
||||
join the Teleport cluster.
|
||||
|
||||
When `joinParams.method` is [a delegated join method](../../reference/join-methods.mdx#delegated-join-methods),
|
||||
When `joinParams.method` is [a delegated join method](../../reference/deployment/join-methods.mdx#delegated-join-methods),
|
||||
the value is not sensitive.
|
||||
|
||||
When `joinParams.method` is `token` (by default), `joinParams.tokenName`
|
||||
@@ -134,7 +134,7 @@ If method is `kubernetes`, you must set [`teleportClusterName`](#teleportCluster
|
||||
|
||||
`teleportClusterName` is the name of the joined Teleport cluster.
|
||||
Setting this value is required when joining via the
|
||||
[Kubernetes JWKS or OIDC](../../reference/join-methods.mdx#kubernetes-jwks) join method.
|
||||
[Kubernetes JWKS or OIDC](../../reference/deployment/join-methods.mdx#kubernetes-jwks) join method.
|
||||
|
||||
When this value is set, the chart mounts a kubernetes service account token
|
||||
via a projected volume and configures Teleport to use it for joining.
|
||||
@@ -632,7 +632,7 @@ which does not have valid TLS certificates for testing.
|
||||
Teleport pods. The configuration will be merged with the chart-generated
|
||||
configuration and will take precedence in case of conflict.
|
||||
|
||||
See the [Teleport Configuration Reference](../../reference/config.mdx) for the list of supported fields.
|
||||
See the [Teleport Configuration Reference](../../reference/deployment/config.mdx) for the list of supported fields.
|
||||
|
||||
```yaml
|
||||
teleportConfig:
|
||||
@@ -1408,7 +1408,7 @@ Possible values are `text` (default) or `json`.
|
||||
|
||||
`log.extraFields` sets the fields used in logging for the Teleport process.
|
||||
|
||||
See the [Teleport config file reference](../../reference/config.mdx) for
|
||||
See the [Teleport config file reference](../../reference/deployment/config.mdx) for
|
||||
more details on possible values for `extra_fields`.
|
||||
|
||||
## `affinity`
|
||||
|
||||
@@ -75,7 +75,7 @@ method. `kubernetes` is the most common one.
|
||||
|
||||
`teleportClusterName` is the name of the joined Teleport cluster.
|
||||
Setting this value is required when joining via the
|
||||
[Kubernetes JWKS](../../reference/join-methods.mdx#kubernetes-jwks) join method.
|
||||
[Kubernetes JWKS](../../reference/deployment/join-methods.mdx#kubernetes-jwks) join method.
|
||||
|
||||
## `token`
|
||||
|
||||
|
||||
@@ -193,14 +193,14 @@ proxy_service:
|
||||
cert_file: /my/path/cert.pem
|
||||
```
|
||||
|
||||
See the Teleport [Configuration Reference](../reference/config.mdx) for whether a
|
||||
See the Teleport [Configuration Reference](../reference/deployment/config.mdx) for whether a
|
||||
field you would like to assign requires a file path.
|
||||
|
||||
### Ports
|
||||
|
||||
A single Teleport process can run multiple services, each of which listens on a
|
||||
specific set of ports depending on your configuration. See our [Networking
|
||||
Reference](../reference/networking.mdx#ports) for the ports on your Teleport
|
||||
Reference](../reference/deployment/networking.mdx#ports) for the ports on your Teleport
|
||||
container to expose.
|
||||
|
||||
### Extracting certificates from distroless images
|
||||
|
||||
@@ -9,7 +9,7 @@ tags:
|
||||
- platform-wide
|
||||
---
|
||||
|
||||
Whether you are installing Teleport as a cluster or as an agent that talks to the cluster, the Teleport binary is the same. The difference is only in how you [configure it](../reference/config.mdx), which you will need to do after installation. Before choosing an installation method below, you should identify your particular use case. There are three:
|
||||
Whether you are installing Teleport as a cluster or as an agent that talks to the cluster, the Teleport binary is the same. The difference is only in how you [configure it](../reference/deployment/config.mdx), which you will need to do after installation. Before choosing an installation method below, you should identify your particular use case. There are three:
|
||||
|
||||
1. **Installing Teleport as a cluster:** Install a self-hosted Teleport cluster to provide secure, identity-based access to all your infrastructure. If you are running Teleport Enterprise Cloud, you will not need this use case, as the cluster is managed for you.
|
||||
2. **Installing Teleport as an agent:** Install a Teleport Agent on your infrastructure resource to enroll it with your cluster for centralized access management.
|
||||
|
||||
@@ -78,7 +78,7 @@ The above methods for installing Teleport on a Linux server do not generate a Te
|
||||
|
||||
See the following guides for help setting up a configuration file:
|
||||
|
||||
- [Teleport Configuration Reference](../reference/config.mdx): This will provide you with the command you need to generate and populate the `/etc/config.yaml` file as well as further configuration options for your cluster.
|
||||
- [Teleport Configuration Reference](../reference/deployment/config.mdx): This will provide you with the command you need to generate and populate the `/etc/config.yaml` file as well as further configuration options for your cluster.
|
||||
- [Self-Hosted Demo Cluster](../zero-trust-access/deploy-a-cluster/deploy-a-cluster.mdx): If you are deploying the Teleport Auth Service and Proxy Service, read this guide for an example of a configuration file.
|
||||
|
||||
## Installing Teleport as an agent
|
||||
@@ -111,7 +111,7 @@ See the following guides for examples of setting up a configuration file:
|
||||
Cluster](../zero-trust-access/deploy-a-cluster/deploy-a-cluster.mdx): If you are
|
||||
deploying the Teleport Auth Service and Proxy Service, read this guide for an
|
||||
example of a configuration file.
|
||||
- [Teleport Configuration Reference](../reference/config.mdx): A guide to all
|
||||
- [Teleport Configuration Reference](../reference/deployment/config.mdx): A guide to all
|
||||
configuration fields.
|
||||
|
||||
## Other Install Methods
|
||||
|
||||
@@ -14,7 +14,7 @@ Teleport solves this by issuing each agent its own identity and requiring the ag
|
||||
This allows Teleport to apply Role-Based Access Control (RBAC) at both the network and protocol level.
|
||||
|
||||
Teleport can secure infrastructure components such as SSH servers, Kubernetes clusters, databases, or MCP servers, when accessed by agents.
|
||||
All queries, commands, and requests executed by the agent are logged, providing full visibility and [auditability](/reference/monitoring/audit.mdx).
|
||||
All queries, commands, and requests executed by the agent are logged, providing full visibility and [auditability](../reference/deployment/monitoring/audit.mdx).
|
||||
|
||||
## Interested in a Design Partnership?
|
||||
|
||||
|
||||
@@ -58,4 +58,4 @@ When your IaC runs, Teleport generates a short-lived credential compatible with:
|
||||
The cloud provider issues a temporary credential linked to an IAM role, which allows the IaC workflow to perform its tasks. This credential exists only for the duration of the run and automatically expires once it completes.
|
||||
By design, this minimizes the risk of credential exposure and eliminates the need for manual rotation or long-term management. Because all major cloud providers support this method of authentication, IaC pipelines that manage resources across multiple clouds can rely on a single mechanism instead of juggling separate credential processes.
|
||||
|
||||
Teleport further enhances this model by recording every credential issuance in a comprehensive [audit log](/reference/monitoring/audit.mdx), simplifying compliance and reporting.
|
||||
Teleport further enhances this model by recording every credential issuance in a comprehensive [audit log](../reference/deployment/monitoring/audit.mdx), simplifying compliance and reporting.
|
||||
|
||||
@@ -269,5 +269,5 @@ spec:
|
||||
|
||||
## Next steps
|
||||
|
||||
- Read the [configuration reference](../../../reference/machine-id/configuration.mdx) to explore
|
||||
- Read the [configuration reference](../../../reference/machine-workload-identity/machine-id/configuration.mdx) to explore
|
||||
all the available configuration options.
|
||||
|
||||
@@ -225,5 +225,5 @@ has been configured to use both the client certificate and key.
|
||||
your bot may access.
|
||||
- Configure [JWTs](../../../enroll-resources/application-access/jwt/introduction.mdx) for your
|
||||
Application to remove the need for additional login credentials.
|
||||
- Read the [configuration reference](../../../reference/machine-id/configuration.mdx) to explore
|
||||
- Read the [configuration reference](../../../reference/machine-workload-identity/machine-id/configuration.mdx) to explore
|
||||
all the available configuration options.
|
||||
|
||||
@@ -147,7 +147,7 @@ Use `tctl create -f ./bot.yaml` to create the bot.
|
||||
|
||||
In order for `tbot` to be able to authenticate and join the Teleport cluster,
|
||||
we need to configure a join token. There are a number of different available
|
||||
[methods](../../../reference/join-methods.mdx), but for this guide we will use
|
||||
[methods](../../../reference/deployment/join-methods.mdx), but for this guide we will use
|
||||
the `kubernetes` method with a static JWKS. Please refer to the
|
||||
[Deploying tbot on Kubernetes](../deployment/kubernetes.mdx) guide for more
|
||||
in-depth information.
|
||||
@@ -332,7 +332,7 @@ groups.
|
||||
|
||||
## Next steps
|
||||
|
||||
- Read the [configuration reference](../../../reference/machine-id/configuration.mdx)
|
||||
- Read the [configuration reference](../../../reference/machine-workload-identity/machine-id/configuration.mdx)
|
||||
to explore all the available configuration options.
|
||||
- Read the [Teleport Kubernetes RBAC guide](../../../enroll-resources/kubernetes-access/controls.mdx)
|
||||
for more details on controlling Kubernetes access.
|
||||
|
||||
@@ -268,5 +268,5 @@ access controls.
|
||||
|
||||
## Next steps
|
||||
|
||||
- Read the [configuration reference](../../../reference/machine-id/configuration.mdx) to explore
|
||||
- Read the [configuration reference](../../../reference/machine-workload-identity/machine-id/configuration.mdx) to explore
|
||||
all the available configuration options.
|
||||
|
||||
@@ -209,7 +209,7 @@ this format is compatible with most Kubernetes tools including:
|
||||
|
||||
## Next steps
|
||||
|
||||
- Read the [configuration reference](../../../reference/machine-id/configuration.mdx) to explore
|
||||
- Read the [configuration reference](../../../reference/machine-workload-identity/machine-id/configuration.mdx) to explore
|
||||
all the available configuration options.
|
||||
- Read the [Teleport Kubernetes RBAC guide](../../../enroll-resources/kubernetes-access/controls.mdx)
|
||||
for more details on controlling Kubernetes access.
|
||||
|
||||
@@ -207,5 +207,5 @@ MCP client you are using.
|
||||
|
||||
- Read the [MCP access documentation](../../../enroll-resources/mcp-access/mcp-access.mdx)
|
||||
to learn more about Teleport's MCP integration and RBAC controls.
|
||||
- Read the [configuration reference](../../../reference/machine-id/configuration.mdx) to explore
|
||||
- Read the [configuration reference](../../../reference/machine-workload-identity/machine-id/configuration.mdx) to explore
|
||||
all the available configuration options for `tbot`.
|
||||
|
||||
@@ -172,5 +172,5 @@ SSH client certificates and either ProxyCommand or ProxyJump functionality.
|
||||
|
||||
## Next steps
|
||||
|
||||
- Read the [configuration reference](../../../reference/machine-id/configuration.mdx) to explore
|
||||
- Read the [configuration reference](../../../reference/machine-workload-identity/machine-id/configuration.mdx) to explore
|
||||
all the available configuration options.
|
||||
|
||||
@@ -149,5 +149,5 @@ $ tctl get role/tctl-test
|
||||
|
||||
- Explore the [`tctl` reference](../../../reference/cli/tctl.mdx) to discover all
|
||||
`tctl` can do.
|
||||
- Read the [configuration reference](../../../reference/machine-id/configuration.mdx) to explore
|
||||
- Read the [configuration reference](../../../reference/machine-workload-identity/machine-id/configuration.mdx) to explore
|
||||
all the available `tbot` configuration options.
|
||||
|
||||
@@ -130,6 +130,6 @@ Replace:
|
||||
|
||||
- Follow the [access guides](../access-guides/access-guides.mdx) to finish configuring `tbot` for
|
||||
your environment.
|
||||
- Read the [configuration reference](../../../reference/machine-id/configuration.mdx) to explore
|
||||
- Read the [configuration reference](../../../reference/machine-workload-identity/machine-id/configuration.mdx) to explore
|
||||
all the available configuration options.
|
||||
- [More information about `TELEPORT_ANONYMOUS_TELEMETRY`.](../../../reference/machine-id/telemetry.mdx)
|
||||
- [More information about `TELEPORT_ANONYMOUS_TELEMETRY`.](../../../reference/machine-workload-identity/machine-id/telemetry.mdx)
|
||||
|
||||
@@ -109,7 +109,7 @@ Replace:
|
||||
|
||||
You can find a full list of the token configuration options for Azure DevOps
|
||||
joining on the
|
||||
[join methods reference page.](../../../reference/join-methods.mdx#azure-devops-azure_devops)
|
||||
[join methods reference page.](../../../reference/deployment/join-methods.mdx#azure-devops-azure_devops)
|
||||
|
||||
Apply this to your Teleport cluster using `tctl`:
|
||||
|
||||
@@ -194,9 +194,9 @@ exit.
|
||||
## Further steps
|
||||
|
||||
- For more information about the Azure DevOps join method, read the
|
||||
[join method reference page.](../../../reference/join-methods.mdx#azure-devops-azure_devops)
|
||||
[join method reference page.](../../../reference/deployment/join-methods.mdx#azure-devops-azure_devops)
|
||||
- Follow the [access guides](../access-guides/access-guides.mdx) to finish configuring `tbot` for
|
||||
your environment.
|
||||
- Read the [configuration reference](../../../reference/machine-id/configuration.mdx) to explore
|
||||
- Read the [configuration reference](../../../reference/machine-workload-identity/machine-id/configuration.mdx) to explore
|
||||
all the available configuration options.
|
||||
- [More information about `TELEPORT_ANONYMOUS_TELEMETRY`.](../../../reference/machine-id/telemetry.mdx)
|
||||
- [More information about `TELEPORT_ANONYMOUS_TELEMETRY`.](../../../reference/machine-workload-identity/machine-id/telemetry.mdx)
|
||||
|
||||
@@ -132,6 +132,6 @@ Replace:
|
||||
|
||||
- Follow the [access guides](../access-guides/access-guides.mdx) to finish configuring `tbot` for
|
||||
your environment.
|
||||
- Read the [configuration reference](../../../reference/machine-id/configuration.mdx) to explore
|
||||
- Read the [configuration reference](../../../reference/machine-workload-identity/machine-id/configuration.mdx) to explore
|
||||
all the available configuration options.
|
||||
- [More information about `TELEPORT_ANONYMOUS_TELEMETRY`.](../../../reference/machine-id/telemetry.mdx)
|
||||
- [More information about `TELEPORT_ANONYMOUS_TELEMETRY`.](../../../reference/machine-workload-identity/machine-id/telemetry.mdx)
|
||||
|
||||
@@ -94,7 +94,7 @@ Let's go over the token resource's fields in more detail:
|
||||
- `spec.bitbucket.allow` is used to set rules for what Bitbucket Pipelines runs
|
||||
will be able to authenticate by using the token.
|
||||
|
||||
Refer to the [token reference](../../../reference/join-methods.mdx#bitbucket-pipelines-bitbucket)
|
||||
Refer to the [token reference](../../../reference/deployment/join-methods.mdx#bitbucket-pipelines-bitbucket)
|
||||
for a full list of valid fields.
|
||||
|
||||
Apply this to your Teleport cluster using `tctl`:
|
||||
@@ -157,7 +157,7 @@ credentials are needed in multiple steps.
|
||||
|
||||
- Follow the [access guides](../access-guides/access-guides.mdx) to finish configuring `tbot` for
|
||||
your environment.
|
||||
- Read the [configuration reference](../../../reference/machine-id/configuration.mdx) to explore
|
||||
- Read the [configuration reference](../../../reference/machine-workload-identity/machine-id/configuration.mdx) to explore
|
||||
all the available configuration options.
|
||||
- For more information about Bitbucket Pipelines itself, read
|
||||
[their documentation](https://support.atlassian.com/bitbucket-cloud/docs/get-started-with-bitbucket-pipelines/).
|
||||
|
||||
@@ -216,8 +216,8 @@ resources in your Teleport cluster that your CI/CD needs to interact with.
|
||||
|
||||
- Follow the [access guides](../access-guides/access-guides.mdx) to finish configuring `tbot` for
|
||||
your environment.
|
||||
- Read the [configuration reference](../../../reference/machine-id/configuration.mdx) to explore
|
||||
- Read the [configuration reference](../../../reference/machine-workload-identity/machine-id/configuration.mdx) to explore
|
||||
all the available configuration options.
|
||||
- For more information about CircleCI itself, read
|
||||
[their documentation](https://circleci.com/docs/).
|
||||
- [More information about `TELEPORT_ANONYMOUS_TELEMETRY`.](../../../reference/machine-id/telemetry.mdx)
|
||||
- [More information about `TELEPORT_ANONYMOUS_TELEMETRY`.](../../../reference/machine-workload-identity/machine-id/telemetry.mdx)
|
||||
|
||||
@@ -48,7 +48,7 @@ Machine ID.
|
||||
|
||||
If a specific guide does not exist for your platform, the [Linux
|
||||
guide](linux.mdx) is compatible with most platforms. For
|
||||
custom approaches, you can also read the [Machine ID Reference](../../../reference/machine-id/machine-id.mdx)
|
||||
custom approaches, you can also read the [Machine ID Reference](../../../reference/machine-workload-identity/machine-id/machine-id.mdx)
|
||||
and [Architecture](../../../reference/architecture/machine-id-architecture.mdx) to plan your deployment.
|
||||
|
||||
### Self-hosted infrastructure
|
||||
@@ -84,4 +84,4 @@ integration and continuous deployment platform
|
||||
| [Terraform Cloud](../../../zero-trust-access/infrastructure-as-code/terraform-provider/terraform-cloud.mdx) | Teleport Terraform Provider via Teleport's Terraform Registry | Terraform Cloud-signed identity document |
|
||||
|
||||
|
||||
[bound-keypair]: ../../../reference/machine-id/bound-keypair/getting-started.mdx
|
||||
[bound-keypair]: ../../../reference/machine-workload-identity/machine-id/bound-keypair/getting-started.mdx
|
||||
|
||||
@@ -133,6 +133,6 @@ Replace:
|
||||
|
||||
- Follow the [access guides](../access-guides/access-guides.mdx) to finish configuring `tbot` for
|
||||
your environment.
|
||||
- Read the [configuration reference](../../../reference/machine-id/configuration.mdx) to explore
|
||||
- Read the [configuration reference](../../../reference/machine-workload-identity/machine-id/configuration.mdx) to explore
|
||||
all the available configuration options.
|
||||
- [More information about `TELEPORT_ANONYMOUS_TELEMETRY`.](../../../reference/machine-id/telemetry.mdx)
|
||||
- [More information about `TELEPORT_ANONYMOUS_TELEMETRY`.](../../../reference/machine-workload-identity/machine-id/telemetry.mdx)
|
||||
|
||||
@@ -42,7 +42,7 @@ GitHub Actions run within a specific GitHub repository. In production, you may
|
||||
wish to further restrict these rules to ensure that access can only occur
|
||||
when CI is running against a specific branch. You can find a full list of the
|
||||
available rules on the
|
||||
[GitHub Actions reference page.](../../../reference/machine-id/github-actions.mdx)
|
||||
[GitHub Actions reference page.](../../../reference/machine-workload-identity/machine-id/github-actions.mdx)
|
||||
|
||||
Create a file named `bot-token.yaml`:
|
||||
|
||||
@@ -452,8 +452,8 @@ interact with.
|
||||
- [teleport-actions/auth-k8s](https://github.com/teleport-actions/auth-k8s)
|
||||
- [teleport-actions/auth-application](https://github.com/teleport-actions/auth-application)
|
||||
- For more information about the `github` join method, read the [GitHub Actions
|
||||
reference page](../../../reference/machine-id/github-actions.mdx)
|
||||
reference page](../../../reference/machine-workload-identity/machine-id/github-actions.mdx)
|
||||
- Find out more about GitHub Actions itself, read
|
||||
[their documentation](https://docs.github.com/en/actions).
|
||||
- [More information about `anonymous-telemetry`.](../../../reference/machine-id/telemetry.mdx)
|
||||
- [More information about `anonymous-telemetry`.](../../../reference/machine-workload-identity/machine-id/telemetry.mdx)
|
||||
|
||||
|
||||
@@ -80,7 +80,7 @@ spec:
|
||||
|
||||
You can find a full list of the token configuration options for GitLab joining
|
||||
on the
|
||||
[GitLab CI reference page.](../../../reference/machine-id/gitlab.mdx)
|
||||
[GitLab CI reference page.](../../../reference/machine-workload-identity/machine-id/gitlab.mdx)
|
||||
|
||||
Apply this to your Teleport cluster using `tctl`:
|
||||
|
||||
@@ -174,11 +174,11 @@ failure.
|
||||
## Further steps
|
||||
|
||||
- For more information about GitLab joining, read the
|
||||
[GitLab CI reference page.](../../../reference/machine-id/gitlab.mdx)
|
||||
[GitLab CI reference page.](../../../reference/machine-workload-identity/machine-id/gitlab.mdx)
|
||||
- For more information about GitLab itself, read
|
||||
[their documentation](https://docs.gitlab.com/ee/ci/).
|
||||
- Follow the [access guides](../access-guides/access-guides.mdx) to finish configuring `tbot` for
|
||||
your environment.
|
||||
- Read the [configuration reference](../../../reference/machine-id/configuration.mdx) to explore
|
||||
- Read the [configuration reference](../../../reference/machine-workload-identity/machine-id/configuration.mdx) to explore
|
||||
all the available configuration options.
|
||||
- [More information about `TELEPORT_ANONYMOUS_TELEMETRY`.](../../../reference/machine-id/telemetry.mdx)
|
||||
- [More information about `TELEPORT_ANONYMOUS_TELEMETRY`.](../../../reference/machine-workload-identity/machine-id/telemetry.mdx)
|
||||
|
||||
@@ -177,5 +177,5 @@ to a machine identity that can be rotated, audited, and controlled with access c
|
||||
|
||||
## Next steps
|
||||
|
||||
[More information about `TELEPORT_ANONYMOUS_TELEMETRY`.](../../../reference/machine-id/telemetry.mdx)
|
||||
[More information about `TELEPORT_ANONYMOUS_TELEMETRY`.](../../../reference/machine-workload-identity/machine-id/telemetry.mdx)
|
||||
|
||||
|
||||
@@ -154,7 +154,7 @@ Refer to your cloud provider documentation to enable this feature, including:
|
||||
|
||||
If your provider does not support this feature, consider using either [Static
|
||||
JWKS joining](./kubernetes.mdx) or an [alternative Teleport join
|
||||
method](../../../reference/join-methods.mdx) better suited to your cloud provider.
|
||||
method](../../../reference/deployment/join-methods.mdx) better suited to your cloud provider.
|
||||
</Admonition>
|
||||
|
||||
## Step 2/6. Prepare Kubernetes RBAC
|
||||
@@ -448,8 +448,8 @@ spec:
|
||||
|
||||
- Follow the [access guides](../access-guides/access-guides.mdx) to finish configuring `tbot` for
|
||||
your environment.
|
||||
- Read the [configuration reference](../../../reference/machine-id/configuration.mdx) to explore
|
||||
- Read the [configuration reference](../../../reference/machine-workload-identity/machine-id/configuration.mdx) to explore
|
||||
all the available configuration options.
|
||||
- [More information about `TELEPORT_ANONYMOUS_TELEMETRY`.](../../../reference/machine-id/telemetry.mdx)
|
||||
- [More information about `TELEPORT_ANONYMOUS_TELEMETRY`.](../../../reference/machine-workload-identity/machine-id/telemetry.mdx)
|
||||
|
||||
[said]: https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/#service-account-issuer-discovery
|
||||
|
||||
@@ -376,6 +376,6 @@ spec:
|
||||
|
||||
- Follow the [access guides](../access-guides/access-guides.mdx) to finish configuring `tbot` for
|
||||
your environment.
|
||||
- Read the [configuration reference](../../../reference/machine-id/configuration.mdx) to explore
|
||||
- Read the [configuration reference](../../../reference/machine-workload-identity/machine-id/configuration.mdx) to explore
|
||||
all the available configuration options.
|
||||
- [More information about `TELEPORT_ANONYMOUS_TELEMETRY`.](../../../reference/machine-id/telemetry.mdx)
|
||||
- [More information about `TELEPORT_ANONYMOUS_TELEMETRY`.](../../../reference/machine-workload-identity/machine-id/telemetry.mdx)
|
||||
|
||||
@@ -205,8 +205,8 @@ $ sudo chown teleport:teleport /var/lib/teleport/bot
|
||||
|
||||
- Follow the [access guides](../access-guides/access-guides.mdx) to finish configuring `tbot` for
|
||||
your environment.
|
||||
- Read the [TPM joining reference](../../../reference/join-methods.mdx#trusted-platform-module-tpm)
|
||||
- Read the [TPM joining reference](../../../reference/deployment/join-methods.mdx#trusted-platform-module-tpm)
|
||||
to learn more about `tpm`joining.
|
||||
- Read the [configuration reference](../../../reference/machine-id/configuration.mdx) to explore
|
||||
- Read the [configuration reference](../../../reference/machine-workload-identity/machine-id/configuration.mdx) to explore
|
||||
all the available configuration options.
|
||||
- [More information about `TELEPORT_ANONYMOUS_TELEMETRY`.](../../../reference/machine-id/telemetry.mdx)
|
||||
- [More information about `TELEPORT_ANONYMOUS_TELEMETRY`.](../../../reference/machine-workload-identity/machine-id/telemetry.mdx)
|
||||
|
||||
@@ -118,6 +118,6 @@ $ sudo chown teleport:teleport /var/lib/teleport/bot
|
||||
|
||||
- Follow the [access guides](../access-guides/access-guides.mdx) to finish configuring `tbot` for
|
||||
your environment.
|
||||
- Read the [configuration reference](../../../reference/machine-id/configuration.mdx) to explore
|
||||
- Read the [configuration reference](../../../reference/machine-workload-identity/machine-id/configuration.mdx) to explore
|
||||
all the available configuration options.
|
||||
- [More information about `TELEPORT_ANONYMOUS_TELEMETRY`.](../../../reference/machine-id/telemetry.mdx)
|
||||
- [More information about `TELEPORT_ANONYMOUS_TELEMETRY`.](../../../reference/machine-workload-identity/machine-id/telemetry.mdx)
|
||||
|
||||
@@ -110,7 +110,7 @@ advantage of this functionality.
|
||||
|
||||
Refer to the
|
||||
[CLI reference](../../reference/cli/tbot.mdx#tbot-start-kubernetesv2) and
|
||||
[config reference](../../reference/machine-id/configuration.mdx#kubernetesv2)
|
||||
[config reference](../../reference/machine-workload-identity/machine-id/configuration.mdx#kubernetesv2)
|
||||
for more information.
|
||||
|
||||
## Does `tbot` support Windows?
|
||||
|
||||
@@ -226,7 +226,7 @@ and controlled with access controls.
|
||||
configuring `tbot` in a production-ready way for your platform.
|
||||
- Check out the [access guides](access-guides/access-guides.mdx) to learn about configuring
|
||||
`tbot` for different use cases than SSH.
|
||||
- Read the [configuration reference](../../reference/machine-id/configuration.mdx) to explore
|
||||
- Read the [configuration reference](../../reference/machine-workload-identity/machine-id/configuration.mdx) to explore
|
||||
all the available configuration options.
|
||||
- [More information about `TELEPORT_ANONYMOUS_TELEMETRY`.](../../reference/machine-id/telemetry.mdx)
|
||||
- [More information about `TELEPORT_ANONYMOUS_TELEMETRY`.](../../reference/machine-workload-identity/machine-id/telemetry.mdx)
|
||||
|
||||
|
||||
@@ -113,7 +113,7 @@ Production-ready guidance on deploying Machine ID is broken out into two parts:
|
||||
them.
|
||||
- [Architecture](../../reference/architecture/machine-id-architecture.mdx): A technical deep-dive into how Machine ID
|
||||
works.
|
||||
- [Reference](../../reference/machine-id/machine-id.mdx): Complete documentation of available
|
||||
- [Reference](../../reference/machine-workload-identity/machine-id/machine-id.mdx): Complete documentation of available
|
||||
configuration options.
|
||||
- [Manifesto](./manifesto.mdx): Our vision for Machine Identity and the
|
||||
direction Machine ID and Workload ID are heading in.
|
||||
|
||||
@@ -86,5 +86,5 @@ API endpoints and full audit visibility.
|
||||
|
||||
- [Architecture](../reference/architecture/machine-id-architecture.mdx): A technical deep-dive into how Machine ID
|
||||
works.
|
||||
- [Reference](../reference/machine-id/machine-id.mdx): Complete documentation of available
|
||||
- [Reference](../reference/machine-workload-identity/machine-id/machine-id.mdx): Complete documentation of available
|
||||
configuration options.
|
||||
|
||||
@@ -490,5 +490,5 @@ Workload Identity.
|
||||
Teleport Workload Identity.
|
||||
- [Best Practices](./best-practices.mdx): Best practices for using Workload
|
||||
Identity in Production.
|
||||
- Read the [configuration reference](../../reference/machine-id/configuration.mdx) to explore
|
||||
- Read the [configuration reference](../../reference/machine-workload-identity/machine-id/configuration.mdx) to explore
|
||||
all the available configuration options.
|
||||
|
||||
@@ -349,5 +349,5 @@ The official AWS documentation for Roles Anywhere.
|
||||
Workload Identity.
|
||||
- [Best Practices](./best-practices.mdx): Best practices for using Workload
|
||||
Identity in Production.
|
||||
- Read the [configuration reference](../../reference/machine-id/configuration.mdx) to explore
|
||||
- Read the [configuration reference](../../reference/machine-workload-identity/machine-id/configuration.mdx) to explore
|
||||
all the available configuration options.
|
||||
|
||||
+1
-1
@@ -343,5 +343,5 @@ Workload Identity.
|
||||
Teleport Workload Identity.
|
||||
- [Best Practices](./best-practices.mdx): Best practices for using Workload
|
||||
Identity in Production.
|
||||
- Read the [configuration reference](../../reference/machine-id/configuration.mdx) to explore
|
||||
- Read the [configuration reference](../../reference/machine-workload-identity/machine-id/configuration.mdx) to explore
|
||||
all the available configuration options.
|
||||
|
||||
@@ -103,7 +103,7 @@ Workload API.
|
||||
Workload Identity.
|
||||
- [Best Practices](./best-practices.mdx): Best practices for using Workload
|
||||
Identity in Production.
|
||||
- Read the [configuration reference](../../reference/machine-id/configuration.mdx) to explore
|
||||
- Read the [configuration reference](../../reference/machine-workload-identity/machine-id/configuration.mdx) to explore
|
||||
all the available configuration options.
|
||||
- Read the [SPIFFE Federation Specification](https://github.com/spiffe/spiffe/blob/main/standards/SPIFFE_Federation.md)
|
||||
to understand the technical details of SPIFFE Federation.
|
||||
|
||||
+1
-1
@@ -417,5 +417,5 @@ Workload Identity.
|
||||
Teleport Workload Identity.
|
||||
- [Best Practices](./best-practices.mdx): Best practices for using Workload
|
||||
Identity in Production.
|
||||
- Read the [configuration reference](../../reference/machine-id/configuration.mdx) to explore
|
||||
- Read the [configuration reference](../../reference/machine-workload-identity/machine-id/configuration.mdx) to explore
|
||||
all the available configuration options.
|
||||
|
||||
@@ -251,7 +251,7 @@ integrating SPIFFE with your workloads.
|
||||
Workload Identity.
|
||||
- [Best Practices](./best-practices.mdx): Best practices for using Workload
|
||||
Identity in Production.
|
||||
- Read the [Workload Identity reference](../../reference/workload-identity/workload-identity-resource.mdx)
|
||||
- Read the [Workload Identity reference](../../reference/machine-workload-identity/workload-identity/workload-identity-resource.mdx)
|
||||
to explore the configuration of the Workload Identity resource.
|
||||
- Read the [configuration reference](../../reference/machine-id/configuration.mdx) to explore
|
||||
- Read the [configuration reference](../../reference/machine-workload-identity/machine-id/configuration.mdx) to explore
|
||||
all the available configuration options for `tbot`.
|
||||
|
||||
@@ -102,8 +102,8 @@ Learn more about Teleport Workload Identity:
|
||||
- [Federation](./federation.mdx): Learn about using Federation to allow workloads to trust workloads from other trust domains.
|
||||
- [JWT SVIDs](./jwt-svids.mdx): Learn about the short-lived JWTs issued by Workload Identity.
|
||||
- [Best Practices](./best-practices.mdx): Best practices for using Workload Identity in Production.
|
||||
- [Workload Identity Resource](../../reference/workload-identity/workload-identity-resource.mdx): The full reference for the Workload Identity resource.
|
||||
- [Workload Identity API and Workload Attestation](../../reference/workload-identity/workload-identity-api-and-workload-attestation.mdx): To learn more about the Workload Identity API and Workload Attestation.
|
||||
- [Workload Identity Resource](../../reference/machine-workload-identity/workload-identity/workload-identity-resource.mdx): The full reference for the Workload Identity resource.
|
||||
- [Workload Identity API and Workload Attestation](../../reference/machine-workload-identity/workload-identity/workload-identity-api-and-workload-attestation.mdx): To learn more about the Workload Identity API and Workload Attestation.
|
||||
|
||||
Learn how to configure Teleport Workload Identity for specific use-cases:
|
||||
|
||||
|
||||
@@ -68,5 +68,5 @@ platforms:
|
||||
Workload Identity.
|
||||
- [Best Practices](./best-practices.mdx): Best practices for using Workload
|
||||
Identity in Production.
|
||||
- Read the [configuration reference](../../reference/machine-id/configuration.mdx) to explore
|
||||
- Read the [configuration reference](../../reference/machine-workload-identity/machine-id/configuration.mdx) to explore
|
||||
all the available configuration options.
|
||||
|
||||
@@ -90,5 +90,5 @@ Workload Identity.
|
||||
Workload Identity.
|
||||
- [Best Practices](./best-practices.mdx): Best practices for using Workload
|
||||
Identity in Production.
|
||||
- Read the [configuration reference](../../reference/machine-id/configuration.mdx) to explore
|
||||
- Read the [configuration reference](../../reference/machine-workload-identity/machine-id/configuration.mdx) to explore
|
||||
all the available configuration options.
|
||||
|
||||
@@ -25,5 +25,5 @@ issues flexible short-lived identities to workloads in your infrastructure.
|
||||
- [Best Practices for Teleport Workload Identity](./best-practices.mdx): Answers common questions and describes best practices for using Teleport Workload Identity in production.
|
||||
- [JWT SVIDs](./jwt-svids.mdx): An overview of the JWT SVIDs issued by Teleport Workload Identity
|
||||
- [SPIFFE Federation](./federation.mdx): An overview of the Teleport Workload Identity SPIFFE Federation feature.
|
||||
- [Workload Attestation](../../reference/workload-identity/workload-identity-api-and-workload-attestation.mdx): An overview of the Teleport Workload Identity Workload Attestation feature.
|
||||
- [Workload Identity Resource](../../reference/workload-identity/workload-identity-resource.mdx): The full reference for the Workload Identity resource.
|
||||
- [Workload Attestation](../../reference/machine-workload-identity/workload-identity/workload-identity-api-and-workload-attestation.mdx): An overview of the Teleport Workload Identity Workload Attestation feature.
|
||||
- [Workload Identity Resource](../../reference/machine-workload-identity/workload-identity/workload-identity-resource.mdx): The full reference for the Workload Identity resource.
|
||||
|
||||
@@ -16,7 +16,7 @@ more secure and reliable.
|
||||
## Eliminate secrets from your applications
|
||||
|
||||
Teleport issues special credentials to applications in the form of x.509 certificates or JWTs, after
|
||||
verifying their identity (to get started, see [Introduction to Workload Identity](/machine-workload-identity/workload-identity/introduction.mdx).
|
||||
verifying their identity (to get started, see [Introduction to Workload Identity](workload-identity/introduction.mdx).
|
||||
These credentials are automatically rotated every 20 minutes by default. They contain a URI that
|
||||
uniquely identifies the application. Applications using the credentials automatically gain mTLS,
|
||||
and can verify that a request or response not only comes from a trusted certificate, but from a specific trusted application.
|
||||
@@ -31,5 +31,5 @@ with a wide ecosystem of libraries and SDKs.
|
||||
|
||||
### Further reading
|
||||
|
||||
- [Best Practices for Teleport Workload Identity](/machine-workload-identity/workload-identity/best-practices.mdx): Learn how Teleport verifies applications and issues credentials
|
||||
- [Introduction to SPIFFE:](/machine-workload-identity/workload-identity/spiffe.mdx) Learn about the open-source standard for workload identities and federation
|
||||
- [Best Practices for Teleport Workload Identity](./workload-identity/best-practices.mdx): Learn how Teleport verifies applications and issues credentials
|
||||
- [Introduction to SPIFFE:](./workload-identity/spiffe.mdx) Learn about the open-source standard for workload identities and federation
|
||||
|
||||
@@ -141,7 +141,7 @@ Teleport Auth Service backend. Since your original Teleport cluster uses a
|
||||
separate Auth Service backend from your new cluster, you must retrieve the
|
||||
resources on the first backend, then re-apply them against the second backend.
|
||||
|
||||
Review the [dynamic resources](reference/resources.mdx) list to see if any
|
||||
Review the [dynamic resources](reference/infrastructure-as-code/resources.mdx) list to see if any
|
||||
other resources need to be migrated. Some common dynamic resources includes:
|
||||
|
||||
- `windows_desktop`
|
||||
@@ -211,7 +211,7 @@ To migrate Teleport Agents:
|
||||
|
||||
1. For each Agent and Machine ID Bot, obtain a valid join token. We recommend
|
||||
using a [delegated join
|
||||
method](reference/join-methods.mdx).
|
||||
method](reference/deployment/join-methods.mdx).
|
||||
|
||||
1. If using ephemeral tokens, ensure you specify the appropriate token type to
|
||||
match the Teleport services. Token types can include `node`, `app`, `kube`,
|
||||
|
||||
@@ -1,8 +1,17 @@
|
||||
---
|
||||
title: Access Controls References
|
||||
sidebar_label: Access Controls
|
||||
description: Contains guides to configuring authentication and authorization in Teleport.
|
||||
tags:
|
||||
- zero-trust
|
||||
---
|
||||
|
||||
The Teleport access controls reference guides provide comprehensive information
|
||||
on configuring permissions for users to connect to infrastructure resources or
|
||||
manage your Teleport cluster. For example, you can find lists of configuration
|
||||
fields for Teleport roles, Access Lists, and Access Monitoring Rules.
|
||||
|
||||
If you are new to Teleport RBAC, read [Get Started with Role-Based Access
|
||||
Control](../../zero-trust-access/rbac-get-started/rbac-get-started.mdx).
|
||||
|
||||
<DocCardList />
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Access List Reference
|
||||
sidebar_label: Access Lists
|
||||
description: An explanation and overview of Access Lists in Teleport.
|
||||
tags:
|
||||
- conceptual
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Access Monitoring Rule Reference
|
||||
sidebar_label: Access Monitoring Rules
|
||||
description: An explanation and overview of Access Monitoring Rules.
|
||||
tags:
|
||||
- reference
|
||||
@@ -242,7 +243,7 @@ condition: access_request.spec.resource_labels_intersection["env"].contains("dev
|
||||
condition: access_request.spec.resource_labels_union["env"].contains("prod")
|
||||
```
|
||||
|
||||
See [Predicate Language](../predicate-language.mdx) for more details.
|
||||
See [Predicate Language](predicate-language.mdx) for more details.
|
||||
|
||||
## SSO users and IdP attributes
|
||||
|
||||
@@ -317,5 +318,5 @@ resource "teleport_access_monitoring_rule" "example_rule" {
|
||||
}
|
||||
```
|
||||
|
||||
See [Terraform Provider](../terraform-provider/resources/access_monitoring_rule.mdx)
|
||||
See [Terraform Provider](../infrastructure-as-code/terraform-provider/resources/access_monitoring_rule.mdx)
|
||||
for more details.
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Login Rules Reference
|
||||
sidebar_label: Login Rules
|
||||
description: Reference documentation for Login Rules
|
||||
tocDepth: 3
|
||||
tags:
|
||||
|
||||
+5
-5
@@ -20,8 +20,8 @@ The predicate language uses a slightly different syntax depending on whether it
|
||||
Some fields in Teleport's role resources use the predicate language to define
|
||||
the scope of a role's permissions:
|
||||
|
||||
- [Dynamic Impersonation](../zero-trust-access/authentication/impersonation.mdx)
|
||||
- [RBAC for sessions](access-controls/roles.mdx)
|
||||
- [Dynamic Impersonation](../../zero-trust-access/authentication/impersonation.mdx)
|
||||
- [RBAC for sessions](roles.mdx)
|
||||
|
||||
When used in role resources, the predicate language supports the following operators:
|
||||
|
||||
@@ -42,7 +42,7 @@ The language also supports the following functions:
|
||||
|
||||
## Resource filtering
|
||||
|
||||
Both the [`tsh`](cli/tsh.mdx) and [`tctl`](cli/tctl.mdx) CLI tools allow you to filter nodes,
|
||||
Both the [`tsh`](../cli/tsh.mdx) and [`tctl`](../cli/tctl.mdx) CLI tools allow you to filter nodes,
|
||||
applications, databases, and Kubernetes resources using the `--query` flag. The `--query` flag allows you to
|
||||
perform more sophisticated searches using the predicate language.
|
||||
|
||||
@@ -75,14 +75,14 @@ The language also supports the following functions:
|
||||
| `split(labels["foo"], ",")` | converts a delimited string into a list |
|
||||
| `contains(split(labels["foo"], ","), "bar")` | determines if a value exists in a list |
|
||||
|
||||
See some [examples](cli/cli.mdx) of the different ways you can filter resources.
|
||||
See some [examples](../cli/cli.mdx) of the different ways you can filter resources.
|
||||
|
||||
## Label expressions
|
||||
|
||||
Label expressions can be used in Teleport roles to define access to resources
|
||||
with custom logic.
|
||||
Check out the Access Controls
|
||||
[reference page](access-controls/roles.mdx)
|
||||
[reference page](roles.mdx)
|
||||
for an overview of label expressions and where they can be used.
|
||||
|
||||
Label expressions support a predicate language with the following fields
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Access Controls Reference
|
||||
title: Teleport Role Reference
|
||||
sidebar_label: Roles
|
||||
description: Explains the configuration settings that you can include in a Teleport role, which enables you to apply access controls for your infrastructure.
|
||||
tocDepth: 3
|
||||
tags:
|
||||
@@ -70,7 +71,7 @@ user:
|
||||
| `request_prompt` | Prompt for the Access Request "reason" field | |
|
||||
| `max_connections` | Enterprise-only limit on how many concurrent sessions can be started via Teleport | The lowest value takes precedence. |
|
||||
| `max_kubernetes_connections` | Defines the maximum number of concurrent Kubernetes sessions per user | |
|
||||
| `record_session` |Defines the [Session recording mode](../monitoring/audit.mdx).|The strictest value takes precedence.|
|
||||
| `record_session` |Defines the [Session recording mode](../deployment/monitoring/audit.mdx).|The strictest value takes precedence.|
|
||||
| `desktop_clipboard` | Allow clipboard sharing for desktop sessions | Logical "AND" i.e. evaluates to "yes" if all roles enable clipboard sharing |
|
||||
| `desktop_directory_sharing` | Allows sharing local workstation directory to remote desktop | Logical "AND" i.e. evaluates to "yes" if all roles enable directory sharing |
|
||||
| `pin_source_ip` | Enable source IP pinning for SSH certificates. | Logical "OR" i.e. evaluates to "yes" if at least one role requires session termination |
|
||||
@@ -250,7 +251,7 @@ conditions:
|
||||
- `workload_identity_labels_expression`
|
||||
|
||||
Check out our
|
||||
[predicate language](../predicate-language.mdx)
|
||||
[predicate language](predicate-language.mdx)
|
||||
guide for a more in depth explanation of the language.
|
||||
|
||||
Typically you will only want to use one of `<kind>_labels` or
|
||||
@@ -755,7 +756,7 @@ Labels for resources enrolled with Teleport:
|
||||
|`kubernetes_labels`|[Kubernetes clusters](../../enroll-resources/kubernetes-access/controls.mdx)|
|
||||
|`node_labels`|[SSH Servers](../../enroll-resources/server-access/server-access.mdx)|
|
||||
|`windows_desktop_labels`|[Windows desktops](../../enroll-resources/server-access/server-access.mdx)|
|
||||
|`workload_identity_labels`|[Workload Identities](../workload-identity/workload-identity-resource.mdx)|
|
||||
|`workload_identity_labels`|[Workload Identities](../machine-workload-identity/workload-identity/workload-identity-resource.mdx)|
|
||||
|
||||
Principals a user can assume on infrastructure resources:
|
||||
- `aws_role_arns`
|
||||
@@ -813,7 +814,7 @@ sign-on provider.
|
||||
The `internal` trait namespace includes only the exact internal trait names
|
||||
included in the above table.
|
||||
For local Teleport users, these traits can be set in the `spec.traits` field of the
|
||||
[user resource](../resources.mdx#user).
|
||||
[user resource](../infrastructure-as-code/resources.mdx#user).
|
||||
These trait names can also be set for SSO users if they are included in an
|
||||
attribute or claim from your IdP.
|
||||
|
||||
@@ -845,7 +846,7 @@ included in the `spec.allow.logins` field of roles the user holds in the root cl
|
||||
#### Referring to external traits in Teleport roles
|
||||
|
||||
For local Teleport users, the `external` trait namespace includes all values
|
||||
from the `spec.traits` field of the [user resource](../resources.mdx#user).
|
||||
from the `spec.traits` field of the [user resource](../infrastructure-as-code/resources.mdx#user).
|
||||
This includes any custom trait names, as well as names matching the `internal`
|
||||
traits listed above.
|
||||
For example, `{{internal.logins}}` and `{{external.logins}}` are both valid ways
|
||||
@@ -954,5 +955,5 @@ within this guide:
|
||||
| `user.metadata.name` | The user's name |
|
||||
|
||||
Read the [predicate
|
||||
language](../predicate-language.mdx)
|
||||
language](predicate-language.mdx)
|
||||
guide for a more in depth explanation of the language.
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: SAML Identity Provider Reference
|
||||
sidebar_label: SAML Identity Provider
|
||||
description: Reference documentation for the SAML identity provider
|
||||
tags:
|
||||
- conceptual
|
||||
|
||||
+4
-4
@@ -26,7 +26,7 @@ one-time passwords.
|
||||
|
||||
Local user login can be disabled via `cluster_auth_preference` or `teleport.yaml`.
|
||||
Disabling local authentication is required for [FIPS/FedRAMP compliance
|
||||
](../zero-trust-access/compliance-frameworks/fedramp.mdx).
|
||||
](../../zero-trust-access/compliance-frameworks/fedramp.mdx).
|
||||
|
||||
### Special case: Bots
|
||||
|
||||
@@ -36,10 +36,10 @@ Teleport by a user and a role resource and can be created via the
|
||||
`tctl bots add` command.
|
||||
|
||||
Unlike human users, who use a password, MFA, or SSO, bot users join
|
||||
the cluster as Teleport services using [a join method](./join-methods.mdx). They
|
||||
the cluster as Teleport services using [a join method](../deployment/join-methods.mdx). They
|
||||
can still join even if local auth is disabled.
|
||||
|
||||
See the [Machine ID introduction](../machine-workload-identity/machine-id/introduction.mdx) for more information.
|
||||
See the [Machine ID introduction](../../machine-workload-identity/machine-id/introduction.mdx) for more information.
|
||||
|
||||
## SSO users
|
||||
|
||||
@@ -71,7 +71,7 @@ and automatically expire. The expiry is dynamically computed based on the IdP
|
||||
answer validity, the max session duration allowed by the user roles, and cannot
|
||||
exceed 30 hours. Those users cannot be edited via `tctl`, only deleted.
|
||||
|
||||
See the [SSO setup guides](../zero-trust-access/sso/sso.mdx) to learn how to setup an
|
||||
See the [SSO setup guides](../../zero-trust-access/sso/sso.mdx) to learn how to setup an
|
||||
authentication connector and allow user to log in via an IdP.
|
||||
|
||||
### Synced users
|
||||
@@ -9,6 +9,6 @@ tags:
|
||||
Use these reference guides to configure and run Teleport Agent services. For a
|
||||
comprehensive list of options you can configure when running the `teleport`
|
||||
binary, including all options for Agent services, consult the [Teleport
|
||||
Configuration Reference](../config.mdx).
|
||||
Configuration Reference](../deployment/config.mdx).
|
||||
|
||||
<DocCardList />
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Application Access Reference Documentation
|
||||
sidebar_label: Application Access
|
||||
description: Configuration and CLI reference documentation for Teleport application access.
|
||||
tags:
|
||||
- reference
|
||||
|
||||
+1
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Auto-Discovery Reference
|
||||
sidebar_label: Auto-Discovery
|
||||
description: Configuration reference for the Teleport Discovery Service.
|
||||
tags:
|
||||
- zero-trust
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Discovery Service AWS IAM Reference
|
||||
sidebar_label: Discovery Service AWS IAM
|
||||
description: AWS IAM permissions for the Teleport Discovery Service.
|
||||
tocDepth: 3
|
||||
tags:
|
||||
|
||||
+2
-1
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Kubernetes Application Discovery Reference
|
||||
sidebar_label: Kubernetes Application Discovery
|
||||
description: This guide is a comprehensive reference of configuration options for automatically enrolling Kubernetes applications with Teleport.
|
||||
tags:
|
||||
- reference
|
||||
@@ -71,7 +72,7 @@ app_service:
|
||||
|
||||
Label `teleport.dev/kubernetes-cluster` should match value of `discovery_group` field in the Discovery Service config.
|
||||
|
||||
For more information you can take a look at [`discovery_service`](../../config.mdx) and [`app_service`](../../config.mdx) configuration references.
|
||||
For more information you can take a look at [`discovery_service`](../../deployment/config.mdx) and [`app_service`](../../deployment/config.mdx) configuration references.
|
||||
|
||||
## Annotations
|
||||
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Database Access Audit Events Reference
|
||||
sidebar_label: Database Access Audit Events
|
||||
description: Audit events reference for Teleport database access.
|
||||
tags:
|
||||
- reference
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Database Access AWS IAM Reference
|
||||
sidebar_label: Database Access AWS IAM
|
||||
description: AWS IAM policies for Teleport database access.
|
||||
tags:
|
||||
- reference
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Database Access CLI Reference
|
||||
sidebar_label: Database Access CLI
|
||||
description: CLI reference for Teleport database access.
|
||||
tags:
|
||||
- reference
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Database Access Configuration Reference
|
||||
sidebar_label: Database Access Configuration
|
||||
description: Configuration reference for Teleport database access.
|
||||
tags:
|
||||
- reference
|
||||
|
||||
+1
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Database Access Reference
|
||||
sidebar_label: Database Access
|
||||
description: Configuration and CLI reference for the Teleport Database Service.
|
||||
tags:
|
||||
- zero-trust
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Database Labels Reference
|
||||
sidebar_label: Database Labels
|
||||
description: Database labels reference for Teleport database access.
|
||||
tags:
|
||||
- reference
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Desktop Access Audit Events Reference
|
||||
sidebar_label: Desktop Access Audit Events
|
||||
description: Audit events reference for Teleport desktop access.
|
||||
tags:
|
||||
- reference
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user