The Rekognition connector can return errors when input validation fails, authentication or authorization is unsuccessful, image processing limits are exceeded, or Amazon Rekognition cannot process the submitted image. These errors can be handled within a process to support exception handling, troubleshooting, and recovery workflows.
Some errors originate from the connector itself, while others are returned by Amazon Rekognition or related AWS services.
The following errors can be returned by the Rekognition connector:
| Error | Description |
|---|---|
| MISSING_INPUT | A required input parameter was not provided. Verify that all mandatory connector inputs are mapped and contain values. |
| INVALID_INPUT | An input parameter contains an invalid value or unsupported data type. Verify that the input matches the format expected by the connector action. |
| INVALID_RESULT_FORMAT | The response returned by Amazon Rekognition could not be parsed by the connector. This can occur when the response format is unexpected or invalid. |
| PROVISIONED_THROUGHPUT_EXCEEDED | The number of requests exceeded the configured throughput limit. Retry the operation after a delay or reduce the request rate. |
| ACCESS_DENIED | The configured AWS user or role is not authorized to perform the requested Rekognition operation. Verify IAM permissions and resource access. |
| IMAGE_TOO_LARGE | The submitted image exceeds the size limits supported by Amazon Rekognition. Reduce the image size before processing. |
| INVALID_IMAGE_FORMAT | The image format is not supported by Amazon Rekognition. Verify that the file is a supported image type. |
| LIMIT_EXCEEDED | An Amazon Rekognition service limit has been exceeded. Review service quotas and request limits. |
| THROTTLING_ERROR | Amazon Rekognition is temporarily unable to process the request due to throttling. Retry the request after a delay. |
| UNKNOWN_ERROR | An unexpected error occurred during connector execution. Review connector configuration, image content, and AWS service availability for possible causes. |
| BAD_REQUEST | The request could not be processed because the request syntax or content was invalid. |
| UNAUTHORIZED | Authentication information is missing or invalid. Verify the configured AWS credentials. |
| FORBIDDEN | The request was understood, but the configured AWS user or role does not have sufficient permissions to perform the requested operation. |
| NOT_FOUND | The specified resource could not be found. Verify configuration values and AWS resources. |
| METHOD_NOT_ALLOWED | The requested operation is not supported for the targeted resource. |
| NOT_ACCEPTABLE | The service cannot produce a response that matches the request requirements. |
| REQUEST_TIMEOUT | The request was not completed within the allowed time period. |
| CONFLICT | The request conflicts with the current state of the resource. |
| GONE | The requested resource is no longer available. |
| UNPROCESSABLE_ENTITY | The request was syntactically valid, but the service could not process the supplied values or instructions. |
| LOCKED | The requested resource is currently locked and cannot be processed. |
| FAILED_DEPENDENCY | The operation failed because a dependent request, service, or resource failed. |
| INTERNAL_SERVER_ERROR | The service encountered an unexpected condition that prevented it from fulfilling the request. |
| NOT_IMPLEMENTED | The requested functionality is not supported by the service. |
| BAD_GATEWAY | An upstream service returned an invalid response. |
| SERVICE_UNAVAILABLE | The service is temporarily unavailable or unable to process requests. |
| GATEWAY_TIMEOUT | The service did not receive a response from an upstream system within the expected time period. |