Keep a key safe
A key is a password for your account. Keep it on your server, give it the fewest scopes, and rotate by overlap.
Updated 1 min read
- Keep it in your server’s environment or a secret manager. Never in a browser, a mobile app or a repository.
- One key per system, so one can be revoked without touching the others.
- Scopes as narrow as the job: a reporting job needs
runs:read, notruns:write. - Give keys an expiry where you can.
- Rotate by overlap: make the new key, deploy it, then revoke the old one.