#[non_exhaustive]
pub enum DetectTextErrorKind {
AccessDeniedException(AccessDeniedException),
ImageTooLargeException(ImageTooLargeException),
InternalServerError(InternalServerError),
InvalidImageFormatException(InvalidImageFormatException),
InvalidParameterException(InvalidParameterException),
InvalidS3ObjectException(InvalidS3ObjectException),
ProvisionedThroughputExceededException(ProvisionedThroughputExceededException),
ThrottlingException(ThrottlingException),
Unhandled(Unhandled),
}
Expand description
Types of errors that can occur for the DetectText
operation.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
AccessDeniedException(AccessDeniedException)
You are not authorized to perform the action.
ImageTooLargeException(ImageTooLargeException)
The input image size exceeds the allowed limit. If you are calling DetectProtectiveEquipment, the image size or resolution exceeds the allowed limit. For more information, see Guidelines and quotas in Amazon Rekognition in the Amazon Rekognition Developer Guide.
InternalServerError(InternalServerError)
Amazon Rekognition experienced a service issue. Try your call again.
InvalidImageFormatException(InvalidImageFormatException)
The provided image format is not supported.
InvalidParameterException(InvalidParameterException)
Input parameter violated a constraint. Validate your parameter before calling the API operation again.
InvalidS3ObjectException(InvalidS3ObjectException)
Amazon Rekognition is unable to access the S3 object specified in the request.
ProvisionedThroughputExceededException(ProvisionedThroughputExceededException)
The number of requests exceeded your throughput limit. If you want to increase this limit, contact Amazon Rekognition.
ThrottlingException(ThrottlingException)
Amazon Rekognition is temporarily unable to process the request. Try your call again.
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.