Keeping your Koha installation up to date has always required careful planning. How do you apply the latest Koha release, security patches, or platform fixes without risking the MySQL database and configuration files that hold your library’s catalog?
Until now, the answer was “carefully” — snapshot the volume, stop the instance, restore if something goes wrong.
With the May 2026 release, that problem is solved at the platform level.
How It Works
KohaSupport Standard and Enterprise AMIs now provision your Koha server with two separate EBS volumes:
Root volume (10 GB) — the operating system, Koha application code, KohaSupport scripts, and everything else that makes up the AMI image. This volume is replaced when you upgrade.
Data volume (configurable, default 20 GB) — your MySQL database, Koha configuration files, SSL certificates, and anything else that belongs to your library. This volume has DeletionPolicy: Retain in the CloudFormation stack. It is never replaced during an AMI upgrade. It is not deleted when you update your stack. It survives.
When you upgrade to a new AMI, CloudFormation replaces the EC2 instance with the new image and re-attaches your existing data volume. Your catalog, your settings, your certificates — all intact.
Upgrading Is Now a Parameter Change
To upgrade your Koha server to a new AMI release:
- Open the AWS CloudFormation console
- Select your Koha stack → Update → Use existing template
- Change the ImageId parameter to the new AMI ID
- Review and apply — CloudFormation handles the rest
The update takes under 10 minutes. No data migration. No restore from backup. No downtime beyond the normal instance restart.
Data Volume Encryption
The persistent data volume is KMS-encrypted with a customer-managed key (CMK) and automatic annual key rotation. Your library data is encrypted at rest by default — no configuration required.
The KMS key is provisioned as part of your CloudFormation stack and tied to your AWS account. You retain full control of the key.
What This Means for Your Library
- Security patches — we publish updated AMIs as security issues are resolved. Applying them is now a 10-minute operation, not a half-day project.
- Koha version updates — new Koha releases (like the upcoming v25.11.x series) arrive as AMI updates. You apply them the same way.
- Disaster recovery — because your data volume has
DeletionPolicy: Retain, you can delete and recreate your CloudFormation stack without losing your catalog. The data volume remains in EC2 until you explicitly delete it.
Available On
- Standard tier — x86_64 and arm64
- Enterprise tier — arm64
Free and Basic tiers use a single-volume configuration; the persistent data volume and zero-friction upgrade path are Standard and Enterprise features.
Questions about upgrading your stack? Contact support or see the AMI upgrade guide.