Integrations Overview

Integrations Overview

SSH-KLM integrates with infrastructure automation tools, cloud providers, and identity systems to provide centralized SSH key management across your environment.

---

Supported Integrations

Integration	Type	Use Case
Ansible	Configuration Management	Automate SSH key distribution and rotation across hosts
Terraform	Infrastructure as Code	Provision SSH keys during cloud infrastructure deployment
AWS EC2	Cloud Provider	Discover and manage SSH key pairs on EC2 instances
Azure VMs	Cloud Provider	Manage SSH keys on Azure Virtual Machines
GCP Compute	Cloud Provider	Manage OS Login and project-level SSH keys
LDAP / Active Directory	Identity Provider	Sync SSH public keys with directory services for centralized authentication
HashiCorp Boundary	Access Management	Integrate SSH key lifecycle with zero-trust access proxy
Teleport	Access Management	Manage SSH certificates alongside Teleport’s certificate authority

---

Integration Architecture

All integrations follow a common pattern:

SSH-KLM Platform
    ├── API (REST / gRPC)
    ├── Agent (on-host discovery)
    └── Webhooks (event-driven)

Integration Layer
    ├── Ansible / Terraform (push-based)
    ├── Cloud APIs (discovery)
    └── LDAP / AD (sync)

---

Choosing an Integration

Automation & Provisioning

Use Ansible or Terraform when you need to:

• Distribute authorized_keys to hosts at scale
• Rotate SSH keys on a schedule
• Provision keys during infrastructure deployment

Cloud Discovery

Use Cloud Provider integrations when you need to:

• Discover existing SSH key pairs across cloud accounts
• Correlate instance metadata with key inventory
• Enforce key policies on cloud-provisioned infrastructure

Identity Sync

Use LDAP / Active Directory when you need to:

• Store SSH public keys as user attributes in your directory
• Use AuthorizedKeysCommand for real-time key lookup
• Centralize SSH authentication with existing identity infrastructure

---

Getting Started

1. Ensure the SSH-KLM API is accessible from your integration target
2. Generate an API key in Settings → API Keys
3. Follow the integration-specific guide for configuration

---

Common Prerequisites

Requirement	Details
SSH-KLM API access	HTTPS endpoint with valid TLS certificate
API key	Generated from the SSH-KLM platform
Network connectivity	Integration target must reach SSH-KLM API
Agent (optional)	Required for on-host discovery and enforcement