Add a cluster to your AWS CloudHSM configuration
When connecting to multiple clusters,
use the configure-cli add-cluster command to add a cluster to your configuration.
Syntax
configure-cli add-cluster[OPTIONS]--cluster-id<CLUSTER ID>[--region<REGION>] [--endpoint<ENDPOINT>] [--hsm-ca-cert<HSM CA CERTIFICATE FILE>] [--client-cert-hsm-tls-file<CLIENT CERTIFICATE FILE>] [--client-key-hsm-tls-file<CLIENT KEY FILE>] [-h, --help]
Examples
Use the configure-cli add-cluster along with the cluster-id parameter to add a cluster (with the ID of cluster-1234567) to your configuration.
Tip
If using configure-cli add-cluster with the cluster-id parameter doesn't result in the cluster being added, refer to the following example for a longer version
of this command that also requires --region and --endpoint parameters to identify the cluster being added. If, for example, the region of the cluster is different than the one configured as your AWS CLI default,
you should use the --region parameter to use the correct region. Additionally, you have the ability to specify the AWS CloudHSM API endpoint to use for the call, which may be necessary for
various network setups, such as using VPC interface endpoints that don’t use the default DNS hostname for AWS CloudHSM.
Use the configure-cli add-cluster along with the cluster-id, endpoint, and region parameters to add a cluster (with the ID of cluster-1234567) to your configuration.
For more information about the --cluster-id, --region,
and --endpoint parameters, see AWS CloudHSM Client SDK 5 configuration parameters.
Parameters
- --cluster-id
<Cluster ID> -
Makes a
DescribeClusterscall to find all of the HSM elastic network interface (ENI) IP addresses in the cluster associated with the cluster ID. The system adds the ENI IP addresses to the AWS CloudHSM configuration files.Note
If you use the
--cluster-idparameter from an EC2 instance within a VPC that does not have access to the public internet, then you must create an interface VPC endpoint to connect with AWS CloudHSM. For more information about VPC endpoints, see AWS CloudHSM and VPC endpoints.Required: Yes
- --endpoint
<Endpoint> -
Specify the AWS CloudHSM API endpoint used for making the
DescribeClusterscall. You must set this option in combination with--cluster-id.Required: No
- --hsm-ca-cert
<HsmCA Certificate Filepath> -
Specifies the filepath to the HSM CA certificate.
Required: No
- --region
<Region> -
Specify the region of your cluster. You must set this option in combination with
--cluster-id.If you don’t supply the
--regionparameter, the system chooses the region by attempting to read theAWS_DEFAULT_REGIONorAWS_REGIONenvironment variables. If those variables aren’t set, then the system checks the region associated with your profile in your AWS config file (typically~/.aws/config) unless you specified a different file in theAWS_CONFIG_FILEenvironment variable. If none of the above are set, the system defaults to theus-east-1region.Required: No
- --client-cert-hsm-tls-file
<client certificate hsm tls path> -
Path to the client certificate used for TLS client-HSM mutual authentication.
Only use this option if you have registered at least one trust anchor onto HSM with CloudHSM CLI. You must set this option in combination with
--client-key-hsm-tls-file.Required: No
- --client-key-hsm-tls-file
<client key hsm tls path> -
Path to the client key used for TLS client-HSM mutual authentication.
Only use this option if you have registered at least one trust anchor onto HSM with CloudHSM CLI. You must set this option in combination with
--client-cert-hsm-tls-file.Required: No