mirror of
https://github.com/gravitational/teleport.git
synced 2026-11-04 10:25:32 +08:00
Paul Gottschling
5ba910b38f
* Provide more context in the docs intro page Closes #22469 The current docs landing page does not include enough context for new readers. After the general description of Teleport, the rest of the landing page is series of links, with little guidance for what a new user should do first (or what an intermediate user should do after completing the initial setup steps). This change takes a more narrative approach to the landing page, briefly describing the content of each top-level docs section and putting it in context with the rest of the docs. This also helps users find the right top-level docs section for their needs, since otherwise the only way to do this is to visit each section. This change is also more opinionated about which guide new users should begin with. It recommends the guide to getting started with Teleport Cloud, since this doesn't require setting up a Teleport cluster and helps a user register a resource quickly. The landing page links to the introduction page of each top-level docs section. If a section does not have an introduction page, this change adds one. * Respond to zmb3 feedback Reorder list items * Linter fixes * Respond to alexfornuto PR feedback
48 lines
1.7 KiB
Plaintext
48 lines
1.7 KiB
Plaintext
---
|
|
title: "Manage your Cluster"
|
|
description: "Guides for performing day-two operations on your Teleport cluster."
|
|
layout: tocless-doc
|
|
---
|
|
|
|
In this section, you can find guides on managing a Teleport cluster after
|
|
deploying it.
|
|
|
|
## Export audit events
|
|
|
|
Teleport's Auth Service maintains an audit log that tracks events in your
|
|
cluster, such when a user begins an SSH session or attempts to authenticate. You
|
|
can get insight into how users are interacting with your Teleport cluster by
|
|
exporting audit events to your log management solution. See how in the
|
|
[Exporting Audit Events](./export-audit-events.mdx) guides.
|
|
|
|
## Security
|
|
|
|
While Teleport is designed with security in mind, there are steps you can take
|
|
to ensure that your cluster is as secure as possible. Read about these in the
|
|
[Security](./security.mdx) section.
|
|
|
|
## Admin guides
|
|
|
|
The [Admin Guides](./admin.mdx) section describes how to perform routine
|
|
administrative tasks in your Teleport cluster, such as upgrading the `teleport`
|
|
binary or adding labels to Teleport resources.
|
|
|
|
## Operations
|
|
|
|
The [Operations](./operations.mdx) section describes how to perform critical,
|
|
infrequent tasks such as achieving scalability, upgrading a cluster, and
|
|
rotating Teleport's certificate authority.
|
|
|
|
## Integrations
|
|
|
|
Teleport integrates with third-party software in order to enable secure access
|
|
to your infrastructure. The [Integrations](./guides.mdx) section describes
|
|
Teleport's Kubernetes Operator, Terraform Provider, and other integrations.
|
|
|
|
## Diagnostics
|
|
|
|
To get visibility into the performance of the Teleport services running in your
|
|
infrastructure, you can use Teleport's built-in metrics, traces, and profiling.
|
|
Learn more in the [Diagnostics](./diagnostics.mdx) section.
|
|
|