Notes

This update only affects the DCsv3 and DCdsv3 series instances. To verify the machine type for your Azure-hosted API co-signer, navigate to your Azure Portal Virtual Machines, visit the Overview page of your machine, and look for the Size field.
If a request to sign a new transaction is made during the post-maintenance reboot, the transaction will enter the Pending signature status until the API Co-Signer comes back online and processes it.

Overview

Microsoft Azure is patching instance types that support the Fireblocks API Co-Signer software. All existing customers must reboot their machines by December 4th, 2022 to avoid an unplanned service interruption.

Fireblocks customers with an API Co-Signer hosted in an Azure environment configured prior to November 4th, 2022 should follow the instructions below by December 4th.

Important

Failure to complete this maintenance before December 4th will result in a sudden reboot triggered by Microsoft Azure. The machine will be unavailable to sign transactions until the update is complete.

Updating an existing API Co-Signer on Azure

First, update your API Co-Signer software version to version 1.1.5 or 1.1.4 if it has not already been updated. Refer to the API Co-Signer version history article for more information.

Please note that migrating to version 1.1.5 cannot be done in-place and must happen using either the New Server method or the Re-imaging the Fireblocks software method. Refer to the Updating the API co-signer article for more information.

Next, schedule a maintenance window for your API Co-Signer. During that maintenance window:

Reboot your API Co-Signer.
Wait until the machine is fully up and running.
Confirm that the Microsoft update is complete.
Initiate a test transaction and sign it with the API Co-Signer to verify that it operates as expected.
Complete these steps for all additional API Co-Signer machines.

Note

We recommend performing the maintenance on one machine at a time if you have more than one API Co-Signer.

Checking the instance's health post-reboot

To check the instance is healthy after the maintenance reboot:

Run the following command to output a list of all running containers.
```
# docker ps -a
```
Confirm the cosigner-init docker container is not running.
Confirm the cosigner docker container is not restarting.
Initiate a test transaction through the API and confirm that the API Co-Signer signs it as expected.

Installing a new API Co-Signer

Follow the instructions in the Configuring a server for the API Co-Signer article to install a new API Co-Signer machine on Azure. All new instances already include the latest Microsoft updates and are not affected by this issue.