Skip to content

Runbook: Rotate API Key & Credentials

Trigger: Suspected credential exposure, routine periodic rotation, or agent de-provisioning.



  1. Generate New Cryptographic Key: Create a high-entropy secret token in the management console / API backend.
  2. Deploy Key to Agent: Update the target agent’s runtime configuration with the new token.
  3. Verify Authorized Ingress: Inspect incoming requests on https://api.salitech.de to ensure requests with the new key succeed (HTTP 200).
  4. Revoke Previous Key: Invalidate the deprecated key immediately to close exposure windows.

Procedure: Rotate Host Service Secret (e.g. n8n / Umami)

Section titled “Procedure: Rotate Host Service Secret (e.g. n8n / Umami)”
  1. SSH into production-01.
  2. Navigate to /opt/<service>.
  3. Update .env with new secret values:
    Terminal window
    chmod 600 .env
  4. Restart the Docker Compose stack:
    Terminal window
    docker compose down && docker compose up -d