This guide assumes that the CloudHSM client is pre-installed on an EJBCA Cloud instance. If the cloudHSM client is not yet installed, refer to Appendix D - Installing the CloudHSM Client
To configure the CloudHSM client cloudhsm-client, do the following:
SSH into the EJBCA instance.
Copy your issuing certificate (the one that you used to sign the cluster's certificate) to the following location on the client instance:
/opt/cloudhsm/etc/customerCA.crt
CODE
You need root permissions on the client instance to copy your certificate to this location. If you used your EJBCA instance to generate this file it is located in /home/ec2-user and you may also move or copy it to this location.
Stop the cloudhsm-client
# sudo stop cloudhsm-client
or
# sudo service cloudhsm-client stop
CODE
Use the following command to update the configuration files for the AWS CloudHSM client and command line tools, specifying the IP address of the HSM in your cluster. If you don't know the HSM's IP address, view your cluster in the AWS CloudHSM console.
# sudo /opt/cloudhsm/bin/configure -a <IP address>
Updating server config in /opt/cloudhsm/etc/cloudhsm_client.cfg
Updating server config in /opt/cloudhsm/etc/cloudhsm_mgmt_util.cfg
CODE
Set the CloudHSM client to start on boot
# systemctl enable cloudhsm-client
BASH
Start the CloudHSM client:
# sudo start cloudhsm-client
or
# sudo service cloudhsm-client start
CODE
Ensure the cloudhsm_mgmt_util configuration file is up to date. We need to do this to ensure cloudhsm_mgmt_util is aware of all the HSM instances in the cluster.
# sudo /opt/cloudhsm/bin/configure -m
CODE
Connect to the HSM instances, enable end-to-end encryption, and log in to the HSM instances. Enabling end-to-end encryption encrypts the communication between cloudhsm_mgmt_util and the HSM to prevent interception of sensitive information such as passwords: