Runbook: Rotate API Key & Credentials
Runbook: Rotate API Key & Credentials
Section titled “Runbook: Rotate API Key & Credentials”Trigger: Suspected credential exposure, routine periodic rotation, or agent de-provisioning.
Strict Policy Notice
Section titled “Strict Policy Notice”Procedure: Rotate Customer Agent Key
Section titled “Procedure: Rotate Customer Agent Key”- Generate New Cryptographic Key: Create a high-entropy secret token in the management console / API backend.
- Deploy Key to Agent: Update the target agent’s runtime configuration with the new token.
- Verify Authorized Ingress:
Inspect incoming requests on
https://api.salitech.deto ensure requests with the new key succeed (HTTP 200). - 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)”- SSH into
production-01. - Navigate to
/opt/<service>. - Update
.envwith new secret values:Terminal window chmod 600 .env - Restart the Docker Compose stack:
Terminal window docker compose down && docker compose up -d