📘

Learn more about the Fireblocks API Co-signer here

High Availability

Configuring multiple API Co-signers to work in an active-active state is a good practice.

This high availability configuration ensures that transaction operations are always running and that the transaction signing load is shared across the API Co-signers. If an API Co-signer fails or becomes impaired, the other API Co-signer(s) continues signing transactions.
In addition, configuring multiple API Co-signers can significantly improve your signing throughput.

Backup & Recovery

Backing up the API Co-signer server and data is highly recommended for streamlining machine updates or replacement processes. This backup can also be used for disaster recovery (DR), however, it is recommended to set up an additional API Co-signer in high availability (active-active) and use it if something goes wrong. You can learn more about backing up and restoring the API Co-signer by referring to one of the articles below:

• SGX API Co-Signer Backup & Recovery
• AWS Nitro API Co-Signer Backup & Recovery

Best practices

To ensure business continuity, install the API Co-signers in high availability using both on-prem data centers (when possible) and cloud service providers.

If only one infrastructure provider is available for hosting all the API Co-signers, follow the best practices for each cloud service provider for setting up cross-region replication and multiple API Co-signer instances on different data centers when deploying on-prem.