Keep IRIS running
This guide is for the person who looks after the IRIS server: new releases, backups, credentials, certificates, signing keys, and recovery when something breaks. Day-to-day staging work is in the User Guide.
Common tasks
| Task | Page |
|---|---|
| Replace browser TLS or telemetry credentials in the UI | Guided Console rotation |
| Replace deployment trust or backup recovery keys | Rotate deployment trust and keys |
| Deploy a new IRIS release | Deploy a new release |
| Remove a managed deployment | Remove an IRIS deployment |
| Back up the server, or restore it | Back up and restore |
| Export the audit trail, set the API request budget, reset the admin account | Routine maintenance tasks |
| Rotate a credential or a certificate | Rotate credentials and certificates |
| Replace or recover the signing keys | Replace or recover signing keys |
| Replace and revoke the online signing key | Rotate the online signer |
| Schedule rotations, approvals and credential reviews | Schedule key maintenance |
| Recover after an interrupted job or damaged state | Recover from an interrupted job or damaged state |
Pages in this guide
- Deploy a new release: undeploy, remove the old deployment, install its replacement and onboard the devices.
- Remove an IRIS deployment: review exact removal targets, choose data retention, and recover interrupted removal.
- Back up and restore: what to back up per layout, and how to restore it.
- Routine maintenance tasks: audit export, the API request budget, and the admin account reset.
- Rotate credentials and certificates: one procedure per credential, per layout.
- Replace or recover signing keys: the two root keys, a lost key, a leaked key, and hand delivery of the first instruction file.
- Recover from an interrupted job or damaged state: interrupted device jobs, damaged volumes, and retained migration evidence.