Enum aws_sdk_managedblockchain::error::CreateAccessorErrorKind

#[non_exhaustive]
pub enum CreateAccessorErrorKind {
    AccessDeniedException(AccessDeniedException),
    InternalServiceErrorException(InternalServiceErrorException),
    InvalidRequestException(InvalidRequestException),
    ResourceAlreadyExistsException(ResourceAlreadyExistsException),
    ResourceLimitExceededException(ResourceLimitExceededException),
    ThrottlingException(ThrottlingException),
    Unhandled(Unhandled),
}

Types of errors that can occur for the CreateAccessor operation.

Variants (Non-exhaustive)

Non-exhaustive enums could have additional variants added in future. Therefore, when matching against variants of non-exhaustive enums, an extra wildcard arm must be added to account for any future variants.

AccessDeniedException(AccessDeniedException)

You don't have sufficient access to perform this action.

InternalServiceErrorException(InternalServiceErrorException)

The request processing has failed because of an unknown error, exception or failure.

InvalidRequestException(InvalidRequestException)

The action or operation requested is invalid. Verify that the action is typed correctly.

ResourceAlreadyExistsException(ResourceAlreadyExistsException)

A resource request is issued for a resource that already exists.

ResourceLimitExceededException(ResourceLimitExceededException)

The maximum number of resources of that type already exist. Ensure the resources requested are within the boundaries of the service edition and your account limits.

ThrottlingException(ThrottlingException)

The request or operation couldn't be performed because a service is throttling requests. The most common source of throttling errors is creating resources that exceed your service limit for this resource type. Request a limit increase or delete unused resources if possible.

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.

Trait Implementations

impl Debug for CreateAccessorErrorKind

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.