Select your cookie preferences

We use essential cookies and similar tools that are necessary to provide our site and services. We use performance cookies to collect anonymous statistics, so we can understand how customers use our site and make improvements. Essential cookies cannot be deactivated, but you can choose “Customize” or “Decline” to decline performance cookies.

If you agree, AWS and approved third parties will also use cookies to provide useful site features, remember your preferences, and display relevant content, including relevant advertising. To accept or decline all non-essential cookies, choose “Accept” or “Decline.” To make more detailed choices, choose “Customize.”

Prerequisites for integrating AWS CloudHSM with Java Keytool and Jarsigner using Client SDK 3

Focus mode
Prerequisites for integrating AWS CloudHSM with Java Keytool and Jarsigner using Client SDK 3 - AWS CloudHSM

To use the AWS CloudHSM key store, you must first initialize and configure the AWS CloudHSM JCE SDK. Use the following steps to do so.

Step 1: Install the JCE

To install the JCE, including the AWS CloudHSM client prerequisites, follow the steps for installing the Java library.

Step 2: Add HSM login credentials to environment variables

Set up environment variables to contain your HSM login credentials.

export HSM_PARTITION=PARTITION_1 export HSM_USER=<HSM user name> export HSM_PASSWORD=<HSM password>
Note

The CloudHSM JCE offers various login options. To use the AWS CloudHSM key store with third-party applications, you must use implicit login with environment variables. If you want to use explicit login through application code, you must build your own application using the AWS CloudHSM key store. For additional information, see the article on Using AWS CloudHSM Key Store.

Step 3: Register the JCE provider

To register the JCE provider, in the Java CloudProvider configuration.

  1. Open the java.security configuration file in your Java installation, for editing.

  2. In the java.security configuration file, add com.cavium.provider.CaviumProvider as the last provider. For example, if there are nine providers in the java.security file, add the following provider as the last provider in the section. Adding the Cavium provider as a higher priority may negatively impact your system's performance.

    security.provider.10=com.cavium.provider.CaviumProvider

    Note

    Power users may be accustomed to specifying -providerName, -providerclass, and -providerpath command line options when using keytool, instead of updating the security configuration file. If you attempt to specify command line options when generating keys with AWS CloudHSM key store, it will cause errors.

PrivacySite termsCookie preferences
© 2025, Amazon Web Services, Inc. or its affiliates. All rights reserved.