13. Upgrading to a new version¶
Your vendor announces a new version tag, e.g.
2026.11.01. If QuantaCloud is switched off (power schedule or by hand), switch it on first and wait until your domain opens: the update prepares the database, which needs the database running. The same applies to any other stack update.CloudFormation → your stack → Update stack → Make a direct update.
Same YAML: Use existing template.
New YAML provided with the release: Replace existing template → Upload a template file.
Change
ImageTagto the new version. Leave every other field as it is (hidden fields keep their value automatically).Next → Next → tick the IAM box → Submit.
The update prepares the database for the new version automatically, before the new version starts, then replaces the services one by one. Open files keep working, but sign-in, the Admin Console and desktop sync pause for 1–2 minutes while their single server restarts (pages show 502 until it is back). Update outside working hours.
Wait for UPDATE_COMPLETE — about 5–15 minutes; click the refresh button now and then. If it fails, CloudFormation automatically returns to the previous version — then read section 12.