Skip to content

docs: update agent architecture reference to users #60267

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 17, 2025
Merged

docs: update agent architecture reference to users #60267

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/pages/reference/architecture/architecture.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,7 +64,7 @@ Administrators can **enroll** infrastructure resources with a Teleport cluster
to provide secure access, RBAC, and auditing. There are three ways to enroll
infrastructure resources with a Teleport cluster:

- **Teleport Agents** proxy traffic from human users to and from
- **Teleport Agents** proxy traffic from users to and from
Teleport-protected infrastructure resources.
- **Machine ID Bots** receive short-lived credentials from the `tbot` binary so
service accounts can access infrastructure.
Expand All @@ -74,7 +74,7 @@ infrastructure resources with a Teleport cluster:

### Teleport Agents

Teleport Agents proxy traffic from users to resources in your infrastructure.
Teleport Agents proxy traffic from users, human or machine, to resources in your infrastructure.
Agents are instances of the `teleport` binary configured to run certain
services, e.g., the Teleport SSH Service and Teleport Kubernetes Service, and
administrators deploy Agents on their own infrastructure.
Expand Down
Loading