- Newest
- Most votes
- Most comments
It turned out that the cloudhsm-dyn.cfg and cloudhsm-pkcs11.cfg files were missing the client_cert_hsm_tls_path and client_key_hsm_tls_path properties. I copied them from cloudhsm-cli.cfg and they started working.
answered a year ago
It appears that you're experiencing a connection issue between OpenSSL and your AWS CloudHSM cluster. The error message suggests that the OpenSSL engine is unable to establish a connection with the HSM. Here are some steps you can take to troubleshoot and potentially resolve this issue:
-
Check the IP address: Ensure that the IP address specified in your CloudHSM client configuration file is correct and points to an active, reachable HSM in your cluster. The configuration file is typically located at
/opt/cloudhsm/etc/cloudhsm-client.cfg. If the IP address is incorrect or the HSM is no longer available, update the configuration with a valid IP address of an active HSM in your cluster. -
Verify client configuration: Double-check that your CloudHSM client is properly configured. This includes ensuring that the
cloudhsm-clientdaemon is running and that the client can communicate with the HSM cluster. -
Check HSM status: Verify that your HSM cluster is active and that there is at least one HSM available. You can do this using the AWS CloudHSM console or the AWS CLI.
-
Restart the client: Try stopping and restarting the CloudHSM client daemon. This can sometimes resolve connection issues.
-
Check OpenSSL version compatibility: Ensure that your OpenSSL version is compatible with the AWS CloudHSM OpenSSL Dynamic Engine. Some older versions of OpenSSL may not be supported.
-
Verify engine location: Confirm that the CloudHSM OpenSSL engine shared library is correctly installed at
/opt/cloudhsm/lib/libcloudhsm_openssl.so. -
Review logs: Check the CloudHSM client logs for any additional error messages or clues about the connection failure.
If you've verified all these points and are still experiencing issues, you may need to contact AWS support for further assistance. They can help diagnose any potential problems with your HSM cluster or network configuration that might be preventing the OpenSSL engine from connecting successfully.
Sources
Lost connection to the AWS CloudHSM cluster - AWS CloudHSM
Use the OpenSSL Dynamic Engine for AWS CloudHSM Client SDK 3 - AWS CloudHSM
AWS CloudHSM error seen during key availability check - AWS CloudHSM
answered a year ago
Relevant content
asked 2 years ago
asked a year ago

Wow this is really bad. I'm using version 5 of the SDK, which I've made clear in my post, but you insist on giving me advice for version 3. So helpful.