Did this page help you? Yes No Tell us about it...

Common Errors

Topics

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 section in the Amazon SQS Developer Guide.

	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.

List of Errors

Error	Description	HTTP Status Code
`AccessDenied`	Access to the resource is denied.	403
`AuthFailure`	A value used for authentication could not be validated, such as `Signature`. For an example, see Example Response for AuthFailure Error.	401
`AWS.SimpleQueueService.InternalError`	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.SimpleQueueService.NonExistentQueue`	Queue does not exist.	400
`ConflictingQueryParameter`	The query parameter `<parameter>` is invalid. Its structure conflicts with that of another parameter.	400
`InternalError`	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
`InvalidAccessKeyId`	AWS was not able to validate the provided access credentials.	401
`InvalidAction`	The action specified was invalid.	400
`InvalidAddress`	The address `<address>` is not valid for this web service.	404
`InvalidHttpRequest`	Invalid HTTP request. Reason: `<reason>`.	400
`InvalidParameterCombination`	Two parameters were specified that cannot be used together, such as `Timestamp` and `Expires`.	400
`InvalidParameterValue`	One or more parameters cannot be validated.	400
`InvalidQueryParameter`	The query parameter `<parameter>` is invalid. Please see service documentation for correct syntax.	400
`InvalidRequest`	The service cannot handle the request. Request is invalid.	400
`InvalidSecurity`	The provided security credentials are not valid. Reason: `<reason>`.	403
`InvalidSecurityToken`	The security token used in the request is invalid. Reason: `<reason>`.	400
`MalformedVersion`	Version not well formed: `<version>`. Must be in YYYY-MM-DD format.	400
`MissingClientTokenId`	Request must contain AWSAccessKeyId or X.509 certificate.	403
`MissingCredentials`	AWS was not able to authenticate the request: access credentials are missing.	401
`MissingParameter`	A required parameter is missing.	400
`NoSuchVersion`	An incorrect version was specified in the request.	400
`NotAuthorizedToUseVersion`	Users who sign up to use Amazon SQS after February 1, 2008, must use API version 2008-01-01 and above; not previous API versions.	401
`RequestExpired`	The timestamp used with the signature has expired.	400
`RequestThrottled`	Request is throttled.	503
`ServiceUnavailable`	A required server needed by SQS is unavailable. This error is often temporary; resend the request after a short wait.	503
`X509ParseError`	Could not parse X.509 certificate.	400

Example Response for AuthFailure Error

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>

Document Conventions
Terms of Use

Did this page help you? Yes No Tell us about it...