Teleport — Secure Infrastructure Access Platform

What it is

Teleport is an open-source platform that provides identity-based access to servers, Kubernetes clusters, databases, and internal web applications. It replaces traditional VPNs and SSH key management with short-lived certificates, session recording, and role-based access control.

Teleport targets DevOps teams and security engineers who need auditable access to production infrastructure without distributing static credentials. It supports SSH, Kubernetes, PostgreSQL, MySQL, MongoDB, Redis, and web app proxying.

How it saves time or tokens

Without Teleport, onboarding a new engineer means distributing SSH keys, configuring VPN credentials, managing jump hosts, and hoping nobody leaks a private key. Teleport centralizes all access through a single identity provider. Certificate-based auth means credentials auto-expire -- no more rotating SSH keys manually.

For compliance, every session is recorded and searchable. Audit logs show who accessed what, when, and what commands they ran.

How to use

1. Install and start a Teleport cluster:

# Install Teleport
curl https://goteleport.com/static/install.sh | bash

# Configure and start
sudo teleport configure --cluster-name=my-cluster -o /etc/teleport.yaml
sudo teleport start

1. Add nodes (servers) to the cluster:

# On each server
teleport node configure --token=<join-token> --proxy=teleport.example.com
teleport start

1. Access via the web UI or CLI:

# Login
tsh login --proxy=teleport.example.com

# SSH to a node
tsh ssh user@node-name

# Access Kubernetes
tsh kube login my-cluster
kubectl get pods

Example

# List available servers
tsh ls
# Node Name       Address        Labels
# ----------      ----------     -------
# web-prod-01     10.0.1.5:3022  env=prod,role=web
# db-staging-01   10.0.2.8:3022  env=staging,role=db

# SSH with session recording
tsh ssh admin@web-prod-01
# Session is automatically recorded and auditable

# Access a database through Teleport
tsh db connect --db-name=mydb postgres-prod

# Kubernetes access
tsh kube login prod-cluster
kubectl get deployments

Related on TokRepo

• AI Tools for DevOps -- Infrastructure automation tools for modern teams
• AI Tools for Security -- Security-focused tools and frameworks

Common pitfalls

• Teleport requires a running auth server (the cluster). If the auth server goes down, new connections cannot be established. Run it in HA mode for production.
• Certificate TTLs default to 12 hours. Adjust this in the role configuration if your workflows need longer sessions.
• Database access requires configuring Teleport as a database proxy. Each database type (Postgres, MySQL, MongoDB) has its own setup steps.