gravitational · stevenGravy · May 7, 2023 · May 6, 2023 · May 6, 2023 · May 6, 2023
diff --git a/docs/img/enterprise/license.png b/docs/img/enterprise/license.png
diff --git a/docs/pages/access-controls/access-request-plugins/ssh-approval-jira.mdx b/docs/pages/access-controls/access-request-plugins/ssh-approval-jira.mdx
@@ -13,7 +13,6 @@ Jira tickets.
 
 - Jira Server or Jira Cloud installation with an owner privileges, specifically
   to set up webhooks, issue types, and workflows
-
 - (!docs/pages/includes/tctl.mdx!)
 
 ## Step 1/6. Create a user and role for access

diff --git a/docs/pages/access-controls/compliance-frameworks/fedramp.mdx b/docs/pages/access-controls/compliance-frameworks/fedramp.mdx
@@ -25,14 +25,11 @@ government agencies.
 | [IA-03 Device Identification and Authentication]((=fedramp.control_url=)IA-3) | Teleport requires valid x509 or SSH certificates issued by a Teleport Certificate Authority (CA) to establish a network connection for device-to-device network connection between Teleport components. |
 | [SC-12 Cryptographic Key Establish and Management]((=fedramp.control_url=)SC-12) | Teleport initializes cryptographic keys that act as a Certificate Authority (CA) to further issue x509 and SSH certificates. SSH and x509 user certificates that are issued are signed by the CA and are (by default) short-lived. SSH host certificates are also signed by the CA and rotated automatically (a manual force rotation can also be performed).<br/>Teleport Enterprise builds against a FIPS 140-2 compliant library (BoringCrypto) is available. <br/>In addition, when Teleport Enterprise is in FedRAMP/FIPS 140-2 mode, Teleport will only start and use FIPS 140-2 compliant cryptography. |
 
