Deployment and install

Install on AWS or your own server, set up HTTPS, and run and back up a deployment.

• Deployment requirementsWhat you need before installing Workforce Intelligence: a box, open ports, a GitHub token for the image registry, and a public address.
• Install on AWS with CloudFormationProvision a Workforce Intelligence box with the CloudFormation template: parameters, access over Session Manager, outputs, generated secrets, and data protection.
• Install on your own serverInstall Workforce Intelligence on a Linux server you manage, using install.sh and an .env file you prepare.
• First-run setup tokenFind the one-time setup token that the setup wizard asks for on a new installation.
• Configuration referenceEvery environment variable an operator sets for a production deployment, which are required, and which are fixed by the compose file.
• Domains and automatic HTTPSServe Workforce Intelligence on your own domain with a certificate that Caddy obtains and renews for you.
• Day-two operationsCheck status, stop, start, restart, and pull images on a running deployment with Docker Compose.
• Containers and volumesThe containers and Docker volumes that make up a Workforce Intelligence deployment, and what each one holds.
• Master key custodyWI_MASTER_KEY protects the data key that encrypts every stored credential. Back it up off the box, and rotate it with WI_MASTER_KEY_OLD.
• Backups and recovery on AWSHow the CloudFormation deployment protects its root volume, how to check the backups, how to recover a lost instance, and what to arrange on your own server.
• Production boot checksThe configuration problems that make the application refuse to start in production, and how to fix each one.
• Rotate the master keyReplace WI_MASTER_KEY with a new key using WI_MASTER_KEY_OLD, confirm the rotation in the admin screen, and remove the old key.