AWS services or capabilities described in AWS Documentation may vary by region/location. Click Getting Started with Amazon AWS to see specific differences applicable to the China (Beijing) Region.
Connects or reconnects a custom
key store to its backing key store. For an CloudHSM key store,
connects the key store to its associated CloudHSM cluster. For an external key store,
ConnectCustomKeyStore connects the key store to the external key store
proxy that communicates with your external key manager.
The custom key store must be connected before you can create KMS keys in the key store or use the KMS keys it contains. You can disconnect and reconnect a custom key store at any time.
The connection process for a custom key store can take an extended amount of time to complete. This operation starts the connection process, but it does not wait for it to complete. When it succeeds, this operation quickly returns an HTTP 200 response and a JSON object with no properties. However, this response does not indicate that the custom key store is connected. To get the connection state of the custom key store, use the DescribeCustomKeyStores operation.
This operation is part of the custom key stores feature in KMS, which combines the convenience and extensive integration of KMS with the isolation and control of a key store that you own and manage.
ConnectCustomKeyStore operation might fail for various reasons. To
find the reason, use the DescribeCustomKeyStores operation and see the
in the response. For help interpreting the
ConnectionErrorCode, see CustomKeyStoresListEntry.
To fix the failure, use the DisconnectCustomKeyStore operation to disconnect
the custom key store, correct the error, use the UpdateCustomKeyStore operation
if necessary, and then use
CloudHSM key store
During the connection process for an CloudHSM key store, KMS finds the CloudHSM cluster
that is associated with the custom key store, creates the connection infrastructure,
connects to the cluster, logs into the CloudHSM client as the
CU, and rotates its password.
To connect an CloudHSM key store, its associated CloudHSM cluster must have at least
one active HSM. To get the number of active HSMs in a cluster, use the DescribeClusters
operation. To add HSMs to the cluster, use the CreateHsm
operation. Also, the
kmsuser crypto user (CU) must not be logged into the cluster. This
prevents KMS from using this account to log in.
If you are having trouble connecting or disconnecting a CloudHSM key store, see Troubleshooting an CloudHSM key store in the Key Management Service Developer Guide.
External key store
When you connect an external key store that uses public endpoint connectivity, KMS tests its ability to communicate with your external key manager by sending a request via the external key store proxy.
When you connect to an external key store that uses VPC endpoint service connectivity, KMS establishes the networking elements that it needs to communicate with your external key manager via the external key store proxy. This includes creating an interface endpoint to the VPC endpoint service and a private hosted zone for traffic between KMS and the VPC endpoint service.
To connect an external key store, KMS must be able to connect to the external key store proxy, the external key store proxy must be able to communicate with your external key manager, and the external key manager must be available for cryptographic operations.
If you are having trouble connecting or disconnecting an external key store, see Troubleshooting an external key store in the Key Management Service Developer Guide.
Cross-account use: No. You cannot perform this operation on a custom key store in a different Amazon Web Services account.
Required permissions: kms:ConnectCustomKeyStore (IAM policy)
This is an asynchronous operation using the standard naming convention for .NET 4.5 or higher. For .NET 3.5 the operation is implemented as a pair of methods using the standard naming convention of BeginConnectCustomKeyStore and EndConnectCustomKeyStore.
public virtual Task<ConnectCustomKeyStoreResponse> ConnectCustomKeyStoreAsync( ConnectCustomKeyStoreRequest request, CancellationToken cancellationToken )
Container for the necessary parameters to execute the ConnectCustomKeyStore service method.
A cancellation token that can be used by other objects or threads to receive notice of cancellation.
The request was rejected because the associated CloudHSM cluster did not meet the
configuration requirements for an CloudHSM key store.
The CloudHSM cluster must be configured with private subnets in at least two different
Availability Zones in the Region.
group for the cluster (cloudhsm-cluster-
|CloudHsmClusterNotActiveException||The request was rejected because the CloudHSM cluster associated with the CloudHSM key store is not active. Initialize and activate the cluster and try the command again. For detailed instructions, see Getting Started in the CloudHSM User Guide.|
|CustomKeyStoreInvalidStateException||The request was rejected because of the ConnectionState of the custom key store. To get the ConnectionState of a custom key store, use the DescribeCustomKeyStores operation. This exception is thrown under the following conditions: You requested the ConnectCustomKeyStore operation on a custom key store with a ConnectionState of DISCONNECTING or FAILED. This operation is valid for all other ConnectionState values. To reconnect a custom key store in a FAILED state, disconnect it (DisconnectCustomKeyStore), then connect it (ConnectCustomKeyStore). You requested the CreateKey operation in a custom key store that is not connected. This operations is valid only when the custom key store ConnectionState is CONNECTED. You requested the DisconnectCustomKeyStore operation on a custom key store with a ConnectionState of DISCONNECTING or DISCONNECTED. This operation is valid for all other ConnectionState values. You requested the UpdateCustomKeyStore or DeleteCustomKeyStore operation on a custom key store that is not disconnected. This operation is valid only when the custom key store ConnectionState is DISCONNECTED. You requested the GenerateRandom operation in an CloudHSM key store that is not connected. This operation is valid only when the CloudHSM key store ConnectionState is CONNECTED.|
|CustomKeyStoreNotFoundException||The request was rejected because KMS cannot find a custom key store with the specified key store name or ID.|
|KMSInternalException||The request was rejected because an internal exception occurred. The request can be retried.|
.NET Core App:
Supported in: 3.1
Supported in: 2.0
Supported in: 4.5