Multiregion clusters

With PaaS, you can have a multiregion setup which improves Magnolia availability to 99.9% and is essential for a successful (and automated) disaster recovery process. We accomplish this by configuring a multiregion setup for your project. We do this with an active/passive scenario approach.

This active/passive scenario approach includes an additional satellite cluster which is in a different availability zone and/or region. Primary traffic is routed through the active cluster while the secondary (passive) cluster is ready in standby mode meaning if the primary cluster regions goes down, traffic is automatically routed to the healthy secondary cluster.

What is the primary cluster exactly?

The CDN operator decides how to route the traffic best based on geolocation.


User A is based in Germany and is routed through the Frankfurt cluster (primary) and is only routed through the secondary cluster (US-East) if the primary cluster is down.

  • Primary cluster healthy

  • Primary cluster down

When the primary cluster is healthy, it is the active cluster and traffic is routed through it.

multiRegion primaryActive

When the primary cluster is unhealthy or down, the secondary cluster takes over as the active cluster and the traffic now goes through it.

multiRegion secondaryActive


If you have opted for this feature, we set up everything in the backend for your multiregion cluster approach. This can be for one additional remote satellite (passive) cluster or more. That’s up to you. However, we do need you to modify the values.yml file for your specific environments to accommodate the multiregion feature.

See how to configure the values.yml file for multiregion usage here.





This widget lets you know where you are on the docs site.

You are currently perusing through the Magnolia PaaS docs.

Main doc sections

DX Core Headless PaaS Legacy Cloud Incubator modules