GSP
Quick Navigator

Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Support
Contact Us
Online Help
Handbooks
Domain Status
Man Pages

FAQ
Virtual Servers
Pricing
Billing
Technical

Network
Facilities
Connectivity
Topology Map

Miscellaneous
Server Agreement
Year 2038
Credits
 

USA Flag

 

 

Man Pages
Paws::KMS::CustomKeyStoresListEntry(3) User Contributed Perl Documentation Paws::KMS::CustomKeyStoresListEntry(3)

Paws::KMS::CustomKeyStoresListEntry

This class represents one of two things:

Arguments in a call to a service

Use the attributes of this class as arguments to methods. You shouldn't make instances of this class. Each attribute should be used as a named argument in the calls that expect this type of object.

As an example, if Att1 is expected to be a Paws::KMS::CustomKeyStoresListEntry object:

  $service_obj->Method(Att1 => { CloudHsmClusterId => $value, ..., TrustAnchorCertificate => $value  });

Results returned from an API call

Use accessors for each attribute. If Att1 is expected to be an Paws::KMS::CustomKeyStoresListEntry object:

  $result = $service_obj->Method(...);
  $result->Att1->CloudHsmClusterId

Contains information about each custom key store in the custom key store list.

A unique identifier for the AWS CloudHSM cluster that is associated with the custom key store.

Describes the connection error. This field appears in the response only when the "ConnectionState" is "FAILED". For help resolving these errors, see How to Fix a Connection Failure (https://docs.aws.amazon.com/kms/latest/developerguide/fix-keystore.html#fix-keystore-failed) in AWS Key Management Service Developer Guide.

Valid values are:

  • "CLUSTER_NOT_FOUND" - AWS KMS cannot find the AWS CloudHSM cluster with the specified cluster ID.
  • "INSUFFICIENT_CLOUDHSM_HSMS" - The associated AWS CloudHSM cluster does not contain any active HSMs. To connect a custom key store to its AWS CloudHSM cluster, the cluster must contain at least one active HSM.
  • "INTERNAL_ERROR" - AWS KMS could not complete the request due to an internal error. Retry the request. For "ConnectCustomKeyStore" requests, disconnect the custom key store before trying to connect again.
  • "INVALID_CREDENTIALS" - AWS KMS does not have the correct password for the "kmsuser" crypto user in the AWS CloudHSM cluster. Before you can connect your custom key store to its AWS CloudHSM cluster, you must change the "kmsuser" account password and update the key store password value for the custom key store.
  • "NETWORK_ERRORS" - Network errors are preventing AWS KMS from connecting to the custom key store.
  • "SUBNET_NOT_FOUND" - A subnet in the AWS CloudHSM cluster configuration was deleted. If AWS KMS cannot find all of the subnets in the cluster configuration, attempts to connect the custom key store to the AWS CloudHSM cluster fail. To fix this error, create a cluster from a recent backup and associate it with your custom key store. (This process creates a new cluster configuration with a VPC and private subnets.) For details, see How to Fix a Connection Failure (https://docs.aws.amazon.com/kms/latest/developerguide/fix-keystore.html#fix-keystore-failed) in the AWS Key Management Service Developer Guide.
  • "USER_LOCKED_OUT" - The "kmsuser" CU account is locked out of the associated AWS CloudHSM cluster due to too many failed password attempts. Before you can connect your custom key store to its AWS CloudHSM cluster, you must change the "kmsuser" account password and update the key store password value for the custom key store.
  • "USER_LOGGED_IN" - The "kmsuser" CU account is logged into the the associated AWS CloudHSM cluster. This prevents AWS KMS from rotating the "kmsuser" account password and logging into the cluster. Before you can connect your custom key store to its AWS CloudHSM cluster, you must log the "kmsuser" CU out of the cluster. If you changed the "kmsuser" password to log into the cluster, you must also and update the key store password value for the custom key store. For help, see How to Log Out and Reconnect (https://docs.aws.amazon.com/kms/latest/developerguide/fix-keystore.html#login-kmsuser-2) in the AWS Key Management Service Developer Guide.
  • "USER_NOT_FOUND" - AWS KMS cannot find a "kmsuser" CU account in the associated AWS CloudHSM cluster. Before you can connect your custom key store to its AWS CloudHSM cluster, you must create a "kmsuser" CU account in the cluster, and then update the key store password value for the custom key store.

Indicates whether the custom key store is connected to its AWS CloudHSM cluster.

You can create and use CMKs in your custom key stores only when its connection state is "CONNECTED".

The value is "DISCONNECTED" if the key store has never been connected or you use the DisconnectCustomKeyStore operation to disconnect it. If the value is "CONNECTED" but you are having trouble using the custom key store, make sure that its associated AWS CloudHSM cluster is active and contains at least one active HSM.

A value of "FAILED" indicates that an attempt to connect was unsuccessful. The "ConnectionErrorCode" field in the response indicates the cause of the failure. For help resolving a connection failure, see Troubleshooting a Custom Key Store (https://docs.aws.amazon.com/kms/latest/developerguide/fix-keystore.html) in the AWS Key Management Service Developer Guide.

The date and time when the custom key store was created.

A unique identifier for the custom key store.

The user-specified friendly name for the custom key store.

The trust anchor certificate of the associated AWS CloudHSM cluster. When you initialize the cluster (https://docs.aws.amazon.com/cloudhsm/latest/userguide/initialize-cluster.html#sign-csr), you create this certificate and save it in the "customerCA.crt" file.

This class forms part of Paws, describing an object used in Paws::KMS

The source code is located here: <https://github.com/pplu/aws-sdk-perl>

Please report bugs to: <https://github.com/pplu/aws-sdk-perl/issues>

2022-06-01 perl v5.40.2

Search for    or go to Top of page |  Section 3 |  Main Index

Powered by GSP Visit the GSP FreeBSD Man Page Interface.
Output converted with ManDoc.