-Enterprise customers can download the custom FIPS package from the [Dashboard](https://dashboard.gravitational.com/web/login).  Look for `Linux 64-bit (FedRAMP/FIPS)`. RPM and DEB packages are also available.
-
 ## Setup
 
-Customers can follow our [Enterprise Getting Started
-Guide](../../choose-an-edition/teleport-enterprise/getting-started.mdx) for
-instructions on how to set up Teleport Enterprise. You'll need to start with the
-Teleport Enterprise FIPS binary.
+Sign in to your [Teleport account](https://teleport.sh) to download a FIPS binary
+for Teleport Enterprise. Look for `Linux 64-bit (FedRAMP/FIPS)`. RPM and DEB
+packages are also available.
 
 After downloading the binary tarball, run:
 

diff --git a/docs/pages/application-access/guides/connecting-apps.mdx b/docs/pages/application-access/guides/connecting-apps.mdx
@@ -103,7 +103,7 @@ e.g. `grafana.teleport.example.com`. You can also override `public_addr` e.g
 `grafana.acme.com` if you configure the appropriate DNS entry to point to the
 Teleport proxy server.
 
-## Start application service with a config file
+## Start Application Service with a config file
 
 Example `teleport.yaml` configuration:
 

diff --git a/docs/pages/choose-an-edition/teleport-enterprise/getting-started.mdx b/docs/pages/choose-an-edition/teleport-enterprise/getting-started.mdx
@@ -454,7 +454,7 @@ Usually the error will be reported there. Common reasons for failure are:
 ## Getting Help
 
 If something is not working, please reach out to us by creating a ticket in your
-[customer portal](https://dashboard.gravitational.com/web/login).  Customers who
+[Teleport account](https://teleport.sh).  Customers who
 have purchased the premium support package can also ping us through your Slack
 channel.
 
diff --git a/docs/pages/choose-an-edition/teleport-enterprise/introduction.mdx b/docs/pages/choose-an-edition/teleport-enterprise/introduction.mdx
@@ -67,7 +67,7 @@ See the [SSO](../../access-controls/sso.mdx) chapter for more details.
 
 With Teleport we have built the foundation to meet FedRAMP requirements for the purposes of accessing infrastructure. This includes support for [FIPS 140-2](https://en.wikipedia.org/wiki/FIPS\_140-2), also known as the Federal Information Processing Standard, which is the US government approved standard for cryptographic modules.
 
-Enterprise customers can download the custom FIPS package from the [Gravitational Dashboard](https://dashboard.gravitational.com/web/).
+Enterprise customers can download the custom FIPS package from their [Teleport account](https://teleport.sh).
 Look for `Linux 64-bit (FedRAMP/FIPS)`.
 
 Using `teleport start --fips` Teleport will start in FIPS mode, Teleport will

diff --git a/docs/pages/choose-an-edition/teleport-enterprise/license.mdx b/docs/pages/choose-an-edition/teleport-enterprise/license.mdx
@@ -17,10 +17,13 @@ your license file.
 
 ### Download your license file
 
-To obtain your license file, visit the [Teleport customer
-portal](https://dashboard.gravitational.com/web/login) and log in. Click
-"DOWNLOAD LICENSE KEY". You will see your current Teleport Enterprise account
-permissions and the option to download your license file:
+Teleport provides a dedicated account site where you can download your license and
+enterprise binaries, and maintain users' access to your license. 
+
+To obtain your license file navigate to your Teleport account site and log in.
+You can start at [teleport.sh](https://teleport.sh) and enter your
+Teleport account name (e.g. my-license). After logging in
+you will see the "DOWNLOAD LICENSE KEY" button to download the license file.
 
 ![License File modal](../../../img/enterprise/license.png)
 

diff --git a/docs/pages/database-access/getting-started.mdx b/docs/pages/database-access/getting-started.mdx
@@ -34,7 +34,6 @@ release.
   and attach IAM policies.
 - A host, e.g., an EC2 instance, where you will run the Teleport Database
   Service.
-
 - (!docs/pages/includes/tctl.mdx!)
 
 ## Step 1/4. Set up Aurora

diff --git a/docs/pages/database-access/guides/azure-postgres-mysql.mdx b/docs/pages/database-access/guides/azure-postgres-mysql.mdx
@@ -223,7 +223,7 @@ and replace the subscription in "assignableScopes" with your own subscription id
 ![Create JSON role](../../../img/database-access/guides/azure/create-role-from-json@2x.png)
 </Figure>
 
-### Create a role assignment for the Teleport Database Service principal.
+### Create a role assignment for the Teleport Database Service principal
 
 (!docs/pages/includes/database-access/azure-assign-service-principal.mdx!)
 

diff --git a/docs/pages/database-access/guides/redis-aws.mdx b/docs/pages/database-access/guides/redis-aws.mdx
@@ -26,7 +26,6 @@ This guide will help you to:
 - `redis-cli` version `6.2` or newer installed and added to your system's `PATH` environment variable.
 - A host, e.g., an EC2 instance, where you will run the Teleport Database
   Service.
-
 - (!docs/pages/includes/tctl.mdx!)
 
 ## Step 1/6. Create a Teleport user

diff --git a/docs/pages/deploy-a-cluster/deployments/aws-terraform.mdx b/docs/pages/deploy-a-cluster/deployments/aws-terraform.mdx
@@ -185,10 +185,9 @@ EC2 instances. Do not use a keypair that you do not have access to.
 
 ### license_path
 
-Setting `export TF_VAR_license_path="/home/user/teleport-license.pem"`
+(!docs/pages/includes//enterprise/obtainlicense.mdx!)
 
-The full local path to your Teleport license file, which customers can download from
-[the Teleport customer dashboard](https://dashboard.gravitational.com/).
+Set `export TF_VAR_license_path="/home/user/teleport-license.pem"`
 
 This license will be uploaded to AWS SSM and automatically downloaded to Teleport auth nodes in order to enable
 Teleport Enterprise/Pro functionality.

diff --git a/docs/pages/deploy-a-cluster/deployments/gcp.mdx b/docs/pages/deploy-a-cluster/deployments/gcp.mdx
@@ -227,8 +227,8 @@ We recommend configuring Teleport as per the below steps:
 <Tabs>
 	<TabItem label="Open Source">
 **1. Configure Teleport Auth Server** using the below example `teleport.yaml`, and start it
-using [systemd](https://raw.githubusercontent.com/gravitational/teleport/master/examples/systemd/teleport.service)
-or use DEB/RPM packages available from our [Downloads Page](https://goteleport.com/download/).
+using [systemd](../../management/admin/daemon.mdx). The DEB/RPM installations will
+automatically include the `systemd` configuration.
 
 ```yaml
 #
@@ -265,8 +265,8 @@ ssh_service:
 	</TabItem>
 	<TabItem label="Enterprise" label="Enterprise" scope={["enterprise"]}>
 **1. Configure Teleport Auth Server** using the below example `teleport.yaml`, and start it
-using [systemd](https://raw.githubusercontent.com/gravitational/teleport/master/examples/systemd/teleport.service)
-or use DEB/RPM packages available from the [Customer Portal](https://dashboard.gravitational.com).
+using [systemd](../../management/admin/daemon.mdx). The DEB/RPM installations will
+automatically include the `systemd` configuration.
 
 ```yaml
 #

diff --git a/docs/pages/deploy-a-cluster/helm-deployments/aws.mdx b/docs/pages/deploy-a-cluster/helm-deployments/aws.mdx
@@ -271,9 +271,7 @@ Edit your `values.yaml` file to refer to the name of your secret:
 Before you can install Teleport in your Kubernetes cluster, you will need to
 create a secret that contains your Teleport license information.
 
-Download your Teleport Enterprise license from the
-[Customer Portal](https://dashboard.gravitational.com/web/login) and save it to
-a file called `license.pem`.
+(!docs/pages/includes/enterprise/obtainlicense.mdx!)
 
 Create a secret from your license file. Teleport will automatically discover
 this secret as long as your file is named `license.pem`.

diff --git a/docs/pages/deploy-a-cluster/helm-deployments/custom.mdx b/docs/pages/deploy-a-cluster/helm-deployments/custom.mdx
@@ -136,9 +136,7 @@ namespace/teleport labeled
 Before you can install Teleport in your Kubernetes cluster, you will need to
 create a secret that contains your Teleport license information.
 
-Download your Teleport Enterprise license from the
-[Customer Portal](https://dashboard.gravitational.com/web/login) and save it to
-a file called `license.pem`.
+(!docs/pages/includes/enterprise/obtainlicense.mdx!)
 
 Create a secret from your license file. Teleport will automatically discover
 this secret as long as your file is named `license.pem`.

diff --git a/docs/pages/deploy-a-cluster/helm-deployments/digitalocean.mdx b/docs/pages/deploy-a-cluster/helm-deployments/digitalocean.mdx
@@ -72,9 +72,7 @@ $ kubectl label namespace teleport-cluster 'pod-security.kubernetes.io/enforce=b
 namespace/teleport-cluster labeled
 ```
 
-Obtain your Teleport Enterprise license file from the [Teleport Customer
-Portal](https://dashboard.gravitational.com/web/login). Create a secret called
-"license" in the namespace you created:
+(!docs/pages/includes/enterprise/obtainlicense.mdx!)
 
 ```code
 $ kubectl -n teleport-cluster create secret generic license --from-file=license.pem

diff --git a/docs/pages/deploy-a-cluster/helm-deployments/gcp.mdx b/docs/pages/deploy-a-cluster/helm-deployments/gcp.mdx
@@ -282,9 +282,7 @@ $ kubectl --namespace teleport create -f gcp-issuer.yaml
 Before you can install Teleport Enterprise in your Kubernetes cluster, you will need to
 create a secret that contains your Teleport license information.
 
-Download your Teleport Enterprise license from the
-[Customer Portal](https://dashboard.gravitational.com/web/login) and save it to
-a file called `license.pem`.
+(!docs/pages/includes/enterprise/obtainlicense.mdx!)
 
 Create a secret from your license file. Teleport will automatically discover
 this secret as long as your file is named `license.pem`.

diff --git a/docs/pages/includes/commercial-prereqs-tabs.mdx b/docs/pages/includes/commercial-prereqs-tabs.mdx
@@ -7,8 +7,7 @@
   Started](/docs/enterprise/getting-started) guide.
 
 - The Enterprise `tctl` admin tool and `tsh` client tool version >= (=teleport.version=),
-  which you can download by visiting the
-  [customer portal](https://dashboard.gravitational.com/web/login).
+  which you can download by visiting your [Teleport account](https://teleport.sh).
 
   ```code
   $ tctl version

diff --git a/docs/pages/includes/edition-prereqs-tabs.mdx b/docs/pages/includes/edition-prereqs-tabs.mdx
@@ -29,8 +29,7 @@ files in partials, this partial uses relative URL paths instead.
   [Getting Started](/docs/enterprise/getting-started) guide.
 
 - The Enterprise `tctl` admin tool and `tsh` client tool version >= (=teleport.version=),
-  which you can download by visiting the
-  [customer portal](https://dashboard.gravitational.com/web/login).
+  which you can download by visiting your [Teleport account](https://teleport.sh).
 
   ```code
   $ tctl version

diff --git a/docs/pages/includes/enterprise/obtainlicense.mdx b/docs/pages/includes/enterprise/obtainlicense.mdx
@@ -1,9 +1,10 @@
-The `teleport` binary reads a local license file to authenticate your Teleport
+The Teleport Auth Service reads a license file to authenticate your Teleport
 Enterprise account.
 
-To obtain your license file, visit the [Teleport customer
-dashboard](https://dashboard.gravitational.com/web/login) and log in. Click
-"DOWNLOAD LICENSE KEY". You will see your current Teleport Enterprise account
-permissions and the option to download your license file:
+To obtain your license file, navigate to your [Teleport
+account](https://teleport.sh) and enter your
+account name (e.g., `my-license`). After logging in, click
+the "DOWNLOAD LICENSE KEY" button to download your
+license file.
 
-![License File modal](../../../img/enterprise/license.png)
+![License File Download](../../../img/enterprise/license.png)
diff --git a/docs/pages/includes/install-linux.mdx b/docs/pages/includes/install-linux.mdx
@@ -1,7 +1,6 @@
 <ScopedBlock scope={["enterprise"]}>
 
-Visit the [Downloads Page](https://dashboard.gravitational.com/web/downloads) in
-the customer portal and select the URL for your package of choice.
+Visit your [Teleport account](https://teleport.sh) and select the URL for your package of choice.
 
 </ScopedBlock>
 

diff --git a/docs/pages/includes/user-client-prereqs.mdx b/docs/pages/includes/user-client-prereqs.mdx
@@ -22,8 +22,7 @@
   scope={["enterprise"]} label="Enterprise">
 
 - The `tctl` and `tsh` client tools version >= (=teleport.version=), which you
-  can download by visiting the
-  [customer portal](https://dashboard.gravitational.com/web/login).
+  can download by visiting your [Teleport account](https://teleport.sh).
 
   ```code
   $ tctl version

diff --git a/docs/pages/kubernetes-access/discovery/google-cloud.mdx b/docs/pages/kubernetes-access/discovery/google-cloud.mdx
@@ -30,7 +30,6 @@ Auto-Discovery for GKE.
 - A Linux host where you will run the Teleport Discovery and Kubernetes
   services. You can run this host on any cloud provider or even use a local
   machine.
-
 - (!docs/pages/includes/tctl.mdx!)
 
 ## Step 1/3. Obtain Google Cloud credentials

diff --git a/docs/pages/management/admin/self-signed-certs.mdx b/docs/pages/management/admin/self-signed-certs.mdx
@@ -80,8 +80,7 @@ For example, this Teleport Proxy Service configuration would use self-signed cer
   ```
 
 - The `tctl` admin tool and `tsh` client tool version >= (=teleport.version=),
-  which you can download by visiting the
-  [customer portal](https://dashboard.gravitational.com/web/login).
+  which you can download by visiting your [Teleport account](https://teleport.sh).
 
   ```code
   $ tctl version

diff --git a/docs/pages/management/admin/troubleshooting.mdx b/docs/pages/management/admin/troubleshooting.mdx
@@ -151,7 +151,7 @@ Teleport v9.0.4 git: go1.18
 
 <Tabs>
 <TabItem scope={["cloud", "enterprise"]} label="Commercial">
-If you need help, please ask on our [community forum](https://github.com/gravitational/teleport/discussions). You can also open an [issue on GitHub](https://github.com/gravitational/teleport/issues) or create a ticket through the [customer dashboard](https://dashboard.gravitational.com/web/login).
+If you need help, please ask on our [community forum](https://github.com/gravitational/teleport/discussions). You can also open an [issue on GitHub](https://github.com/gravitational/teleport/issues) or create a ticket through your [Teleport account](https://teleport.sh).
 
 </TabItem>
 <TabItem scope={["oss"]} label="Open Source">

diff --git a/docs/pages/management/admin/trustedclusters.mdx b/docs/pages/management/admin/trustedclusters.mdx
@@ -73,8 +73,7 @@ This guide will explain how to:
   our Enterprise [Getting Started](/docs/enterprise/getting-started) guide.
 
 - The `tctl` admin tool and `tsh` client tool version >= (=teleport.version=),
-  which you can download by visiting the
-  [customer portal](https://dashboard.gravitational.com/web/login).
+  which you can download by visiting your [Teleport account](https://teleport.sh).
 
   ```code
   $ tctl version

diff --git a/docs/pages/management/guides/docker.mdx b/docs/pages/management/guides/docker.mdx
@@ -41,7 +41,7 @@ Service) or explore the Auth and Proxy Services locally. In this guide, we will
   # Version:           (=docker.version=)
   ```
 
-- The `tsh` client tool, which ships with the `teleport` binary. Visit the [customer portal](https://dashboard.gravitational.com/web/login) to download Teleport.
+- The `tsh` client tool, which ships with the `teleport` binary. Visit your [Teleport account](https://teleport.sh) to download Teleport.
 
 </TabItem>
 </Tabs>

diff --git a/docs/pages/management/guides/teleport-operator.mdx b/docs/pages/management/guides/teleport-operator.mdx
@@ -77,9 +77,9 @@ Create a namespace for your Teleport cluster resources:
 $ kubectl create namespace teleport-cluster
 ```
 
-Obtain your Teleport Enterprise license file from the [Teleport Customer
-Portal](https://dashboard.gravitational.com/web/login). Create a secret called
-"license" in the namespace you created:
+(!docs/pages/includes/enterprise/obtainlicense.mdx!)
+
+Create a secret called "license" in the namespace you created:
 
 ```code
 $ kubectl -n teleport-cluster create secret generic license --from-file=license.pem

diff --git a/docs/pages/management/join-services-to-your-cluster/aws-ec2.mdx b/docs/pages/management/join-services-to-your-cluster/aws-ec2.mdx
@@ -49,7 +49,6 @@ AWS-specific APIs.
 (!docs/pages/includes/edition-prereqs-tabs.mdx!)
 
 - (!docs/pages/includes/tctl.mdx!)
-
 - An AWS EC2 instance to host a Teleport process, with the Teleport binary
   installed. The host should not have an existing data dir (`/var/lib/teleport`
   by default). Remove the data directory if this instance has previously joined

diff --git a/docs/pages/server-access/guides/host-user-creation.mdx b/docs/pages/server-access/guides/host-user-creation.mdx
@@ -28,7 +28,6 @@ since it must execute these commands in order to create transient users:
   - `groupadd`
   - `getent`
   - `visudo`
-
 - (!docs/pages/includes/tctl.mdx!)
 
 ## Step 1/2. Configure a role