#[non_exhaustive]
pub enum DeleteCustomKeyStoreErrorKind {
CustomKeyStoreHasCmKsException(CustomKeyStoreHasCmKsException),
CustomKeyStoreInvalidStateException(CustomKeyStoreInvalidStateException),
CustomKeyStoreNotFoundException(CustomKeyStoreNotFoundException),
KmsInternalException(KmsInternalException),
Unhandled(Unhandled),
}
Expand description
Types of errors that can occur for the DeleteCustomKeyStore
operation.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
CustomKeyStoreHasCmKsException(CustomKeyStoreHasCmKsException)
The request was rejected because the custom key store contains KMS keys. After verifying that you do not need to use the KMS keys, use the ScheduleKeyDeletion
operation to delete the KMS keys. After they are deleted, you can delete the custom key store.
CustomKeyStoreInvalidStateException(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
CreateKey
orGenerateRandom
operation in a custom key store that is not connected. These operations are valid only when the custom key storeConnectionState
isCONNECTED
. -
You requested the
UpdateCustomKeyStore
orDeleteCustomKeyStore
operation on a custom key store that is not disconnected. This operation is valid only when the custom key storeConnectionState
isDISCONNECTED
. -
You requested the
ConnectCustomKeyStore
operation on a custom key store with aConnectionState
ofDISCONNECTING
orFAILED
. This operation is valid for all otherConnectionState
values.
CustomKeyStoreNotFoundException(CustomKeyStoreNotFoundException)
The request was rejected because KMS cannot find a custom key store with the specified key store name or ID.
KmsInternalException(KmsInternalException)
The request was rejected because an internal exception occurred. The request can be retried.
Unhandled(Unhandled)
An unexpected error occurred (e.g., invalid JSON returned by the service or an unknown error code).
When logging an error from the SDK, it is recommended that you either wrap the error in
DisplayErrorContext
, use another
error reporter library that visits the error’s cause/source chain, or call
Error::source
for more details about the underlying cause.