Components

System Components

Detailed breakdown of each component in the SSH-KLM architecture.

API Server

The API server handles all client requests and orchestrates operations.

Responsibilities

REST API endpoints
WebSocket connections for real-time updates
Authentication and authorization
Request validation
Rate limiting

Configuration

api:
  port: 8081
  workers: 4
  timeout: 30s
  cors:
    origins: ["https://app.example.com"]

Worker Nodes

Background workers process asynchronous tasks.

Worker Types

Worker	Purpose	Concurrency
Discovery	Scan hosts for SSH keys	10 parallel
Rotation	Execute key rotations	5 parallel
Notification	Send alerts/emails	20 parallel
Cleanup	Archive old data	1

Job Queue

// Example job structure
{
  "id": "job-12345",
  "type": "rotation",
  "payload": {
    "keyId": "KEY-abc",
    "algorithm": "ed25519"
  },
  "priority": "high",
  "retries": 3
}

Database (PostgreSQL)

Primary data store for all persistent data.

Schema Overview

Table	Purpose
`hosts`	Target server inventory
`ssh_keys`	Discovered key metadata
`rotations`	Rotation job history
`policies`	Rotation/access policies
`audit_logs`	All operations logged

Cache (Redis)

High-performance caching and job queue.

Usage

Session storage
API response caching
Job queue (Bull/BullMQ)
Rate limit counters
Real-time pub/sub

SSH-KLM Agent

Lightweight daemon on target hosts.

Features

Local key discovery
Key rotation execution
Real-time file monitoring
Secure communication

Resource Usage

Resource	Typical Usage
Memory	50-100 MB
CPU	< 1% idle
Disk	10 MB