Restoring HSM Backup to New Instance
Follow the steps below to restore an HSM from a backup to a new instance:
- Click on CloudHSM in the Services section of the AWS Console and find the existing cluster for the HSM you want to restore. AWS CloudHSM is only billing if there is an HSM in the active cluster.
- Select the link to the cluster that contains the HSM material to restore.
- Click Create HSM and step through the wizard to create a new cluster by selecting the Subnet/AZ for the HSM.
- Once completed it will take some time for AWS to create the HSM. During this time the state will be "Create in progress".
- Once complete the HSM state will be active. Click the refresh button to refresh the status.
- Ensure the appropriate security group for the HSM created is assigned to the SignServer Enterprise Cloud Instance. For more information, see Assigning the Security Group to the SignServer Instance.
- SSH into your SignServer instance with your SSH key using the following command syntax:
# ssh -i ~/Documents/my-ssh.pem firstname.lastname@example.org
- Ensure that the certificate that is used to authenticate with the CloudHSM resides at:
- Stop the CloudHSM client using one of the following commands:
# sudo stop cloudhsm-client or # sudo service cloudhsm-client stop
- Configure the CloudHSM client with the following command replacing
172.16.2.37with the IP address of your HSMCluster:
# sudo /opt/cloudhsm/bin/configure -a 172.16.2.37
- Copy any public key certificates used with SignServer in the past to the following directory (SignServer will not be able to read any keys in CloudHSM without the matching public certificate that was created with it):
- Start the CloudHSM client with the following command:
# sudo start cloudhsm-client or # sudo service cloudhsm-client start
- Update the cloudhsm_mgmt_util Configuration File
# sudo /opt/cloudhsm/bin/configure -m
- Start cloudhsm_mgmt_util to ensure you can connect to the HSM
# /opt/cloudhsm/bin/cloudhsm_mgmt_util /opt/cloudhsm/etc/cloudhsm_mgmt_util.cfg
- Restart Wildfly with the following command:
# sudo systemctl restart wildfly or # sudo service wildfly restart