Operator Manual¶
This manual is for the team that runs Ampora. If you are a day-to-day user — Admin in the UI, Operator pushing rollouts, Viewer browsing the fleet — start with the User Manual instead.
It is organised so a fresh operator can read it top-to-bottom and have a production-ready deployment, then come back later for reference.
Table of contents¶
- Installation — pick a deployment target.
- Configuration — every setting that matters and why.
- Operations — HA, backup/restore, upgrades, self-observability.
- Security — threat model, hardening, rotation, HSM/KMS, revocation.
- Troubleshooting — what to do when something goes wrong.
Quick paths¶
| You are about to … | Start here |
|---|---|
| run a local stack on your laptop | Quickstart |
| deploy on a real Kubernetes cluster | Installation → Kubernetes |
| put Ampora behind your reverse proxy | Operations → High availability |
| harden the deployment for production | Security → Hardening checklist |
| diagnose a stuck rollout | Troubleshooting → Rollouts stall |
Conventions used in this manual¶
- Fenced code is meant to be copy-paste-runnable, with the right language tag for syntax highlighting.
AMPORA_HOSTstands in for your real Ampora hostname (ampora.acme.ioor similar).- All times are UTC unless stated otherwise.
- All hostnames are examples; substitute your own.