#[non_exhaustive]
pub enum AcceptResourceShareInvitationErrorKind {
IdempotentParameterMismatchException(IdempotentParameterMismatchException),
InvalidClientTokenException(InvalidClientTokenException),
MalformedArnException(MalformedArnException),
OperationNotPermittedException(OperationNotPermittedException),
ResourceShareInvitationAlreadyAcceptedException(ResourceShareInvitationAlreadyAcceptedException),
ResourceShareInvitationAlreadyRejectedException(ResourceShareInvitationAlreadyRejectedException),
ResourceShareInvitationArnNotFoundException(ResourceShareInvitationArnNotFoundException),
ResourceShareInvitationExpiredException(ResourceShareInvitationExpiredException),
ServerInternalException(ServerInternalException),
ServiceUnavailableException(ServiceUnavailableException),
Unhandled(Unhandled),
}Expand description
Types of errors that can occur for the AcceptResourceShareInvitation operation.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
IdempotentParameterMismatchException(IdempotentParameterMismatchException)
The client token input parameter was matched one used with a previous call to the operation, but at least one of the other input parameters is different from the previous call.
InvalidClientTokenException(InvalidClientTokenException)
The client token is not valid.
MalformedArnException(MalformedArnException)
The format of an Amazon Resource Name (ARN) is not valid.
OperationNotPermittedException(OperationNotPermittedException)
The requested operation is not permitted.
The specified invitation was already accepted.
The specified invitation was already rejected.
The specified Amazon Resource Name (ARN) for an invitation was not found.
The specified invitation is expired.
ServerInternalException(ServerInternalException)
The service could not respond to the request due to an internal problem.
The service is not available.
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.