Enum aws_sdk_iam::error::DeleteRoleErrorKind
source · #[non_exhaustive]
pub enum DeleteRoleErrorKind {
ConcurrentModificationException(ConcurrentModificationException),
DeleteConflictException(DeleteConflictException),
LimitExceededException(LimitExceededException),
NoSuchEntityException(NoSuchEntityException),
ServiceFailureException(ServiceFailureException),
UnmodifiableEntityException(UnmodifiableEntityException),
Unhandled(Unhandled),
}Expand description
Types of errors that can occur for the DeleteRole operation.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
ConcurrentModificationException(ConcurrentModificationException)
The request was rejected because multiple requests to change this object were submitted simultaneously. Wait a few minutes and submit your request again.
DeleteConflictException(DeleteConflictException)
The request was rejected because it attempted to delete a resource that has attached subordinate entities. The error message describes these entities.
LimitExceededException(LimitExceededException)
The request was rejected because it attempted to create resources beyond the current Amazon Web Services account limits. The error message describes the limit exceeded.
NoSuchEntityException(NoSuchEntityException)
The request was rejected because it referenced a resource entity that does not exist. The error message describes the resource.
ServiceFailureException(ServiceFailureException)
The request processing has failed because of an unknown error, exception or failure.
UnmodifiableEntityException(UnmodifiableEntityException)
The request was rejected because only the service that depends on the service-linked role can modify or delete the role on your behalf. The error message includes the name of the service that depends on this service-linked role. You must request the change through that service.
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.