How are database migrations handled for FusionAuth Cloud instances?

FASupportBot

I noticed a new FusionAuth release (1.70.0) requires a database migration to be run out of band. For FusionAuth Cloud (SaaS) instances, how are these database migrations handled?

Do customers need to:

Run the migrations manually through the FusionAuth UI?
Execute them via command line or API?
Or are they automatically applied by the FusionAuth Cloud team during upgrades?

FASupportBot

For FusionAuth Cloud (SaaS) instances, database migrations are automatically applied as part of the upgrade process. You do not need to take any action.

The FusionAuth Cloud team handles all required database migrations when upgrading your hosted instance to a new version. This is managed on your behalf as part of the cloud service. When you initiate an upgrade through your FusionAuth Account dashboard, the migrations run automatically during the upgrade process.

For HA Cloud (multi-node) deployments, nodes are upgraded one at a time. When the first upgraded node connects to the database, it locks the database and runs the required migrations while other nodes continue serving traffic, resulting in only seconds of downtime.

For Basic/Business Cloud (single-node) deployments, the entire instance goes offline during the upgrade, with downtime ranging from 5 to 60 minutes depending on the amount of data and schema changes required.

If you are running a self-hosted FusionAuth instance, you would need to follow the upgrade guide and apply any required out-of-band migrations manually (or configure Silent Mode for automatic migrations). However, for cloud-hosted instances, this is handled automatically by FusionAuth.

Note: You cannot downgrade a FusionAuth Cloud deployment version after upgrading, so it's recommended to test upgrades in a non-production environment first if possible.

How are database migrations handled for FusionAuth Cloud instances?

Related Documentation