This section lists the errors shared by all actions. Errors specific to an action are listed in the topic about that action. For information about the structure of an error response, see Responses.
![]() | Important |
|---|---|
We might throttle requests to Amazon SQS as necessary. When we throttle, we return a 503 (service unavailable) HTTP status code. Your system should be prepared to retry any request that receives a 503 code. |
![]() | Note |
|---|---|
For SOAP 1.1, SQS returns HTTP status code 500 for all faults. For SOAP 1.2, SQS returns the HTTP status code shown in the following table. |
| Error | Description | HTTP Status Code |
|---|---|---|
| Access to the resource is denied. | 403 |
| A value used for authentication could not be validated, such as | 401 |
| There is an internal problem with SQS, which you cannot resolve. Retry the request. If the problem persists, contact us through the Amazon SQS Discussion Forums. | 500 |
| Queue does not exist. | 400 |
| The query parameter | 400 |
|
| The element | 403 |
| There is an internal problem with SQS, which you cannot resolve. Retry the request. If the problem persists, contact us through the Amazon SQS Discussion Forums. | 500 |
| AWS was not able to validate the provided access credentials. | 401 |
| The action specified was invalid. | 400 |
| The address | 404 |
| Invalid HTTP request. Reason: | 400 |
| Two parameters were specified that cannot be used together, such as | 400 |
| One or more parameters cannot be validated. | 400 |
| The query parameter | 400 |
| The service cannot handle the request. Request is invalid. | 400 |
| The provided security credentials are not valid. Reason: | 403 |
| The security token used in the request is invalid. Reason: | 400 |
| Invalid SOAP Signature. Reason: | 400 |
| Version not well formed: | 400 |
| Request must contain AWSAccessKeyId or X.509 certificate. | 403 |
| AWS was not able to authenticate the request: access credentials are missing. | 401 |
| A required parameter is missing. | 400 |
| An incorrect version was specified in the request. | 400 |
| Users who sign up to use Amazon SQS after February 1, 2008, must use API version 2008-01-01 and not previous API versions. | 401 |
| The timestamp used with the signature has expired. | 400 |
| Request is throttled. | 503 |
| A required server needed by SQS is unavailable. This error is often temporary; resend the request after a short wait. | 503 |
| Timestamp must be in XSD date format. | 400 |
| The <Action> request element is missing in SOAP 1.1 request. | 400 |
| Could not find the SOAP body in the request. | 400 |
| Could not find the SOAP envelope in the request. | 400 |
| Could not parse the SOAP envelope. | 400 |
| Envelope Namespace must be for either SOAP 1.1: http://schemas.xmlsoap.org/soap/envelope, or SOAP 1.2: http://www.w3.org/2003/05/soap-envelope. | 400 |
| Signed info is corrupt. | 400 |
| Timestamp for created date must be in ISO8601 format. | 400 |
| BinarySecurityToken must have EncodingType of | 400 |
| Timestamp for expires date must be in ISO8601 format. | 400 |
| BinarySecurityToken has bad ValueType. | 400 |
| BinarySecurityToken must have attribute ValueType. | 400 |
| Request must not contain more than one BinarySecurityToken with valueType | 400 |
| Request must not contain more than one BinarySecurityToken with valueType | 400 |
| Error while processing signature element. | 400 |
| SignatureValue is missing or empty. | 400 |
| Request has no SignedInfo. | 400 |
| Request has expired. | 400 |
| Timestamp must have Expires element. | 400 |
| Security Header Element is missing the timestamp element. | 400 |
| Request cannot contain both Credential and an X.509 certificate. | 400 |
| Could not parse X.509 certificate. | 400 |
The following sample response is for an AuthFailure error.
<ErrorResponse>
<Error>
<Type>
Sender
</Type>
<Code>
AuthFailure
</Code>
<Message>
The provided signature is not valid for this access token
</Message>
<Detail/>
</Error>
<RequestID>
ef3aba6a-dc84-4937-91bf-cef2ddd6775a
</RequestID>
</ErrorResponse>The following sample response shows a SOAP fault for an ElementNotSigned error.
<soap:Envelope
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:aws="http://webservices.amazon.com/AWSFault/2005-15-09">
<soap:Body>
<soap:Fault>
<faultcode>aws:Client.ElementNotSigned</faultcode>
<faultstring>The element Timestamp is not signed.</faultstring>
<detail>
<aws:RequestId xmlns:aws="http://webservices.amazon.com/AWSFault/2005-15-09">
ba5f0ea7-bc42-45a4-804b-6b9329b6e44f
</aws:RequestId>
</detail>
</soap:Fault>
</soap:Body>
</soap:Envelope>