Operations
Health checks, logs, backups, getting support, and removing an install.
Health and logs
- Health:
https://APP_HOST/api/healthanswers"ok": truewhen the web app, its engine connection and the cache are working. - Logs: the app and MCP endpoint log to the cluster (
kubectl -n eode logs deploy/eode-app). Install and upgrade logs are in CloudWatch Logs, log group/aws/codebuild/<cluster>-installer. - Telemetry: set TelemetryEndpoint to send traces and metrics to your own OpenTelemetry collector.
Backups
| What | How it's backed up |
|---|---|
| Database | RDS automated backups, kept DbBackupDays days, plus a snapshot before every stack update |
| Model files | The EFS file system; add it to AWS Backup |
| Secrets | Secrets Manager. Keep eode/data-connections safe: without it, saved data-connection credentials can't be read |
To restore, open a ticket in the eode portal. The stack can't switch to a restored database by itself, so we restore the database and file system together with you.
Support
Open a ticket in the eode portal (portal.eode.app). Say which release you run and what happened. Nothing is
sent to River Logic unless you send it.
Uninstall
- Turn off deletion protection on the eode database in RDS.
- Delete the stack in CloudFormation.
The database leaves a final snapshot, the snapshots taken before each upgrade (eode-pre-…) stay, and the EFS file
system is kept, so nothing is lost by accident. They're billed until you delete them in RDS and EFS. Ask us to remove your account's invitation when you're done.