diff --git a/docs/pages/connect-your-client/includes/connect-my-computer-prerequisites.mdx b/docs/pages/connect-your-client/includes/connect-my-computer-prerequisites.mdx index 68a9d3bac70..072ee8e0f24 100644 --- a/docs/pages/connect-your-client/includes/connect-my-computer-prerequisites.mdx +++ b/docs/pages/connect-your-client/includes/connect-my-computer-prerequisites.mdx @@ -1,5 +1,5 @@ - A macOS or Linux device. -- Teleport Connect v14.1+, on the same major version or one version behind the Teleport Proxy +- Teleport Connect, on the same major version or one version behind the Teleport Proxy Service version. See [version compatibility](../../upcoming-releases.mdx#teleport). - A local Teleport user: you must authenticate using credentials or passwordless login, and not with SSO. diff --git a/docs/pages/enroll-resources/database-access/enrollment/aws/aws-cross-account.mdx b/docs/pages/enroll-resources/database-access/enrollment/aws/aws-cross-account.mdx index fa72de4e556..bf3d3fc1c20 100644 --- a/docs/pages/enroll-resources/database-access/enrollment/aws/aws-cross-account.mdx +++ b/docs/pages/enroll-resources/database-access/enrollment/aws/aws-cross-account.mdx @@ -14,8 +14,6 @@ You can deploy the Teleport Database Service with AWS IAM credentials in one AWS account and use an AWS IAM role to grant Teleport access to databases in another AWS account. -AWS cross-account database access is available starting from Teleport `13.0`. - When the Teleport Database Service needs to discover, configure, or retrieve short-lived authentication tokens for AWS databases, it uses credentials for an AWS IAM identity to make requests to the AWS API. diff --git a/docs/pages/enroll-resources/database-access/enrollment/azure/azure-postgres-mysql.mdx b/docs/pages/enroll-resources/database-access/enrollment/azure/azure-postgres-mysql.mdx index c80d19e1e69..1b418961b2e 100644 --- a/docs/pages/enroll-resources/database-access/enrollment/azure/azure-postgres-mysql.mdx +++ b/docs/pages/enroll-resources/database-access/enrollment/azure/azure-postgres-mysql.mdx @@ -11,9 +11,6 @@ tags: (!docs/pages/includes/database-access/db-introduction.mdx dbType="Azure PostgreSQL or MySQL" dbConfigure="with Microsoft Entra ID-based authentication"!) -Database auto-discovery for Azure PostgreSQL/MySQL flexible servers is available starting from -Teleport `12.0`. - ## How it works The Teleport Database Service proxies traffic between Teleport users and Azure diff --git a/docs/pages/reference/architecture/tls-routing.mdx b/docs/pages/reference/architecture/tls-routing.mdx index 8452e11d84d..5bb7c0cc1c8 100644 --- a/docs/pages/reference/architecture/tls-routing.mdx +++ b/docs/pages/reference/architecture/tls-routing.mdx @@ -18,9 +18,6 @@ To implement TLS routing, Teleport uses SNI ([Server Name Indication](https://en and ALPN ([Application-Level Protocol Negotiation](https://en.wikipedia.org/wiki/Application-Layer_Protocol_Negotiation)) TLS extensions. -Support for TLS Routing behind layer 7 (HTTP/HTTPS) load balancers and reverse -proxies is available starting from Teleport `13.0`. - ## How it works The Teleport Proxy Service listens for all client connections on its `web_listen_addr` by default: diff --git a/docs/pages/reference/deployment/backends.mdx b/docs/pages/reference/deployment/backends.mdx index bb73fbed2b1..6f7dadf3bda 100644 --- a/docs/pages/reference/deployment/backends.mdx +++ b/docs/pages/reference/deployment/backends.mdx @@ -302,9 +302,6 @@ tctl get --format=json | awk '{ total += length($0) } EN ## PostgreSQL -PostgreSQL cluster state and audit log storage is available starting from -Teleport `13.3`. - Teleport can use [PostgreSQL](https://www.postgresql.org/) as a storage backend to achieve high availability. You must take steps to protect access to PostgreSQL in this configuration because that is where Teleport secrets like @@ -1080,8 +1077,6 @@ Config option priority is applied in the following order: ## Athena -The Athena audit log backend is available starting from Teleport v14.0. - If you are running Teleport on AWS, you can use an [Athena](https://aws.amazon.com/athena/)-based audit log system that manages [Parquet files](https://parquet.apache.org/) stored on diff --git a/docs/pages/zero-trust-access/management/external-audit-storage.mdx b/docs/pages/zero-trust-access/management/external-audit-storage.mdx index e17340b8da3..837599c7814 100644 --- a/docs/pages/zero-trust-access/management/external-audit-storage.mdx +++ b/docs/pages/zero-trust-access/management/external-audit-storage.mdx @@ -23,10 +23,7 @@ audit events right where they are stored. External Audit Storage is based on Teleport's [Athena](../../reference/deployment/backends.mdx#athena) backend for audit events and the -[S3](../../reference/deployment/backends.mdx#s3-session-recordings) backend for session recordings. It is only -available on Teleport Enterprise Cloud clusters running Teleport v14.2.1 or -above. - +[S3](../../reference/deployment/backends.mdx#s3-session-recordings) backend for session recordings. ## Prerequisites