Upgrades
Move to a new eode release with one stack update, and roll back if you need to.
Each release has a version number like 2026.11.1 and release notes in the eode portal and on
Release notes. Upgrading is a stack update: the installer takes a database snapshot, updates the
database, rolls eode onto the new release, and checks it's healthy before it reports success.
Upgrade
Pick a time
A running conversation stops when the web app restarts, and users pick it up again where they left off. Models, data and finished results aren't affected. Choose a quiet hour.
Update the stack
Select the stack in CloudFormation, choose Update, then Replace existing template with the new release's template URL from the eode portal. Set Release to the new version, leave every other field as it is, and submit.
Check it
The stack reaches UPDATE_COMPLETE. The installer only reports success after the new release answers its health check.
You can skip releases: an upgrade applies every database change between your version and the new one.
Roll back
Roll back with a stack update: Replace existing template with the previous release's template URL, set Release to the previous version, and leave every other field as it is.
Database changes only go forward. If the newer release changed the database, the older one can't run on it, and
going back means restoring the snapshot the upgrade took (eode-pre-<new version, dots as dashes>-<time>, for example
eode-pre-2026-11-1-20261130140500). We do that restore with you.
Ask us through the eode portal before you roll back. We'll confirm the steps for your two versions.