FusionAuth Cloud High Availability Architecture
On this page
A High Availability (HA) deployment runs in a single region across three availability zones. Each availability zone runs on separate infrastructure. When one availability zone fails, the other two availability zones continue to serve traffic. To choose HA for a new deployment, see Create a Deployment.
HA Architecture Diagram#
The following diagram shows the components of an HA deployment. A global anycast edge network receives each request and passes the request to a traffic router. The traffic router forwards the request to the load balancer. The load balancer spreads traffic across three FusionAuth nodes, one in each availability zone. The primary database runs in one availability zone and replicates to a secondary database in another availability zone. Each availability zone also runs a search node.
An HA deployment spreads FusionAuth nodes, databases, and search nodes across three availability zones in one region.
Components Replicated Across Zones#
Each HA deployment replicates the following components across availability zones:
| Component | Redundancy |
|---|---|
| FusionAuth nodes | Three nodes, one in each availability zone. |
| Database | A primary and a secondary database, always in different availability zones. |
| Load balancer | A redundant load balancer with DNS failover. |
| Backups | Stored in Amazon S3, which replicates backups across multiple availability zones. |
| Search nodes | FusionAuth does not back up Elasticsearch or OpenSearch data. The search cluster keeps multiple copies of each record on nodes in all three availability zones. FusionAuth can rebuild the search data from the database. |
Failure Scenarios Covered by HA#
An HA deployment continues to serve traffic through the following failures:
| Failure | Covered | Result |
|---|---|---|
| Single server | Yes | The remaining FusionAuth nodes continue to serve traffic. |
| Database node | Yes | The secondary database becomes the primary automatically. |
| Single availability zone | Yes | The FusionAuth nodes and database in the other two availability zones continue to serve traffic with no downtime. |
| Load balancer | Yes | The redundant load balancer and DNS failover continue to route traffic. |
| Full region | No | Requires the Disaster Recovery add-on. |
HA does not protect against an outage of a full region. For cross-region protection, FusionAuth offers the Disaster Recovery add-on to Enterprise customers.
Related
Exploring Disaster Recovery (DR) options in FusionAuth Cloud.
Learn how to create a FusionAuth Cloud account.
Learn how to delete your FusionAuth Cloud account.
Learn about the account portal, where you can manage account data, deployments, and licenses.