> For the complete documentation index, see [llms.txt](https://docs.certinext.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.certinext.io/documentation/deployment-and-operations/high-availability-and-disaster-recovery.md).

# High Availability and Disaster Recovery

CertiNext is designed with **high availability (HA)** and **disaster recovery (DR)** as foundational principles to ensure continuous certificate lifecycle operations and resilient trust services. The platform architecture spans multiple layers—application, data, and trust services—to minimize downtime and maintain service continuity even during infrastructure failures.

***

#### CertiNext High Availability on AWS

CertiNext is hosted on **Amazon Web Services (AWS)** and leverages cloud-native resilience patterns.

Key characteristics include:

* **Auto-scalable application servers** to handle variable workloads and peak demand
* **Highly available databases** with synchronous/asynchronous replication
* **Multi–Availability Zone (Multi-AZ) deployments** within each operating region
* **Automated failover** to ensure service continuity in the event of AZ-level issues

This architecture ensures that application and data layers remain available even during localized infrastructure disruptions.

***

#### emSign Trust Services Availability

emSign TLS and trust services are hosted in **WebTrust-accredited data centers** operated by us, with strict physical and logical security controls.

emSign’s HA and DR design includes:

* Deployment across **multiple WebTrust-accredited data centers**
* **Data replication** between geographically separated sites
* Redundant trust service components to eliminate single points of failure
* Secure access controls aligned with WebTrust audit requirements

This ensures continuity of public trust services, including certificate issuance, validation, and revocation.

***

#### End-to-End Resilience Across Platforms

Together, CertiNext and emSign deliver resilience across:

* **Application and API layer** (auto-scaling and load balancing)
* **Data layer** (replicated databases and backups)
* **Trust services** (redundant CA and validation infrastructure)

This coordinated design supports uninterrupted certificate lifecycle operations for both public and private trust use cases.

***

#### Availability Targets

The combined architecture of CertiNext and emSign is designed to deliver **up to 99.99% service availability**. This target reflects:

* Redundant infrastructure across availability zones and data centers
* Automated recovery and failover mechanisms
* Continuous monitoring and operational oversight

***

#### Planned Maintenance and Downtime

Planned maintenance activities, including platform upgrades or infrastructure changes, are performed using controlled deployment practices to minimize impact. When planned downtime is required:

* Customers are **notified in advance**
* Maintenance windows are scheduled to reduce operational disruption
* Clear communication is provided regarding scope and expected impact

***

#### Summary

CertiNext’s high availability and disaster recovery strategy combines **cloud-native resilience on AWS** with **WebTrust-accredited trust infrastructure for emSign**, delivering a robust, enterprise-grade service model. This architecture ensures reliable certificate lifecycle management, secure trust services, and consistent availability—supporting mission-critical environments with confidence and predictability.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.certinext.io/documentation/deployment-and-operations/high-availability-and-disaster-recovery.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
