2021-02-10 18:07:30 +00:00
|
|
|
{
|
|
|
|
|
"navigation": [
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"icon": "home",
|
2021-04-15 00:06:57 +00:00
|
|
|
"title": "Home",
|
2021-02-10 18:07:30 +00:00
|
|
|
"entries": [
|
2022-02-22 23:21:46 +00:00
|
|
|
{
|
|
|
|
|
"title": "Introduction",
|
|
|
|
|
"slug": "/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Adopters",
|
|
|
|
|
"slug": "/adopters/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Installation",
|
|
|
|
|
"slug": "/installation/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "FAQ",
|
|
|
|
|
"slug": "/faq/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Changelog",
|
|
|
|
|
"slug": "/changelog/"
|
|
|
|
|
}
|
2021-02-10 18:07:30 +00:00
|
|
|
]
|
|
|
|
|
},
|
2021-06-02 22:46:59 +00:00
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"icon": "play",
|
|
|
|
|
"title": "Try out Teleport",
|
2021-06-02 22:46:59 +00:00
|
|
|
"entries": [
|
2021-08-19 22:00:26 +00:00
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Browser Labs",
|
|
|
|
|
"slug": "/try-out-teleport/browser-labs/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Docker Compose",
|
|
|
|
|
"slug": "/try-out-teleport/docker-compose/",
|
|
|
|
|
"forScopes": ["oss"]
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Local Kubernetes Lab",
|
|
|
|
|
"slug": "/try-out-teleport/local-kubernetes/",
|
|
|
|
|
"forScopes": ["oss"]
|
|
|
|
|
}
|
|
|
|
|
]
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"icon": "quickstart",
|
|
|
|
|
"title": "Deploy a Cluster",
|
|
|
|
|
"entries": [
|
|
|
|
|
{
|
|
|
|
|
"title": "Open Source Teleport",
|
|
|
|
|
"slug": "/deploy-a-cluster/open-source/",
|
|
|
|
|
"forScopes": ["oss"]
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Teleport Cloud",
|
|
|
|
|
"slug": "/deploy-a-cluster/teleport-cloud/introduction/",
|
|
|
|
|
"forScopes": ["cloud"],
|
2021-08-19 22:00:26 +00:00
|
|
|
"entries": [
|
2022-02-22 23:21:46 +00:00
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Getting Started",
|
|
|
|
|
"slug": "/deploy-a-cluster/teleport-cloud/getting-started/",
|
|
|
|
|
"forScopes": ["cloud"]
|
2022-02-22 23:21:46 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Architecture",
|
|
|
|
|
"slug": "/deploy-a-cluster/teleport-cloud/architecture/",
|
|
|
|
|
"forScopes": ["cloud"]
|
2022-02-22 23:21:46 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Downloads",
|
|
|
|
|
"slug": "/deploy-a-cluster/teleport-cloud/downloads/",
|
|
|
|
|
"forScopes": ["cloud"]
|
2022-02-22 23:21:46 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "FAQ",
|
|
|
|
|
"slug": "/deploy-a-cluster/teleport-cloud/faq/",
|
|
|
|
|
"forScopes": ["cloud"]
|
|
|
|
|
}
|
|
|
|
|
]
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Teleport Enterprise",
|
|
|
|
|
"slug": "/deploy-a-cluster/teleport-enterprise/introduction/",
|
|
|
|
|
"forScopes": ["enterprise"],
|
|
|
|
|
"entries": [
|
|
|
|
|
{
|
|
|
|
|
"title": "Getting Started",
|
|
|
|
|
"slug": "/deploy-a-cluster/teleport-enterprise/getting-started/",
|
|
|
|
|
"forScopes": ["enterprise"]
|
2022-02-22 23:21:46 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "HSM",
|
|
|
|
|
"slug": "/deploy-a-cluster/teleport-enterprise/hsm/",
|
|
|
|
|
"forScopes": ["enterprise"]
|
2022-02-22 23:21:46 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Enterprise License File",
|
|
|
|
|
"slug": "/deploy-a-cluster/teleport-enterprise/license/",
|
|
|
|
|
"forScopes": ["enterprise"]
|
|
|
|
|
}
|
|
|
|
|
]
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Deploy with Helm",
|
|
|
|
|
"slug": "/deploy-a-cluster/helm-deployments/",
|
|
|
|
|
"forScopes": ["oss", "enterprise"],
|
|
|
|
|
"entries": [
|
|
|
|
|
{
|
|
|
|
|
"title": "Deploy Teleport on Kubernetes",
|
|
|
|
|
"slug": "/deploy-a-cluster/helm-deployments/kubernetes-cluster/",
|
2022-07-20 19:26:27 +00:00
|
|
|
"forScopes": ["oss", "enterprise"]
|
2022-02-22 23:21:46 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "AWS EKS Cluster",
|
|
|
|
|
"slug": "/deploy-a-cluster/helm-deployments/aws/",
|
|
|
|
|
"forScopes": ["oss", "enterprise"]
|
2022-02-22 23:21:46 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Google Cloud GKE Cluster",
|
|
|
|
|
"slug": "/deploy-a-cluster/helm-deployments/gcp/",
|
|
|
|
|
"forScopes": ["oss", "enterprise"]
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "DigitalOcean Kubernetes Cluster",
|
|
|
|
|
"slug": "/deploy-a-cluster/helm-deployments/digitalocean/",
|
|
|
|
|
"forScopes": ["oss", "enterprise"]
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Customize Deployment Config",
|
|
|
|
|
"slug": "/deploy-a-cluster/helm-deployments/custom/",
|
|
|
|
|
"forScopes": ["oss", "enterprise"]
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Migrating From Older Charts",
|
|
|
|
|
"slug": "/deploy-a-cluster/helm-deployments/migration/",
|
|
|
|
|
"forScopes": ["oss", "enterprise"]
|
2022-02-22 23:21:46 +00:00
|
|
|
}
|
2021-08-19 22:00:26 +00:00
|
|
|
]
|
|
|
|
|
},
|
2021-06-02 22:46:59 +00:00
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Deploy to your Cloud",
|
|
|
|
|
"slug": "/deploy-a-cluster/deployments/",
|
2022-07-20 19:26:27 +00:00
|
|
|
"forScopes": ["oss", "enterprise"],
|
2021-07-16 20:46:55 +00:00
|
|
|
"entries": [
|
2022-02-22 23:21:46 +00:00
|
|
|
{
|
|
|
|
|
"title": "AWS Terraform",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"slug": "/deploy-a-cluster/deployments/aws-terraform/",
|
2022-07-20 19:26:27 +00:00
|
|
|
"forScopes": ["oss", "enterprise"]
|
2022-02-22 23:21:46 +00:00
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "GCP",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"slug": "/deploy-a-cluster/deployments/gcp/",
|
2022-07-20 19:26:27 +00:00
|
|
|
"forScopes": ["oss", "enterprise"]
|
2022-02-22 23:21:46 +00:00
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "IBM",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"slug": "/deploy-a-cluster/deployments/ibm/",
|
2022-07-20 19:26:27 +00:00
|
|
|
"forScopes": ["oss", "enterprise"]
|
2022-06-21 15:32:16 +00:00
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Digital Ocean",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"slug": "/deploy-a-cluster/deployments/digitalocean/",
|
2022-07-20 19:26:27 +00:00
|
|
|
"forScopes": ["oss", "enterprise"]
|
2022-02-22 23:21:46 +00:00
|
|
|
}
|
2021-07-16 20:46:55 +00:00
|
|
|
]
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
}
|
|
|
|
|
]
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"icon": "lock",
|
|
|
|
|
"title": "Configure Access",
|
|
|
|
|
"entries": [
|
|
|
|
|
{
|
|
|
|
|
"title": "Introduction",
|
|
|
|
|
"slug": "/access-controls/introduction/"
|
2021-07-16 20:46:55 +00:00
|
|
|
},
|
2022-06-23 15:25:27 +00:00
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Getting Started",
|
|
|
|
|
"slug": "/access-controls/getting-started/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Cluster Access and RBAC",
|
|
|
|
|
"slug": "/access-controls/guides/",
|
2022-06-23 15:25:27 +00:00
|
|
|
"entries": [
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Role Templates",
|
|
|
|
|
"slug": "/access-controls/guides/role-templates/"
|
2022-06-23 15:25:27 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Session Locking",
|
|
|
|
|
"slug": "/access-controls/guides/locking/"
|
2022-06-23 15:25:27 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Passwordless (Preview)",
|
|
|
|
|
"slug": "/access-controls/guides/passwordless/"
|
2022-06-23 15:25:27 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Second Factor - WebAuthn",
|
|
|
|
|
"slug": "/access-controls/guides/webauthn/"
|
2022-06-23 15:25:27 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Per-session MFA",
|
|
|
|
|
"slug": "/access-controls/guides/per-session-mfa/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Dual Authorization",
|
|
|
|
|
"slug": "/access-controls/guides/dual-authz/",
|
|
|
|
|
"forScopes": ["enterprise", "cloud"]
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Impersonation",
|
|
|
|
|
"slug": "/access-controls/guides/impersonation/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Moderated Sessions",
|
|
|
|
|
"slug": "/access-controls/guides/moderated-sessions/",
|
|
|
|
|
"forScopes": ["enterprise", "cloud"]
|
2022-10-20 20:01:06 +00:00
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Hardware Key Support (Preview)",
|
|
|
|
|
"slug": "/access-controls/guides/hardware-key-support/",
|
|
|
|
|
"forScopes": ["enterprise", "cloud"]
|
2022-06-23 15:25:27 +00:00
|
|
|
}
|
|
|
|
|
]
|
|
|
|
|
},
|
2021-09-20 17:22:12 +00:00
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Single Sign-On (SSO)",
|
|
|
|
|
"slug": "/access-controls/sso/",
|
2022-10-17 15:12:59 +00:00
|
|
|
"forScopes": ["enterprise", "oss", "cloud"],
|
2021-09-20 17:22:12 +00:00
|
|
|
"entries": [
|
2022-02-22 23:21:46 +00:00
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "GitHub SSO",
|
|
|
|
|
"slug": "/access-controls/sso/github-sso/"
|
2022-02-22 23:21:46 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Azure Active Directory (AD)",
|
|
|
|
|
"slug": "/access-controls/sso/azuread/",
|
|
|
|
|
"forScopes": ["enterprise", "cloud"]
|
2022-02-22 23:21:46 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Active Directory (ADFS)",
|
|
|
|
|
"slug": "/access-controls/sso/adfs/",
|
|
|
|
|
"forScopes": ["enterprise", "cloud"]
|
2022-02-22 23:21:46 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Google Workspace",
|
|
|
|
|
"slug": "/access-controls/sso/google-workspace/",
|
|
|
|
|
"forScopes": ["enterprise", "cloud"]
|
2022-02-22 23:21:46 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "GitLab",
|
|
|
|
|
"slug": "/access-controls/sso/gitlab/",
|
|
|
|
|
"forScopes": ["enterprise", "cloud"]
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "OneLogin",
|
|
|
|
|
"slug": "/access-controls/sso/one-login/",
|
|
|
|
|
"forScopes": ["enterprise", "cloud"]
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "OIDC",
|
|
|
|
|
"slug": "/access-controls/sso/oidc/",
|
|
|
|
|
"forScopes": ["enterprise", "cloud"]
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Okta",
|
|
|
|
|
"slug": "/access-controls/sso/okta/",
|
|
|
|
|
"forScopes": ["enterprise", "cloud"]
|
2022-02-22 23:21:46 +00:00
|
|
|
}
|
2021-09-20 17:22:12 +00:00
|
|
|
]
|
|
|
|
|
},
|
2021-12-15 15:58:16 +00:00
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Access Requests",
|
|
|
|
|
"slug": "/access-controls/access-requests/",
|
2022-02-22 23:21:46 +00:00
|
|
|
"entries": [
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Role Requests",
|
|
|
|
|
"slug": "/access-controls/access-requests/role-requests/",
|
|
|
|
|
"forScopes": ["enterprise", "cloud"]
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Resource Requests",
|
|
|
|
|
"slug": "/access-controls/access-requests/resource-requests/",
|
|
|
|
|
"forScopes": ["enterprise", "cloud"]
|
2022-02-22 23:21:46 +00:00
|
|
|
}
|
2021-12-15 15:58:16 +00:00
|
|
|
]
|
|
|
|
|
},
|
2021-07-16 20:46:55 +00:00
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Access Request Plugins",
|
|
|
|
|
"slug": "/access-controls/access-request-plugins/",
|
|
|
|
|
"forScopes": ["enterprise", "cloud"],
|
2021-06-02 22:46:59 +00:00
|
|
|
"entries": [
|
2022-08-08 20:33:07 +00:00
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Mattermost",
|
|
|
|
|
"slug": "/access-controls/access-request-plugins/ssh-approval-mattermost/",
|
|
|
|
|
"forScopes": ["enterprise", "cloud"]
|
2022-08-08 20:33:07 +00:00
|
|
|
},
|
2022-09-22 18:35:06 +00:00
|
|
|
{
|
|
|
|
|
"title": "Microsoft Teams",
|
|
|
|
|
"slug": "/access-controls/access-request-plugins/ssh-approval-msteams/",
|
|
|
|
|
"forScopes": ["enterprise", "cloud"]
|
|
|
|
|
},
|
2022-02-22 23:21:46 +00:00
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "PagerDuty",
|
|
|
|
|
"slug": "/access-controls/access-request-plugins/ssh-approval-pagerduty/",
|
|
|
|
|
"forScopes": ["enterprise", "cloud"]
|
2022-02-22 23:21:46 +00:00
|
|
|
},
|
|
|
|
|
{
|
2022-11-04 20:28:58 +00:00
|
|
|
"title": "Jira",
|
|
|
|
|
"slug": "/access-controls/access-request-plugins/ssh-approval-jira/",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"forScopes": ["enterprise", "cloud"]
|
2022-02-22 23:21:46 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Slack",
|
|
|
|
|
"slug": "/access-controls/access-request-plugins/ssh-approval-slack/",
|
|
|
|
|
"forScopes": ["enterprise", "cloud"]
|
2022-02-22 23:21:46 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Email",
|
|
|
|
|
"slug": "/access-controls/access-request-plugins/ssh-approval-email/",
|
|
|
|
|
"forScopes": ["enterprise", "cloud"]
|
|
|
|
|
}
|
|
|
|
|
]
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Compliance Frameworks",
|
|
|
|
|
"slug": "/access-controls/compliance-frameworks/",
|
|
|
|
|
"forScopes": ["enterprise", "cloud"],
|
|
|
|
|
"entries": [
|
2022-03-23 21:09:26 +00:00
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "FedRAMP",
|
|
|
|
|
"slug": "/access-controls/compliance-frameworks/fedramp/",
|
|
|
|
|
"forScopes": ["enterprise"]
|
2022-03-30 08:45:32 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "SOC 2",
|
|
|
|
|
"slug": "/access-controls/compliance-frameworks/soc2/",
|
|
|
|
|
"forScopes": ["enterprise", "cloud"]
|
2022-02-22 23:21:46 +00:00
|
|
|
}
|
2021-06-13 02:10:19 +00:00
|
|
|
]
|
|
|
|
|
},
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
|
2021-06-13 02:10:19 +00:00
|
|
|
{
|
|
|
|
|
"title": "Reference",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"slug": "/access-controls/reference/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "FAQ",
|
|
|
|
|
"slug": "/access-controls/faq/"
|
|
|
|
|
}
|
|
|
|
|
]
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"icon": "wrench",
|
|
|
|
|
"title": "Manage your Cluster",
|
|
|
|
|
"entries": [
|
|
|
|
|
{
|
|
|
|
|
"title": "Admin Guides",
|
|
|
|
|
"slug": "/management/admin/",
|
2021-06-13 02:10:19 +00:00
|
|
|
"entries": [
|
2022-02-22 23:21:46 +00:00
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Adding Nodes",
|
|
|
|
|
"slug": "/management/admin/adding-nodes/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Trusted Clusters",
|
|
|
|
|
"slug": "/management/admin/trustedclusters/"
|
2022-02-22 23:21:46 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Labels",
|
|
|
|
|
"slug": "/management/admin/labels/"
|
2022-02-22 23:21:46 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Local Users",
|
|
|
|
|
"slug": "/management/admin/users/"
|
2022-02-22 23:21:46 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Troubleshooting",
|
|
|
|
|
"slug": "/management/admin/troubleshooting/",
|
2022-10-15 01:01:19 +00:00
|
|
|
"forScopes": ["oss", "enterprise", "cloud"]
|
2022-02-22 23:21:46 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Upgrading the Teleport Binary",
|
|
|
|
|
"slug": "/management/admin/upgrading-the-teleport-binary/"
|
2022-02-22 23:21:46 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Run Teleport as a Daemon",
|
|
|
|
|
"slug": "/management/admin/daemon/"
|
2022-10-11 18:02:42 +00:00
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Run Teleport with Self-Signed Certificates",
|
|
|
|
|
"slug": "/management/admin/self-signed-certs/"
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
}
|
|
|
|
|
]
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Operations",
|
|
|
|
|
"slug": "/management/operations/",
|
|
|
|
|
"entries": [
|
|
|
|
|
{
|
|
|
|
|
"title": "Scaling",
|
|
|
|
|
"slug": "/management/operations/scaling/",
|
|
|
|
|
"forScopes": ["oss", "enterprise"]
|
2022-02-22 23:21:46 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Upgrading a Cluster",
|
|
|
|
|
"slug": "/management/operations/upgrading/"
|
2022-02-22 23:21:46 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Backup and Restore",
|
|
|
|
|
"slug": "/management/operations/backup-restore/",
|
2022-07-20 19:26:27 +00:00
|
|
|
"forScopes": ["oss", "enterprise"]
|
2022-02-22 23:21:46 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Cert Authority Rotation",
|
|
|
|
|
"slug": "/management/operations/ca-rotation/"
|
2022-04-26 23:57:19 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "TLS Routing Migration",
|
|
|
|
|
"slug": "/management/operations/tls-routing/",
|
|
|
|
|
"forScopes": ["oss", "enterprise"]
|
2022-10-04 16:00:37 +00:00
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Proxy Peering Migration",
|
|
|
|
|
"slug": "/management/operations/proxy-peering/",
|
|
|
|
|
"forScopes": ["enterprise"]
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
}
|
|
|
|
|
]
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Security",
|
|
|
|
|
"slug": "/management/security/",
|
|
|
|
|
"entries": [
|
2022-05-12 21:17:34 +00:00
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Reducing the Blast Radius of Attacks",
|
|
|
|
|
"slug": "/management/security/reduce-blast-radius/"
|
2022-02-22 23:21:46 +00:00
|
|
|
}
|
2021-06-02 22:46:59 +00:00
|
|
|
]
|
2022-06-24 21:38:59 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Integrations",
|
|
|
|
|
"slug": "/management/guides/",
|
2022-06-24 21:38:59 +00:00
|
|
|
"entries": [
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Kubernetes Operator (Preview)",
|
|
|
|
|
"slug": "/management/guides/teleport-operator/"
|
2022-06-24 21:38:59 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Terraform Provider",
|
|
|
|
|
"slug": "/management/guides/terraform-provider/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Docker",
|
|
|
|
|
"slug": "/management/guides/docker/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Fluentd",
|
2022-09-29 15:23:25 +00:00
|
|
|
"slug": "/management/guides/fluentd/",
|
|
|
|
|
"forScopes": ["enterprise", "cloud"]
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Monitor Audit Events with the Elastic Stack",
|
|
|
|
|
"slug": "/management/guides/elastic-stack/",
|
|
|
|
|
"forScopes": ["enterprise", "cloud"]
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "EC2 Tags",
|
|
|
|
|
"slug": "/management/guides/ec2-tags/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Joining Nodes via AWS IAM",
|
|
|
|
|
"slug": "/management/guides/joining-nodes-aws-iam/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Joining Nodes via AWS EC2",
|
|
|
|
|
"slug": "/management/guides/joining-nodes-aws-ec2/",
|
|
|
|
|
"forScopes": ["oss", "enterprise"]
|
2022-08-18 10:22:23 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Using Teleport's CA with GitHub",
|
|
|
|
|
"slug": "/management/guides/ssh-key-extensions/"
|
2022-06-24 21:38:59 +00:00
|
|
|
}
|
|
|
|
|
]
|
2022-10-14 20:05:07 +00:00
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Diagnostics",
|
|
|
|
|
"slug": "/management/diagnostics/",
|
|
|
|
|
"entries": [
|
|
|
|
|
{
|
|
|
|
|
"title": "Health Monitoring",
|
|
|
|
|
"slug": "/management/diagnostics/monitoring/",
|
|
|
|
|
"forScopes": ["oss", "enterprise", "cloud"]
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Metrics",
|
|
|
|
|
"slug": "/management/diagnostics/metrics/",
|
|
|
|
|
"forScopes": ["oss", "enterprise", "cloud"]
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Collecting Profiles",
|
|
|
|
|
"slug": "/management/diagnostics/profiles/",
|
|
|
|
|
"forScopes": ["oss", "enterprise", "cloud"]
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Distributed Tracing",
|
|
|
|
|
"slug": "/management/diagnostics/tracing/",
|
|
|
|
|
"forScopes": ["oss", "enterprise", "cloud"]
|
|
|
|
|
}
|
|
|
|
|
]
|
2021-06-02 22:46:59 +00:00
|
|
|
}
|
|
|
|
|
]
|
|
|
|
|
},
|
2022-07-20 08:32:53 +00:00
|
|
|
{
|
|
|
|
|
"icon": "connect",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Connect your Client",
|
2022-07-20 08:32:53 +00:00
|
|
|
"entries": [
|
|
|
|
|
{
|
|
|
|
|
"title": "Using tsh",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"slug": "/connect-your-client/tsh/"
|
2022-07-27 16:02:52 +00:00
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Using Teleport Connect",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"slug": "/connect-your-client/teleport-connect/"
|
|
|
|
|
},
|
|
|
|
|
|
|
|
|
|
{
|
|
|
|
|
"title": "Database GUI Clients",
|
|
|
|
|
"slug": "/connect-your-client/gui-clients/"
|
2022-07-20 08:32:53 +00:00
|
|
|
}
|
|
|
|
|
]
|
|
|
|
|
},
|
2021-03-28 17:09:58 +00:00
|
|
|
{
|
|
|
|
|
"icon": "window",
|
|
|
|
|
"title": "Application Access",
|
|
|
|
|
"entries": [
|
2022-02-22 23:21:46 +00:00
|
|
|
{
|
|
|
|
|
"title": "Introduction",
|
|
|
|
|
"slug": "/application-access/introduction/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Getting Started",
|
|
|
|
|
"slug": "/application-access/getting-started/"
|
|
|
|
|
},
|
2021-03-28 17:09:58 +00:00
|
|
|
{
|
2022-06-03 15:25:20 +00:00
|
|
|
"title": "Access Guides",
|
2021-03-28 17:09:58 +00:00
|
|
|
"slug": "/application-access/guides/",
|
|
|
|
|
"entries": [
|
2022-02-22 23:21:46 +00:00
|
|
|
{
|
2022-08-02 17:26:27 +00:00
|
|
|
"title": "Web App Access",
|
2022-02-22 23:21:46 +00:00
|
|
|
"slug": "/application-access/guides/connecting-apps/"
|
|
|
|
|
},
|
2022-08-02 17:26:27 +00:00
|
|
|
{
|
|
|
|
|
"title": "TCP App Access (Preview)",
|
|
|
|
|
"slug": "/application-access/guides/tcp/"
|
|
|
|
|
},
|
2022-02-22 23:21:46 +00:00
|
|
|
{
|
|
|
|
|
"title": "API Access",
|
|
|
|
|
"slug": "/application-access/guides/api-access/"
|
|
|
|
|
},
|
|
|
|
|
{
|
2022-08-24 15:17:38 +00:00
|
|
|
"title": "AWS Access",
|
2022-02-22 23:21:46 +00:00
|
|
|
"slug": "/application-access/guides/aws-console/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Dynamic Registration",
|
|
|
|
|
"slug": "/application-access/guides/dynamic-registration/"
|
|
|
|
|
}
|
2021-03-28 17:09:58 +00:00
|
|
|
]
|
|
|
|
|
},
|
2022-06-03 15:25:20 +00:00
|
|
|
{
|
|
|
|
|
"title": "JWT Guides",
|
|
|
|
|
"slug": "/application-access/jwt/",
|
|
|
|
|
"entries": [
|
|
|
|
|
{
|
|
|
|
|
"title": "Introduction",
|
|
|
|
|
"slug": "/application-access/jwt/introduction/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "ElasticSearch",
|
|
|
|
|
"slug": "/application-access/jwt/elasticsearch/"
|
|
|
|
|
}
|
|
|
|
|
]
|
|
|
|
|
},
|
2022-02-22 23:21:46 +00:00
|
|
|
{
|
|
|
|
|
"title": "Access Controls",
|
|
|
|
|
"slug": "/application-access/controls/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Reference",
|
|
|
|
|
"slug": "/application-access/reference/"
|
|
|
|
|
}
|
2021-03-28 17:09:58 +00:00
|
|
|
]
|
|
|
|
|
},
|
2021-05-27 02:36:48 +00:00
|
|
|
{
|
|
|
|
|
"icon": "server",
|
|
|
|
|
"title": "Server Access",
|
|
|
|
|
"entries": [
|
2022-02-22 23:21:46 +00:00
|
|
|
{
|
|
|
|
|
"title": "Introduction",
|
|
|
|
|
"slug": "/server-access/introduction/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Getting Started",
|
|
|
|
|
"slug": "/server-access/getting-started/"
|
|
|
|
|
},
|
2021-05-27 02:36:48 +00:00
|
|
|
{
|
|
|
|
|
"title": "Guides",
|
|
|
|
|
"slug": "/server-access/guides/",
|
|
|
|
|
"entries": [
|
2022-02-22 23:21:46 +00:00
|
|
|
{
|
|
|
|
|
"title": "Using Teleport with PAM",
|
|
|
|
|
"slug": "/server-access/guides/ssh-pam/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "OpenSSH Guide",
|
|
|
|
|
"slug": "/server-access/guides/openssh/"
|
|
|
|
|
},
|
2022-03-31 21:35:48 +00:00
|
|
|
{
|
|
|
|
|
"title": "Recording Proxy Mode",
|
2022-07-20 19:26:27 +00:00
|
|
|
"slug": "/server-access/guides/recording-proxy-mode/",
|
|
|
|
|
"forScopes": ["oss", "enterprise"]
|
2022-03-31 21:35:48 +00:00
|
|
|
},
|
2022-02-22 23:21:46 +00:00
|
|
|
{
|
|
|
|
|
"title": "BPF Session Recording",
|
|
|
|
|
"slug": "/server-access/guides/bpf-session-recording/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Restricted Session",
|
|
|
|
|
"slug": "/server-access/guides/restricted-session/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Visual Studio Code",
|
|
|
|
|
"slug": "/server-access/guides/vscode/"
|
2022-07-06 15:03:56 +00:00
|
|
|
},
|
2022-10-17 19:11:58 +00:00
|
|
|
{
|
|
|
|
|
"title": "JetBrains SFTP",
|
|
|
|
|
"slug": "/server-access/guides/jetbrains-sftp/"
|
|
|
|
|
},
|
2022-07-06 15:03:56 +00:00
|
|
|
{
|
|
|
|
|
"title": "Host User Creation",
|
|
|
|
|
"slug": "/server-access/guides/host-user-creation/"
|
2022-10-05 14:53:39 +00:00
|
|
|
},
|
|
|
|
|
{
|
2022-10-13 09:37:06 +00:00
|
|
|
"title": "EC2 Instance Discovery (Preview)",
|
2022-10-05 14:53:39 +00:00
|
|
|
"slug": "/server-access/guides/ec2-discovery/"
|
2022-02-22 23:21:46 +00:00
|
|
|
}
|
2021-05-27 02:36:48 +00:00
|
|
|
]
|
|
|
|
|
}
|
|
|
|
|
]
|
|
|
|
|
},
|
2021-02-10 18:07:30 +00:00
|
|
|
{
|
2021-03-10 19:48:37 +00:00
|
|
|
"icon": "kubernetes",
|
|
|
|
|
"title": "Kubernetes Access",
|
2021-02-10 18:07:30 +00:00
|
|
|
"entries": [
|
2022-02-22 23:21:46 +00:00
|
|
|
{
|
|
|
|
|
"title": "Introduction",
|
|
|
|
|
"slug": "/kubernetes-access/introduction/"
|
|
|
|
|
},
|
2021-07-23 01:37:42 +00:00
|
|
|
{
|
|
|
|
|
"title": "Getting Started",
|
2022-07-12 15:18:37 +00:00
|
|
|
"slug": "/kubernetes-access/getting-started/"
|
2021-07-23 01:37:42 +00:00
|
|
|
},
|
2021-03-10 19:48:37 +00:00
|
|
|
{
|
|
|
|
|
"title": "Guides",
|
|
|
|
|
"slug": "/kubernetes-access/guides/",
|
|
|
|
|
"entries": [
|
2022-02-22 23:21:46 +00:00
|
|
|
{
|
|
|
|
|
"title": "Multiple Clusters",
|
|
|
|
|
"slug": "/kubernetes-access/guides/multiple-clusters/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "CI/CD",
|
|
|
|
|
"slug": "/kubernetes-access/guides/cicd/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Federation",
|
|
|
|
|
"slug": "/kubernetes-access/guides/federation/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Standalone",
|
|
|
|
|
"slug": "/kubernetes-access/guides/standalone-teleport/"
|
|
|
|
|
}
|
2021-03-10 19:48:37 +00:00
|
|
|
]
|
|
|
|
|
},
|
2022-02-22 23:21:46 +00:00
|
|
|
{
|
|
|
|
|
"title": "Access Controls",
|
|
|
|
|
"slug": "/kubernetes-access/controls/"
|
|
|
|
|
}
|
2021-02-10 18:07:30 +00:00
|
|
|
]
|
|
|
|
|
},
|
2021-03-04 18:07:48 +00:00
|
|
|
{
|
|
|
|
|
"icon": "database",
|
|
|
|
|
"title": "Database Access",
|
|
|
|
|
"entries": [
|
2022-02-22 23:21:46 +00:00
|
|
|
{
|
|
|
|
|
"title": "Introduction",
|
|
|
|
|
"slug": "/database-access/introduction/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Getting Started",
|
|
|
|
|
"slug": "/database-access/getting-started/"
|
|
|
|
|
},
|
2021-03-04 18:07:48 +00:00
|
|
|
{
|
|
|
|
|
"title": "Guides",
|
|
|
|
|
"slug": "/database-access/guides/",
|
|
|
|
|
"entries": [
|
2022-02-22 23:21:46 +00:00
|
|
|
{
|
|
|
|
|
"title": "AWS RDS & Aurora",
|
|
|
|
|
"slug": "/database-access/guides/rds/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "AWS Redshift",
|
|
|
|
|
"slug": "/database-access/guides/postgres-redshift/"
|
|
|
|
|
},
|
2022-06-30 16:10:57 +00:00
|
|
|
{
|
2022-07-07 03:29:45 +00:00
|
|
|
"title": "AWS ElastiCache & MemoryDB",
|
2022-06-30 16:10:57 +00:00
|
|
|
"slug": "/database-access/guides/redis-aws/"
|
|
|
|
|
},
|
2022-08-10 16:34:01 +00:00
|
|
|
{
|
|
|
|
|
"title": "AWS DynamoDB",
|
|
|
|
|
"slug": "/database-access/guides/dynamodb/"
|
|
|
|
|
},
|
2022-02-22 23:21:46 +00:00
|
|
|
{
|
|
|
|
|
"title": "GCP Cloud SQL PostgreSQL",
|
|
|
|
|
"slug": "/database-access/guides/postgres-cloudsql/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "GCP Cloud SQL MySQL",
|
|
|
|
|
"slug": "/database-access/guides/mysql-cloudsql/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Azure PostgreSQL & MySQL",
|
|
|
|
|
"slug": "/database-access/guides/azure-postgres-mysql/"
|
|
|
|
|
},
|
2022-10-27 20:32:25 +00:00
|
|
|
{
|
|
|
|
|
"title": "Azure Cache for Redis",
|
|
|
|
|
"slug": "/database-access/guides/azure-redis/"
|
|
|
|
|
},
|
2022-11-01 23:39:43 +00:00
|
|
|
{
|
|
|
|
|
"title": "Azure SQL Server (Preview)",
|
|
|
|
|
"slug": "/database-access/guides/azure-sql-server-ad/"
|
|
|
|
|
},
|
2022-02-22 23:21:46 +00:00
|
|
|
{
|
|
|
|
|
"title": "MongoDB Atlas",
|
|
|
|
|
"slug": "/database-access/guides/mongodb-atlas/"
|
|
|
|
|
},
|
2022-10-25 15:05:14 +00:00
|
|
|
{
|
|
|
|
|
"title": "Self-Hosted Elasticsearch",
|
|
|
|
|
"slug": "/database-access/guides/elastic/"
|
|
|
|
|
},
|
2022-02-22 23:21:46 +00:00
|
|
|
{
|
|
|
|
|
"title": "Self-Hosted PostgreSQL",
|
|
|
|
|
"slug": "/database-access/guides/postgres-self-hosted/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Self-Hosted MySQL/MariaDB",
|
|
|
|
|
"slug": "/database-access/guides/mysql-self-hosted/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Self-Hosted MongoDB",
|
|
|
|
|
"slug": "/database-access/guides/mongodb-self-hosted/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Self-Hosted CockroachDB",
|
|
|
|
|
"slug": "/database-access/guides/cockroachdb-self-hosted/"
|
|
|
|
|
},
|
2022-03-11 18:05:13 +00:00
|
|
|
{
|
|
|
|
|
"title": "Self-Hosted Redis",
|
|
|
|
|
"slug": "/database-access/guides/redis/"
|
|
|
|
|
},
|
2022-04-04 15:53:54 +00:00
|
|
|
{
|
|
|
|
|
"title": "Self-Hosted Redis Cluster",
|
|
|
|
|
"slug": "/database-access/guides/redis-cluster/"
|
|
|
|
|
},
|
2022-02-22 23:21:46 +00:00
|
|
|
{
|
|
|
|
|
"title": "SQL Server (Preview)",
|
|
|
|
|
"slug": "/database-access/guides/sql-server-ad/"
|
|
|
|
|
},
|
2022-06-30 02:53:19 +00:00
|
|
|
{
|
|
|
|
|
"title": "Snowflake (Preview)",
|
|
|
|
|
"slug": "/database-access/guides/snowflake/"
|
|
|
|
|
},
|
2022-02-22 23:21:46 +00:00
|
|
|
{
|
|
|
|
|
"title": "Dynamic Registration",
|
|
|
|
|
"slug": "/database-access/guides/dynamic-registration/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "High Availability",
|
|
|
|
|
"slug": "/database-access/guides/ha/"
|
|
|
|
|
}
|
2021-03-04 18:07:48 +00:00
|
|
|
]
|
|
|
|
|
},
|
2022-02-22 23:21:46 +00:00
|
|
|
{
|
|
|
|
|
"title": "Access Controls",
|
|
|
|
|
"slug": "/database-access/rbac/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Architecture",
|
|
|
|
|
"slug": "/database-access/architecture/"
|
|
|
|
|
},
|
2021-05-19 00:03:49 +00:00
|
|
|
{
|
|
|
|
|
"title": "Reference",
|
|
|
|
|
"slug": "/database-access/reference/",
|
|
|
|
|
"entries": [
|
2022-02-22 23:21:46 +00:00
|
|
|
{
|
|
|
|
|
"title": "Configuration",
|
|
|
|
|
"slug": "/database-access/reference/configuration/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "CLI",
|
|
|
|
|
"slug": "/database-access/reference/cli/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Audit Events",
|
|
|
|
|
"slug": "/database-access/reference/audit/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "AWS IAM",
|
|
|
|
|
"slug": "/database-access/reference/aws/"
|
|
|
|
|
}
|
2021-05-19 00:03:49 +00:00
|
|
|
]
|
|
|
|
|
},
|
2022-02-22 23:21:46 +00:00
|
|
|
{
|
|
|
|
|
"title": "FAQ",
|
|
|
|
|
"slug": "/database-access/faq/"
|
2022-10-04 12:02:34 +00:00
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Troubleshooting",
|
|
|
|
|
"slug": "/database-access/troubleshooting/"
|
2022-02-22 23:21:46 +00:00
|
|
|
}
|
2021-03-04 18:07:48 +00:00
|
|
|
]
|
|
|
|
|
},
|
2021-10-11 22:42:00 +00:00
|
|
|
{
|
|
|
|
|
"icon": "desktop",
|
|
|
|
|
"title": "Desktop Access",
|
|
|
|
|
"entries": [
|
2022-02-22 23:21:46 +00:00
|
|
|
{
|
|
|
|
|
"title": "Introduction",
|
|
|
|
|
"slug": "/desktop-access/introduction/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Getting Started",
|
|
|
|
|
"slug": "/desktop-access/getting-started/"
|
|
|
|
|
},
|
|
|
|
|
{
|
2022-03-16 22:35:11 +00:00
|
|
|
"title": "Access Controls",
|
|
|
|
|
"slug": "/desktop-access/rbac/"
|
|
|
|
|
},
|
2022-10-11 18:02:42 +00:00
|
|
|
{
|
|
|
|
|
"title": "Directory Sharing",
|
|
|
|
|
"slug": "/desktop-access/directory-sharing/"
|
|
|
|
|
},
|
2022-03-16 22:35:11 +00:00
|
|
|
{
|
|
|
|
|
"title": "Reference",
|
|
|
|
|
"slug": "/desktop-access/reference/",
|
|
|
|
|
"entries": [
|
|
|
|
|
{
|
|
|
|
|
"title": "Configuration",
|
|
|
|
|
"slug": "/desktop-access/reference/configuration/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Audit Events",
|
|
|
|
|
"slug": "/desktop-access/reference/audit/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Clipboard Sharing",
|
|
|
|
|
"slug": "/desktop-access/reference/clipboard/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Session Recording",
|
|
|
|
|
"slug": "/desktop-access/reference/sessions/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "CLI",
|
|
|
|
|
"slug": "/desktop-access/reference/cli/"
|
|
|
|
|
}
|
|
|
|
|
]
|
2022-02-22 23:21:46 +00:00
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Troubleshooting",
|
|
|
|
|
"slug": "/desktop-access/troubleshooting/"
|
|
|
|
|
}
|
2021-10-11 22:42:00 +00:00
|
|
|
]
|
|
|
|
|
},
|
2022-03-03 01:40:51 +00:00
|
|
|
{
|
2022-03-25 00:30:42 +00:00
|
|
|
"icon": "chip",
|
2022-03-03 01:40:51 +00:00
|
|
|
"title": "Machine ID",
|
|
|
|
|
"entries": [
|
|
|
|
|
{
|
|
|
|
|
"title": "Introduction",
|
|
|
|
|
"slug": "/machine-id/introduction/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Getting Started",
|
|
|
|
|
"slug": "/machine-id/getting-started/"
|
2022-03-09 02:42:42 +00:00
|
|
|
},
|
2022-09-01 08:50:04 +00:00
|
|
|
{
|
|
|
|
|
"title": "Architecture",
|
|
|
|
|
"slug": "/machine-id/architecture/"
|
|
|
|
|
},
|
2022-08-04 22:35:22 +00:00
|
|
|
{
|
|
|
|
|
"title": "Troubleshooting",
|
|
|
|
|
"slug": "/machine-id/troubleshooting/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "FAQ",
|
|
|
|
|
"slug": "/machine-id/faq/"
|
|
|
|
|
},
|
2022-03-13 00:42:05 +00:00
|
|
|
{
|
|
|
|
|
"title": "Reference",
|
|
|
|
|
"slug": "/machine-id/reference/",
|
|
|
|
|
"entries": [
|
|
|
|
|
{
|
|
|
|
|
"title": "Configuration",
|
|
|
|
|
"slug": "/machine-id/reference/configuration/"
|
|
|
|
|
}
|
|
|
|
|
]
|
|
|
|
|
},
|
2022-03-09 02:42:42 +00:00
|
|
|
{
|
|
|
|
|
"title": "Guides",
|
|
|
|
|
"slug": "/machine-id/guides/",
|
|
|
|
|
"entries": [
|
|
|
|
|
{
|
2022-08-12 19:50:09 +00:00
|
|
|
"title": "Ansible",
|
2022-03-09 02:42:42 +00:00
|
|
|
"slug": "/machine-id/guides/ansible/"
|
2022-03-10 02:35:27 +00:00
|
|
|
},
|
2022-11-04 00:08:41 +00:00
|
|
|
{
|
|
|
|
|
"title": "GitHub Actions",
|
|
|
|
|
"slug": "/machine-id/guides/github-actions/"
|
|
|
|
|
},
|
2022-03-10 02:35:27 +00:00
|
|
|
{
|
2022-08-12 19:50:09 +00:00
|
|
|
"title": "Jenkins",
|
2022-03-10 02:35:27 +00:00
|
|
|
"slug": "/machine-id/guides/jenkins/"
|
2022-07-07 23:50:31 +00:00
|
|
|
},
|
|
|
|
|
{
|
2022-08-12 19:50:09 +00:00
|
|
|
"title": "Databases",
|
2022-07-07 23:50:31 +00:00
|
|
|
"slug": "/machine-id/guides/databases/"
|
2022-08-12 19:50:09 +00:00
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Kubernetes",
|
|
|
|
|
"slug": "/machine-id/guides/kubernetes/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Applications",
|
|
|
|
|
"slug": "/machine-id/guides/applications/"
|
2022-10-31 18:38:51 +00:00
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Host Certificates",
|
|
|
|
|
"slug": "/machine-id/guides/host-certificate/"
|
2022-03-09 02:42:42 +00:00
|
|
|
}
|
|
|
|
|
]
|
2022-03-03 01:40:51 +00:00
|
|
|
}
|
|
|
|
|
]
|
|
|
|
|
},
|
2021-03-30 17:04:23 +00:00
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"icon": "list",
|
|
|
|
|
"title": "API",
|
2021-03-30 17:04:23 +00:00
|
|
|
"entries": [
|
2022-02-22 23:21:46 +00:00
|
|
|
{
|
|
|
|
|
"title": "Introduction",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"slug": "/api/introduction/"
|
2022-02-22 23:21:46 +00:00
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Getting Started",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"slug": "/api/getting-started/"
|
2022-02-22 23:21:46 +00:00
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Architecture",
|
|
|
|
|
"slug": "/api/architecture/"
|
|
|
|
|
}
|
2021-08-19 22:00:26 +00:00
|
|
|
]
|
2021-10-11 22:42:00 +00:00
|
|
|
},
|
2021-03-10 19:48:37 +00:00
|
|
|
{
|
|
|
|
|
"icon": "wand",
|
|
|
|
|
"title": "Preview",
|
|
|
|
|
"entries": [
|
2022-02-22 23:21:46 +00:00
|
|
|
{
|
|
|
|
|
"title": "Upcoming Releases",
|
|
|
|
|
"slug": "/preview/upcoming-releases/"
|
|
|
|
|
}
|
2021-03-10 19:48:37 +00:00
|
|
|
]
|
|
|
|
|
},
|
2021-02-10 18:07:30 +00:00
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"icon": "book",
|
|
|
|
|
"title": "Reference",
|
2021-02-10 18:07:30 +00:00
|
|
|
"entries": [
|
2022-02-22 23:21:46 +00:00
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Config File",
|
|
|
|
|
"slug": "/reference/config/"
|
2022-02-22 23:21:46 +00:00
|
|
|
},
|
2021-02-10 18:07:30 +00:00
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Config Resources",
|
|
|
|
|
"slug": "/reference/resources/"
|
2021-02-10 18:07:30 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Command Line",
|
|
|
|
|
"slug": "/reference/cli/"
|
2021-02-10 18:07:30 +00:00
|
|
|
},
|
2021-07-31 20:28:53 +00:00
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Metrics",
|
|
|
|
|
"slug": "/reference/metrics/"
|
2021-09-12 23:21:54 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Terraform Resources",
|
|
|
|
|
"slug": "/reference/terraform-provider/"
|
2021-09-24 19:35:39 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Audit Events and Records",
|
|
|
|
|
"slug": "/reference/audit/"
|
2022-04-13 16:47:12 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Authentication",
|
|
|
|
|
"slug": "/reference/authentication/"
|
|
|
|
|
},
|
2022-02-22 23:21:46 +00:00
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Storage Backends",
|
|
|
|
|
"slug": "/reference/backends/",
|
|
|
|
|
"forScopes": ["oss", "enterprise"]
|
2022-02-22 23:21:46 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Networking",
|
|
|
|
|
"slug": "/reference/networking/"
|
2022-02-22 23:21:46 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Predicate Language",
|
|
|
|
|
"slug": "/reference/predicate-language/"
|
2022-02-22 23:21:46 +00:00
|
|
|
},
|
2022-03-24 23:47:38 +00:00
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Signals",
|
|
|
|
|
"slug": "/reference/signals/"
|
2022-03-24 23:47:38 +00:00
|
|
|
},
|
2022-02-22 23:21:46 +00:00
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"title": "Helm Charts",
|
|
|
|
|
"slug": "/reference/helm-reference/",
|
|
|
|
|
"entries": [
|
|
|
|
|
{
|
|
|
|
|
"title": "teleport-cluster",
|
|
|
|
|
"slug": "/reference/helm-reference/teleport-cluster/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "teleport-kube-agent",
|
|
|
|
|
"slug": "/reference/helm-reference/teleport-kube-agent/"
|
|
|
|
|
},
|
2022-08-26 12:23:07 +00:00
|
|
|
{
|
|
|
|
|
"title": "teleport-plugin-event-handler",
|
|
|
|
|
"slug": "/reference/helm-reference/teleport-plugin-event-handler/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "teleport-plugin-jira",
|
|
|
|
|
"slug": "/reference/helm-reference/teleport-plugin-jira/"
|
2022-08-31 15:57:20 +00:00
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "teleport-plugin-pagerduty",
|
|
|
|
|
"slug": "/reference/helm-reference/teleport-plugin-pagerduty/"
|
2022-09-08 11:49:30 +00:00
|
|
|
},
|
2022-09-26 10:11:17 +00:00
|
|
|
{
|
2022-09-08 11:49:30 +00:00
|
|
|
"title": "teleport-plugin-mattermost",
|
|
|
|
|
"slug": "/reference/helm-reference/teleport-plugin-mattermost/"
|
2022-09-26 10:11:17 +00:00
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "teleport-plugin-slack",
|
|
|
|
|
"slug": "/reference/helm-reference/teleport-plugin-slack/"
|
2022-08-26 12:23:07 +00:00
|
|
|
}
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
]
|
2022-02-22 23:21:46 +00:00
|
|
|
}
|
2021-03-04 18:07:48 +00:00
|
|
|
]
|
|
|
|
|
},
|
2021-02-10 18:07:30 +00:00
|
|
|
{
|
|
|
|
|
"icon": "integrations",
|
|
|
|
|
"title": "Architecture",
|
|
|
|
|
"entries": [
|
2022-02-22 23:21:46 +00:00
|
|
|
{
|
2022-06-23 18:39:49 +00:00
|
|
|
"title": "Overview",
|
2022-02-22 23:21:46 +00:00
|
|
|
"slug": "/architecture/overview/"
|
|
|
|
|
},
|
|
|
|
|
{
|
2022-06-23 18:39:49 +00:00
|
|
|
"title": "Authentication",
|
|
|
|
|
"slug": "/architecture/authentication/"
|
2022-02-22 23:21:46 +00:00
|
|
|
},
|
|
|
|
|
{
|
2022-06-23 18:39:49 +00:00
|
|
|
"title": "Authorization",
|
|
|
|
|
"slug": "/architecture/authorization/"
|
2022-02-22 23:21:46 +00:00
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Teleport Proxy",
|
|
|
|
|
"slug": "/architecture/proxy/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Trusted Clusters",
|
2022-06-23 18:39:49 +00:00
|
|
|
"slug": "/architecture/trustedclusters/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Teleport Nodes",
|
|
|
|
|
"slug": "/architecture/nodes/"
|
2022-02-22 23:21:46 +00:00
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "TLS Routing",
|
|
|
|
|
"slug": "/architecture/tls-routing/"
|
2022-10-04 16:00:37 +00:00
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Proxy Peering",
|
|
|
|
|
"slug": "/architecture/proxy-peering/"
|
2022-02-22 23:21:46 +00:00
|
|
|
}
|
2021-02-10 18:07:30 +00:00
|
|
|
]
|
2022-02-09 21:15:49 +00:00
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"icon": "wrench",
|
|
|
|
|
"title": "Contribute",
|
|
|
|
|
"entries": [
|
|
|
|
|
{
|
|
|
|
|
"title": "Documentation",
|
|
|
|
|
"slug": "/contributing/documentation/",
|
2022-02-22 23:21:46 +00:00
|
|
|
"entries": [
|
|
|
|
|
{
|
|
|
|
|
"title": "How to Contribute",
|
|
|
|
|
"slug": "/contributing/documentation/how-to-contribute/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Creating Documentation Issues",
|
|
|
|
|
"slug": "/contributing/documentation/issues/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "Style Guide",
|
|
|
|
|
"slug": "/contributing/documentation/style-guide/"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"title": "UI Reference",
|
|
|
|
|
"slug": "/contributing/documentation/reference/"
|
|
|
|
|
}
|
2022-02-09 21:15:49 +00:00
|
|
|
]
|
|
|
|
|
}
|
|
|
|
|
]
|
2021-02-10 18:07:30 +00:00
|
|
|
}
|
|
|
|
|
],
|
|
|
|
|
"variables": {
|
2021-04-08 22:56:53 +00:00
|
|
|
"version": "7.0",
|
2021-06-02 22:46:59 +00:00
|
|
|
"terraform": {
|
2022-04-02 05:03:15 +00:00
|
|
|
"version": "1.0.0"
|
2021-06-02 22:46:59 +00:00
|
|
|
},
|
2021-08-23 18:30:02 +00:00
|
|
|
"presets": {
|
|
|
|
|
"tokens": {
|
|
|
|
|
"first": "abcd123-insecure-do-not-use-this",
|
|
|
|
|
"second": "efgh456-insecure-do-not-use-this",
|
|
|
|
|
"third": "ijkl789-insecure-do-not-use-this"
|
2022-04-18 20:14:25 +00:00
|
|
|
},
|
|
|
|
|
"ca_pin": "sha256:abdc1245efgh5678abdc1245efgh5678abdc1245efgh5678abdc1245efgh5678"
|
2021-08-23 18:30:02 +00:00
|
|
|
},
|
2021-07-31 20:28:53 +00:00
|
|
|
"fedramp": {
|
|
|
|
|
"control_url": "https://csrc.nist.gov/Projects/risk-management/sp800-53-controls/release-search#!/control?version=5.1&number="
|
|
|
|
|
},
|
2021-07-26 16:14:26 +00:00
|
|
|
"soc2": {
|
2022-08-10 14:09:03 +00:00
|
|
|
"last_report": "August 9th, 2022"
|
2021-07-26 16:14:26 +00:00
|
|
|
},
|
|
|
|
|
"cloud": {
|
2022-11-03 22:49:54 +00:00
|
|
|
"version": "10.3.6",
|
2022-08-15 20:37:26 +00:00
|
|
|
"major_version": "10",
|
2021-07-26 16:14:26 +00:00
|
|
|
"sla": {
|
|
|
|
|
"monthly_percentage": "99.5%",
|
|
|
|
|
"monthly_downtime": "3 hours 40 minutes"
|
|
|
|
|
}
|
|
|
|
|
},
|
2021-07-08 20:36:30 +00:00
|
|
|
"fluentd": {
|
|
|
|
|
"version": "1.12.4"
|
|
|
|
|
},
|
|
|
|
|
"docker": {
|
2021-07-15 18:56:23 +00:00
|
|
|
"version": "20.10.7",
|
|
|
|
|
"compose": {
|
|
|
|
|
"version": "1.25.0"
|
|
|
|
|
}
|
2021-07-08 20:36:30 +00:00
|
|
|
},
|
2021-08-23 18:30:02 +00:00
|
|
|
"helm": {
|
|
|
|
|
"version": "3.4.2"
|
|
|
|
|
},
|
2021-05-17 13:38:13 +00:00
|
|
|
"kubernetes": {
|
|
|
|
|
"major_version": "1",
|
|
|
|
|
"minor_version": "17"
|
|
|
|
|
},
|
2021-09-17 01:23:24 +00:00
|
|
|
"ansible": {
|
|
|
|
|
"min_version": "2.9.6"
|
|
|
|
|
},
|
2021-07-12 06:12:21 +00:00
|
|
|
"mongodb": {
|
|
|
|
|
"min_version": "3.6"
|
|
|
|
|
},
|
2021-02-10 18:07:30 +00:00
|
|
|
"teleport": {
|
2022-07-13 18:28:31 +00:00
|
|
|
"major_version": "11",
|
2022-04-13 20:14:25 +00:00
|
|
|
"version": "9.0.4",
|
2022-04-11 22:50:33 +00:00
|
|
|
"golang": "1.17",
|
2021-02-10 18:07:30 +00:00
|
|
|
"plugin": {
|
2022-09-28 21:51:50 +00:00
|
|
|
"version": "10.2.6"
|
2021-02-10 18:07:30 +00:00
|
|
|
},
|
2021-05-17 13:38:13 +00:00
|
|
|
"helm_repo_url": "https://charts.releases.teleport.dev",
|
2022-08-19 15:24:15 +00:00
|
|
|
"latest_oss_docker_image": "public.ecr.aws/gravitational/teleport:9.1.2",
|
|
|
|
|
"latest_ent_docker_image": "public.ecr.aws/gravitational/teleport-ent:9.1.2"
|
2021-02-10 18:07:30 +00:00
|
|
|
}
|
2021-03-11 17:02:14 +00:00
|
|
|
},
|
|
|
|
|
"redirects": [
|
2022-06-23 18:39:49 +00:00
|
|
|
{
|
|
|
|
|
"source": "/architecture/users/",
|
|
|
|
|
"destination": "/architecture/authorization/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
2021-09-22 03:22:21 +00:00
|
|
|
{
|
|
|
|
|
"source": "/production/",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"destination": "/deploy-a-cluster/deployments/",
|
2021-09-22 03:22:21 +00:00
|
|
|
"permanent": true
|
|
|
|
|
},
|
2021-09-20 17:22:12 +00:00
|
|
|
{
|
|
|
|
|
"source": "/admin-guide/",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"destination": "/management/admin/",
|
2021-09-20 17:22:12 +00:00
|
|
|
"permanent": true
|
|
|
|
|
},
|
2021-09-13 18:49:17 +00:00
|
|
|
{
|
|
|
|
|
"source": "/trustedclusters/",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"destination": "/management/admin/trustedclusters/",
|
2021-09-13 18:49:17 +00:00
|
|
|
"permanent": true
|
|
|
|
|
},
|
2021-08-19 22:00:26 +00:00
|
|
|
{
|
|
|
|
|
"source": "/reference/api/architecture/",
|
|
|
|
|
"destination": "/api/architecture/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/reference/api/getting-started/",
|
|
|
|
|
"destination": "/api/getting-started/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/reference/api/introduction/",
|
|
|
|
|
"destination": "/api/introduction/",
|
|
|
|
|
"permanent": true
|
2021-10-11 22:42:00 +00:00
|
|
|
},
|
2021-08-19 22:00:26 +00:00
|
|
|
{
|
|
|
|
|
"source": "/metrics-logs-reference/",
|
2022-10-14 20:05:07 +00:00
|
|
|
"destination": "/management/diagnostics/metrics/",
|
2021-08-19 22:00:26 +00:00
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/config-reference/",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"destination": "/reference/config/",
|
2021-08-19 22:00:26 +00:00
|
|
|
"permanent": true
|
2021-10-11 22:42:00 +00:00
|
|
|
},
|
2021-08-19 22:00:26 +00:00
|
|
|
{
|
|
|
|
|
"source": "/cli-docs/",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"destination": "/reference/cli/",
|
2021-08-19 22:00:26 +00:00
|
|
|
"permanent": true
|
|
|
|
|
},
|
2021-07-31 20:28:53 +00:00
|
|
|
{
|
|
|
|
|
"source": "/enterprise/ssh-kubernetes-fedramp/",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"destination": "/access-controls/compliance-frameworks/fedramp/",
|
2021-07-31 20:28:53 +00:00
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/enterprise/sso/ssh-one-login/",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"destination": "/access-controls/sso/one-login/",
|
2021-07-31 20:28:53 +00:00
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/enterprise/sso/ssh-okta/",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"destination": "/access-controls/sso/okta/",
|
2021-07-31 20:28:53 +00:00
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/enterprise/sso/ssh-google-workspace/",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"destination": "/access-controls/sso/google-workspace/",
|
2021-07-31 20:28:53 +00:00
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/enterprise/sso/ssh-azuread/",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"destination": "/access-controls/sso/azuread/",
|
2021-07-31 20:28:53 +00:00
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/enterprise/sso/ssh-adfs/",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"destination": "/access-controls/sso/adfs/",
|
2021-07-31 20:28:53 +00:00
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/enterprise/sso/ssh-sso/",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"destination": "/access-controls/sso/",
|
2022-05-17 20:26:34 +00:00
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/enterprise/ssh_sso/",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"destination": "/access-controls/sso/",
|
2021-07-31 20:28:53 +00:00
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/enterprise/quickstart-enterprise/",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"destination": "/deploy-a-cluster/teleport-enterprise/getting-started/",
|
2021-07-31 20:28:53 +00:00
|
|
|
"permanent": true
|
|
|
|
|
},
|
2021-07-16 20:46:55 +00:00
|
|
|
{
|
|
|
|
|
"source": "/gcp-guide/",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"destination": "/deploy-a-cluster/deployments/gcp/",
|
2021-07-16 20:46:55 +00:00
|
|
|
"permanent": true
|
2021-10-11 22:42:00 +00:00
|
|
|
},
|
2021-07-16 20:46:55 +00:00
|
|
|
{
|
|
|
|
|
"source": "/ibm-cloud-guide/",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"destination": "/deploy-a-cluster/deployments/ibm/",
|
2021-07-16 20:46:55 +00:00
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/aws-terraform-guide/",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"destination": "/deploy-a-cluster/deployments/aws-terraform/",
|
2021-07-16 20:46:55 +00:00
|
|
|
"permanent": true
|
|
|
|
|
},
|
2021-07-15 18:56:23 +00:00
|
|
|
{
|
|
|
|
|
"source": "/setup/guides/docker-compose/",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"destination": "/management/guides/docker/",
|
2021-07-15 18:56:23 +00:00
|
|
|
"permanent": true
|
|
|
|
|
},
|
2021-04-15 00:06:57 +00:00
|
|
|
{
|
|
|
|
|
"source": "/cloud/",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"destination": "/deploy-a-cluster/teleport-cloud/",
|
2021-04-15 00:06:57 +00:00
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/application-access/",
|
|
|
|
|
"destination": "/application-access/introduction/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/database-access/",
|
|
|
|
|
"destination": "/database-access/introduction/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/kubernetes-access/",
|
|
|
|
|
"destination": "/kubernetes-access/introduction/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
2021-03-30 17:04:23 +00:00
|
|
|
{
|
|
|
|
|
"source": "/enterprise/ssh-rbac/",
|
|
|
|
|
"destination": "/access-controls/introduction/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
2021-03-11 17:02:14 +00:00
|
|
|
{
|
|
|
|
|
"source": "/quickstart/",
|
|
|
|
|
"destination": "/getting-started/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/preview/database-access/",
|
|
|
|
|
"destination": "/database-access/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/preview/cloud/",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"destination": "/deploy-a-cluster/teleport-cloud/",
|
2021-03-11 17:02:14 +00:00
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/kubernetes-ssh/",
|
|
|
|
|
"destination": "/kubernetes-access/",
|
|
|
|
|
"permanent": true
|
2021-05-27 02:36:48 +00:00
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/features/ssh-pam/",
|
|
|
|
|
"destination": "/server-access/guides/ssh-pam/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/openssh-teleport/",
|
|
|
|
|
"destination": "/server-access/guides/openssh/",
|
|
|
|
|
"permanent": true
|
2021-06-02 19:21:54 +00:00
|
|
|
},
|
2021-06-18 04:00:34 +00:00
|
|
|
{
|
|
|
|
|
"source": "/features/enhanced-session-recording/",
|
|
|
|
|
"destination": "/server-access/guides/bpf-session-recording/",
|
|
|
|
|
"permanent": true
|
2021-06-20 03:20:46 +00:00
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/quickstart-docker/",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"destination": "/management/guides/docker/",
|
2021-06-20 03:20:46 +00:00
|
|
|
"permanent": true
|
2021-11-04 22:52:35 +00:00
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/database-access/guides/postgres-aws/",
|
|
|
|
|
"destination": "/database-access/guides/rds/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/database-access/guides/mysql-aws/",
|
|
|
|
|
"destination": "/database-access/guides/rds/",
|
|
|
|
|
"permanent": true
|
2022-02-09 21:15:49 +00:00
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/docs/",
|
|
|
|
|
"destination": "/contributing/documentation/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/docs/best-practices/",
|
|
|
|
|
"destination": "/contributing/documentation/",
|
|
|
|
|
"permanent": true
|
2022-03-18 15:22:08 +00:00
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/kubernetes-access/guides/migration/",
|
|
|
|
|
"destination": "/kubernetes-access/introduction/",
|
|
|
|
|
"permanent": true
|
2022-03-23 21:09:26 +00:00
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/guides/joining-nodes-aws/",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"destination": "/management/guides/joining-nodes-aws-iam/",
|
2022-03-23 21:09:26 +00:00
|
|
|
"permanent": true
|
2022-04-13 16:47:12 +00:00
|
|
|
},
|
|
|
|
|
{
|
2022-07-18 16:43:52 +00:00
|
|
|
"source": "/setup/reference/license/",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"destination": "/deploy-a-cluster/teleport-enterprise/license/",
|
2022-04-13 16:47:12 +00:00
|
|
|
"permanent": true
|
2022-05-11 23:24:17 +00:00
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/architecture/",
|
|
|
|
|
"destination": "/architecture/overview/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/intro/",
|
|
|
|
|
"destination": "/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/api-reference/",
|
|
|
|
|
"destination": "/api/getting-started/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/server-access/guides/ansible/",
|
|
|
|
|
"destination": "/machine-id/guides/ansible/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
2022-07-20 08:32:53 +00:00
|
|
|
{
|
|
|
|
|
"source": "/server-access/guides/tsh/",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"destination": "/connect-your-client/tsh/",
|
2022-07-20 08:32:53 +00:00
|
|
|
"permanent": true
|
|
|
|
|
},
|
2022-05-11 23:24:17 +00:00
|
|
|
{
|
|
|
|
|
"source": "/cluster/",
|
|
|
|
|
"destination": "/kubernetes-access/guides/multiple-clusters/",
|
|
|
|
|
"permanent": true
|
2022-06-03 15:25:20 +00:00
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/application-access/guides/jwt/",
|
|
|
|
|
"destination": "/application-access/jwt/",
|
|
|
|
|
"permanent": true
|
2022-06-21 15:32:16 +00:00
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/getting-started/digitalocean/",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"destination": "/deploy-a-cluster/deployments/digitalocean/",
|
2022-06-21 15:32:16 +00:00
|
|
|
"permanent": true
|
2022-06-22 19:29:32 +00:00
|
|
|
},
|
|
|
|
|
{
|
2022-07-18 16:43:52 +00:00
|
|
|
"source": "/kubernetes-access/getting-started/agent/",
|
|
|
|
|
"destination": "/kubernetes-access/getting-started/",
|
2022-06-22 19:29:32 +00:00
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
2022-07-18 16:43:52 +00:00
|
|
|
"source": "/kubernetes-access/getting-started/cluster/",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"destination": "/deploy-a-cluster/helm-deployments/kubernetes-cluster/",
|
2022-06-22 19:29:32 +00:00
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
2022-07-18 16:43:52 +00:00
|
|
|
"source": "/kubernetes-access/getting-started/local/",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"destination": "/try-out-teleport/local-kubernetes/",
|
2022-06-22 19:29:32 +00:00
|
|
|
"permanent": true
|
2022-06-23 15:25:27 +00:00
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/kubernetes-access/helm/guides/",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"destination": "/deploy-a-cluster/helm-deployments/",
|
2022-06-23 15:25:27 +00:00
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/kubernetes-access/helm/guides/aws/",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"destination": "/deploy-a-cluster/helm-deployments/aws/",
|
2022-06-23 15:25:27 +00:00
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/kubernetes-access/helm/guides/custom/",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"destination": "/deploy-a-cluster/helm-deployments/custom/",
|
2022-06-23 15:25:27 +00:00
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/kubernetes-access/helm/guides/digitalocean/",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"destination": "/deploy-a-cluster/helm-deployments/digitalocean/",
|
2022-06-23 15:25:27 +00:00
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/kubernetes-access/helm/guides/gcp/",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"destination": "/deploy-a-cluster/helm-deployments/gcp/",
|
2022-06-23 15:25:27 +00:00
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/kubernetes-access/helm/guides/migration/",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"destination": "/deploy-a-cluster/helm-deployments/migration/",
|
2022-06-23 15:25:27 +00:00
|
|
|
"permanent": true
|
2022-06-24 21:38:59 +00:00
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/kubernetes-access/helm/reference/",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"destination": "/reference/helm-reference/",
|
2022-06-24 21:38:59 +00:00
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/kubernetes-access/helm/reference/teleport-cluster/",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"destination": "/reference/helm-reference/teleport-cluster/",
|
2022-06-24 21:38:59 +00:00
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/kubernetes-access/helm/reference/teleport-kube-agent/",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"destination": "/reference/helm-reference/teleport-kube-agent/",
|
2022-06-24 21:38:59 +00:00
|
|
|
"permanent": true
|
2022-07-06 20:30:51 +00:00
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/access-controls/guides/u2f/",
|
|
|
|
|
"destination": "/access-controls/guides/webauthn/",
|
|
|
|
|
"permanent": true
|
2022-07-18 19:46:35 +00:00
|
|
|
},
|
|
|
|
|
{
|
2022-07-20 08:32:53 +00:00
|
|
|
"source": "/setup/admin/graceful-restarts/",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"destination": "/management/admin/upgrading-the-teleport-binary/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/enterprise/workflow/",
|
|
|
|
|
"destination": "/access-controls/access-requests/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/enterprise/workflow/ssh-approval-mattermost/",
|
|
|
|
|
"destination": "/access-controls/access-request-plugins/ssh-approval-mattermost/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
2022-08-26 21:50:06 +00:00
|
|
|
"source": "/enterprise/workflow/ssh-approval-pagerduty/",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"destination": "/access-controls/access-request-plugins/ssh-approval-pagerduty/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/enterprise/workflow/ssh-approval-jira-server/",
|
2022-11-04 20:28:58 +00:00
|
|
|
"destination": "/access-controls/access-request-plugins/ssh-approval-jira/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/enterprise/workflow/ssh-approval-jira-cloud/",
|
|
|
|
|
"destination": "/access-controls/access-request-plugins/ssh-approval-jira/",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/enterprise/workflow/ssh-approval-jira-cloud/",
|
2022-11-04 20:28:58 +00:00
|
|
|
"destination": "/access-controls/access-request-plugins/ssh-approval-jira/",
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/enterprise/workflow/ssh-approval-slack/",
|
|
|
|
|
"destination": "/access-controls/access-request-plugins/ssh-approval-slack/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/enterprise/workflow/resource-requests/",
|
|
|
|
|
"destination": "/access-controls/access-requests/resource-requests/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/enterprise/workflow/role-requests/",
|
|
|
|
|
"destination": "/access-controls/access-requests/role-requests/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/user-manual/",
|
|
|
|
|
"destination": "/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/enterprise/fedramp/",
|
|
|
|
|
"destination": "/access-controls/compliance-frameworks/fedramp/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/enterprise/soc2/",
|
|
|
|
|
"destination": "/access-controls/compliance-frameworks/soc2/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/enterprise/sso/",
|
|
|
|
|
"destination": "/access-controls/sso/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/enterprise/sso/adfs/",
|
|
|
|
|
"destination": "/access-controls/sso/adfs/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/enterprise/sso/azuread/",
|
|
|
|
|
"destination": "/access-controls/sso/azuread/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/admin/github-sso/",
|
|
|
|
|
"destination": "/access-controls/sso/github-sso/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/enterprise/sso/gitlab/",
|
|
|
|
|
"destination": "/access-controls/sso/gitlab/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/enterprise/sso/google-workspace/",
|
|
|
|
|
"destination": "/access-controls/sso/google-workspace/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/enterprise/sso/oidc/",
|
|
|
|
|
"destination": "/access-controls/sso/oidc/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/enterprise/sso/okta/",
|
|
|
|
|
"destination": "/access-controls/sso/okta/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/enterprise/sso/one-login/",
|
|
|
|
|
"destination": "/access-controls/sso/one-login/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/database-access/guides/gui-clients/",
|
|
|
|
|
"destination": "/connect-your-client/gui-clients/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/use-teleport/teleport-connect/",
|
|
|
|
|
"destination": "/connect-your-client/teleport-connect/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/use-teleport/tsh/",
|
|
|
|
|
"destination": "/connect-your-client/tsh/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/deployments/",
|
|
|
|
|
"destination": "/deploy-a-cluster/deployments/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/deployments/aws-terraform/",
|
|
|
|
|
"destination": "/deploy-a-cluster/deployments/aws-terraform/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/deployments/digitalocean/",
|
|
|
|
|
"destination": "/deploy-a-cluster/deployments/digitalocean/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/deployments/gcp/",
|
|
|
|
|
"destination": "/deploy-a-cluster/deployments/gcp/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/deployments/ibm/",
|
|
|
|
|
"destination": "/deploy-a-cluster/deployments/ibm/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/helm-deployments/",
|
|
|
|
|
"destination": "/deploy-a-cluster/helm-deployments/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/helm-deployments/aws/",
|
|
|
|
|
"destination": "/deploy-a-cluster/helm-deployments/aws/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/helm-deployments/custom/",
|
|
|
|
|
"destination": "/deploy-a-cluster/helm-deployments/custom/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/helm-deployments/digitalocean/",
|
|
|
|
|
"destination": "/deploy-a-cluster/helm-deployments/digitalocean/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/helm-deployments/gcp/",
|
|
|
|
|
"destination": "/deploy-a-cluster/helm-deployments/gcp/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/getting-started/kubernetes-cluster/",
|
|
|
|
|
"destination": "/deploy-a-cluster/helm-deployments/kubernetes-cluster/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/helm-deployments/migration/",
|
|
|
|
|
"destination": "/deploy-a-cluster/helm-deployments/migration/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/getting-started/linux-server/",
|
|
|
|
|
"destination": "/deploy-a-cluster/open-source/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/cloud/architecture/",
|
|
|
|
|
"destination": "/deploy-a-cluster/teleport-cloud/architecture/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/cloud/downloads/",
|
|
|
|
|
"destination": "/deploy-a-cluster/teleport-cloud/downloads/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/cloud/faq/",
|
|
|
|
|
"destination": "/deploy-a-cluster/teleport-cloud/faq/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/cloud/getting-started/",
|
|
|
|
|
"destination": "/deploy-a-cluster/teleport-cloud/getting-started/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/cloud/introduction/",
|
|
|
|
|
"destination": "/deploy-a-cluster/teleport-cloud/introduction/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/enterprise/getting-started/",
|
|
|
|
|
"destination": "/deploy-a-cluster/teleport-enterprise/getting-started/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/enterprise/hsm/",
|
|
|
|
|
"destination": "/deploy-a-cluster/teleport-enterprise/hsm/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/enterprise/introduction/",
|
|
|
|
|
"destination": "/deploy-a-cluster/teleport-enterprise/introduction/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/enterprise/license/",
|
|
|
|
|
"destination": "/deploy-a-cluster/teleport-enterprise/license/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/admin/",
|
|
|
|
|
"destination": "/management/admin/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/admin/adding-nodes/",
|
|
|
|
|
"destination": "/management/admin/adding-nodes/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/admin/daemon/",
|
|
|
|
|
"destination": "/management/admin/daemon/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/admin/labels/",
|
|
|
|
|
"destination": "/management/admin/labels/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/admin/troubleshooting/",
|
|
|
|
|
"destination": "/management/admin/troubleshooting/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/admin/trustedclusters/",
|
|
|
|
|
"destination": "/management/admin/trustedclusters/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/admin/upgrading-the-teleport-binary/",
|
|
|
|
|
"destination": "/management/admin/upgrading-the-teleport-binary/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/admin/users/",
|
|
|
|
|
"destination": "/management/admin/users/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/guides/",
|
|
|
|
|
"destination": "/management/guides/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/guides/docker/",
|
|
|
|
|
"destination": "/management/guides/docker/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/guides/ec2-tags/",
|
|
|
|
|
"destination": "/management/guides/ec2-tags/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/guides/fluentd/",
|
|
|
|
|
"destination": "/management/guides/fluentd/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/guides/joining-nodes-aws-ec2/",
|
|
|
|
|
"destination": "/management/guides/joining-nodes-aws-ec2/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/guides/joining-nodes-aws-iam/",
|
|
|
|
|
"destination": "/management/guides/joining-nodes-aws-iam/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/guides/ssh-key-extensions/",
|
|
|
|
|
"destination": "/management/guides/ssh-key-extensions/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/guides/teleport-operator/",
|
|
|
|
|
"destination": "/management/guides/teleport-operator/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/guides/terraform-provider/",
|
|
|
|
|
"destination": "/management/guides/terraform-provider/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/operations/",
|
|
|
|
|
"destination": "/management/operations/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/operations/backup-restore/",
|
|
|
|
|
"destination": "/management/operations/backup-restore/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/operations/ca-rotation/",
|
|
|
|
|
"destination": "/management/operations/ca-rotation/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
2022-10-04 16:00:37 +00:00
|
|
|
{
|
|
|
|
|
"source": "/setup/operations/proxy-peering/",
|
|
|
|
|
"destination": "/management/operations/proxy-peering/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
{
|
|
|
|
|
"source": "/setup/operations/scaling/",
|
|
|
|
|
"destination": "/management/operations/scaling/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/operations/tls-routing/",
|
|
|
|
|
"destination": "/management/operations/tls-routing/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/operations/upgrading/",
|
|
|
|
|
"destination": "/management/operations/upgrading/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/security/",
|
|
|
|
|
"destination": "/management/security/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/security/reduce-blast-radius/",
|
|
|
|
|
"destination": "/management/security/reduce-blast-radius/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/reference/audit/",
|
|
|
|
|
"destination": "/reference/audit/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/reference/authentication/",
|
|
|
|
|
"destination": "/reference/authentication/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/reference/backends/",
|
|
|
|
|
"destination": "/reference/backends/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/reference/cli/",
|
|
|
|
|
"destination": "/reference/cli/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/reference/config/",
|
|
|
|
|
"destination": "/reference/config/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/helm-reference/",
|
|
|
|
|
"destination": "/reference/helm-reference/",
|
|
|
|
|
"permanent": true
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"source": "/setup/helm-reference/teleport-cluster/",
|
|
|
|
|
"destination": "/reference/helm-reference/teleport-cluster/",
|
2022-07-20 08:32:53 +00:00
|
|
|
"permanent": true
|
2022-08-01 17:44:36 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"source": "/setup/helm-reference/teleport-kube-agent/",
|
|
|
|
|
"destination": "/reference/helm-reference/teleport-kube-agent/",
|
|
|
|
|
"permanent": true
|
2022-08-01 17:44:36 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"source": "/setup/reference/metrics/",
|
|
|
|
|
"destination": "/reference/metrics/",
|
|
|
|
|
"permanent": true
|
2022-08-01 17:44:36 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"source": "/setup/reference/networking/",
|
|
|
|
|
"destination": "/reference/networking/",
|
|
|
|
|
"permanent": true
|
2022-08-01 17:44:36 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"source": "/setup/reference/predicate-language/",
|
|
|
|
|
"destination": "/reference/predicate-language/",
|
|
|
|
|
"permanent": true
|
2022-08-01 17:44:36 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"source": "/setup/reference/resources/",
|
|
|
|
|
"destination": "/reference/resources/",
|
|
|
|
|
"permanent": true
|
2022-08-01 17:44:36 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"source": "/setup/reference/signals/",
|
|
|
|
|
"destination": "/reference/signals/",
|
|
|
|
|
"permanent": true
|
2022-08-01 17:44:36 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"source": "/setup/reference/terraform-provider/",
|
|
|
|
|
"destination": "/reference/terraform-provider/",
|
|
|
|
|
"permanent": true
|
2022-08-01 17:44:36 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"source": "/getting-started/docker-compose/",
|
|
|
|
|
"destination": "/try-out-teleport/docker-compose/",
|
|
|
|
|
"permanent": true
|
2022-08-12 20:55:13 +00:00
|
|
|
},
|
|
|
|
|
{
|
Organize docs guide sections chronologically (#15357)
* Organize docs guide sections chronologically
This change aims to make docs navigation easier by organizing some docs
sections according to the sequence of steps a user would take to set up
Teleport.
The current docs organization uses a variety of categories and schemes
to organize the docs. For example, there is a "Home" section that
includes the Changelog, Installation page, and Getting Started guides; a
"Setup" section that includes references and admin guides; and
edition-specific sections (Enterprise, Cloud). For a user who is setting
up Teleport--or who has already done some setup work and wants more
advanced instructions--it's difficult to know where in the docs to find
the right information.
This change organizes our how-to guides into the following categories
that describe the process of setting up Teleport:
- Try out Teleport
- Deploy a Cluster (including choosing an edition)
- Configure Access (including SSO, RBAC, and Access Requests)
- Manage your Cluster (admin guides, operations, etc.)
- Use Teleport (this section already exists)
I moved the Reference section after this chronology, since users can
access the reference guides anywhere in the setup process.
As part of the change, I have also moved the content from the
"Enterprise" and "Cloud" sections into "Deploy a Cluster", since this
content has to do with how to deploy a specific edition of Teleport.
Note that this change does _not_ attempt to reorganize our
protocol-specific sections. While adding resources is part of the
Teleport setup process, we have a lot of content in our
protocol-specific sections, and moving it all into a single section
related to adding resources to a cluster would (a) exceed the maximum
depth for subsections in the nav bar and (b) cause more confusion than
it alleviates.
* Respond to PR feedback
- Create a "Compliance Frameworks" section of "Configure Access" with
the FedRAMP and SOC 2 guides
- Rename "Use Teleport" to "Connect your Client"
- Move the database GUI client guide into "Connect your Client"
* Add redirects
* Fix linter issues
2022-08-22 19:45:32 +00:00
|
|
|
"source": "/getting-started/local-kubernetes/",
|
|
|
|
|
"destination": "/try-out-teleport/local-kubernetes/",
|
|
|
|
|
"permanent": true
|
2021-06-20 03:20:46 +00:00
|
|
|
}
|
2021-03-11 17:02:14 +00:00
|
|
|
]
|
2022-06-23 18:39:49 +00:00
|
|
|
}
|