pub fn connection_error_code(
            mut self,
            input: crate::model::ConnectionErrorCodeType,
        ) -> Self {
            self.connection_error_code = Some(input);
            self
        }
/// <p>Describes the connection error. This field appears in the response only when the <code>ConnectionState</code> is <code>FAILED</code>. For help resolving these errors, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/fix-keystore.html#fix-keystore-failed">How to Fix a Connection Failure</a> in <i>Key Management Service Developer Guide</i>.</p>
/// <p>Valid values are:</p>
/// <ul>
/// <li> <p> <code>CLUSTER_NOT_FOUND</code> - KMS cannot find the CloudHSM cluster with the specified cluster ID.</p> </li>
/// <li> <p> <code>INSUFFICIENT_CLOUDHSM_HSMS</code> - The associated CloudHSM cluster does not contain any active HSMs. To connect a custom key store to its CloudHSM cluster, the cluster must contain at least one active HSM.</p> </li>
/// <li> <p> <code>INTERNAL_ERROR</code> - KMS could not complete the request due to an internal error. Retry the request. For <code>ConnectCustomKeyStore</code> requests, disconnect the custom key store before trying to connect again.</p> </li>
/// <li> <p> <code>INVALID_CREDENTIALS</code> - KMS does not have the correct password for the <code>kmsuser</code> crypto user in the CloudHSM cluster. Before you can connect your custom key store to its CloudHSM cluster, you must change the <code>kmsuser</code> account password and update the key store password value for the custom key store.</p> </li>
/// <li> <p> <code>NETWORK_ERRORS</code> - Network errors are preventing KMS from connecting to the custom key store.</p> </li>
/// <li> <p> <code>SUBNET_NOT_FOUND</code> - A subnet in the CloudHSM cluster configuration was deleted. If KMS cannot find all of the subnets in the cluster configuration, attempts to connect the custom key store to the 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 <a href="https://docs.aws.amazon.com/kms/latest/developerguide/fix-keystore.html#fix-keystore-failed">How to Fix a Connection Failure</a> in the <i>Key Management Service Developer Guide</i>.</p> </li>
/// <li> <p> <code>USER_LOCKED_OUT</code> - The <code>kmsuser</code> CU account is locked out of the associated CloudHSM cluster due to too many failed password attempts. Before you can connect your custom key store to its CloudHSM cluster, you must change the <code>kmsuser</code> account password and update the key store password value for the custom key store.</p> </li>
/// <li> <p> <code>USER_LOGGED_IN</code> - The <code>kmsuser</code> CU account is logged into the the associated CloudHSM cluster. This prevents KMS from rotating the <code>kmsuser</code> account password and logging into the cluster. Before you can connect your custom key store to its CloudHSM cluster, you must log the <code>kmsuser</code> CU out of the cluster. If you changed the <code>kmsuser</code> password to log into the cluster, you must also and update the key store password value for the custom key store. For help, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/fix-keystore.html#login-kmsuser-2">How to Log Out and Reconnect</a> in the <i>Key Management Service Developer Guide</i>.</p> </li>
/// <li> <p> <code>USER_NOT_FOUND</code> - KMS cannot find a <code>kmsuser</code> CU account in the associated CloudHSM cluster. Before you can connect your custom key store to its CloudHSM cluster, you must create a <code>kmsuser</code> CU account in the cluster, and then update the key store password value for the custom key store.</p> </li>
/// </ul>
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 in Key Management Service Developer Guide.
Valid values are:

  CLUSTER_NOT_FOUND - KMS cannot find the CloudHSM cluster with the specified cluster ID. 
  INSUFFICIENT_CLOUDHSM_HSMS - The associated CloudHSM cluster does not contain any active HSMs. To connect a custom key store to its CloudHSM cluster, the cluster must contain at least one active HSM. 
  INTERNAL_ERROR - 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 - KMS does not have the correct password for the kmsuser crypto user in the CloudHSM cluster. Before you can connect your custom key store to its 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 KMS from connecting to the custom key store. 
  SUBNET_NOT_FOUND - A subnet in the CloudHSM cluster configuration was deleted. If KMS cannot find all of the subnets in the cluster configuration, attempts to connect the custom key store to the 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 in the Key Management Service Developer Guide. 
  USER_LOCKED_OUT - The kmsuser CU account is locked out of the associated CloudHSM cluster due to too many failed password attempts. Before you can connect your custom key store to its 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 CloudHSM cluster. This prevents KMS from rotating the kmsuser account password and logging into the cluster. Before you can connect your custom key store to its 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 in the Key Management Service Developer Guide. 
  USER_NOT_FOUND - KMS cannot find a kmsuser CU account in the associated CloudHSM cluster. Before you can connect your custom key store to its 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. 

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 in Key Management Service Developer Guide . Valid values are : CLUSTER_NOT_FOUND - KMS cannot find the CloudHSM cluster with the specified cluster ID . INSUFFICIENT_CLOUDHSM_HSMS - The associated CloudHSM cluster does not contain any active HSMs . To connect a custom key store to its CloudHSM cluster the cluster must contain at least one active HSM . INTERNAL_ERROR - 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 - KMS does not have the correct password for the kmsuser crypto user in the CloudHSM cluster . Before you can connect your custom key store to its 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 KMS from connecting to the custom key store . SUBNET_NOT_FOUND - A subnet in the CloudHSM cluster configuration was deleted . If KMS cannot find all of the subnets in the cluster configuration attempts to connect the custom key store to the 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 in the Key Management Service Developer Guide . USER_LOCKED_OUT - The kmsuser CU account is locked out of the associated CloudHSM cluster due to too many failed password attempts . Before you can connect your custom key store to its 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 CloudHSM cluster . This prevents KMS from rotating the kmsuser account password and logging into the cluster . Before you can connect your custom key store to its 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 in the Key Management Service Developer Guide . USER_NOT_FOUND - KMS cannot find a kmsuser CU account in the associated CloudHSM cluster . Before you can connect your custom key store to its 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 .
pub fn connection_error_code(
            mut self,
            input: crate::model::ConnectionErrorCodeType,
        ) -> Self {
            self.connection_error_code = Some(input);
            self
        }
pub fn connection_error_code ( mut self , input : crate :: model :: ConnectionErrorCodeType , ) -> Self { self . connection_error_code = Some ( input ) ; self }
<p>Describes the connection error.
<p > Describes the connection error .
mut self
input
crate::model::ConnectionErrorCodeType
mut self
input
crate::model::ConnectionErrorCodeType