|« PreviousNext »|
|Did this page help you? Yes | No | Tell us about it...|
This section provides reference information about Amazon S3 errors.
The following table lists Amazon S3 error codes.
|Error Code||Description||HTTP Status Code||SOAP Fault Code Prefix|
|Access Denied||403 Forbidden||Client|
|There is a problem with your AWS account that prevents the operation from completing successfully. Please use Contact Us.||403 Forbidden||Client|
||The e-mail address you provided is associated with more than one account.||400 Bad Request||Client|
|The Content-MD5 you specified did not match what we received.||400 Bad Request||Client|
|The requested bucket name is not available. The bucket namespace is shared by all users of the system. Please select a different name and try again.||409 Conflict||Client|
|Your previous request to create the named bucket succeeded and you already own it.||409 Conflict||Client|
|The bucket you tried to delete is not empty.||409 Conflict||Client|
|This request does not support credentials.||400 Bad Request||Client|
|Cross location logging not allowed. Buckets in one geographic location cannot log information to a bucket in another location.||403 Forbidden||Client|
|Your proposed upload is smaller than the minimum allowed object size.||400 Bad Request||Client|
|Your proposed upload exceeds the maximum allowed object size.||400 Bad Request||Client|
|The provided token has expired.||400 Bad Request||Client|
|Indicates that the Versioning configuration specified in the request is invalid.||400 Bad Request||Client|
|You did not provide the number of bytes specified by the Content-Length HTTP header||400 Bad Request||Client|
|POST requires exactly one file upload per request.||400 Bad Request||Client|
|Inline data exceeds the maximum allowed size.||400 Bad Request||Client|
|We encountered an internal error. Please try again.||500 Internal Server Error||Server|
|The AWS Access Key Id you provided does not exist in our records.||403 Forbidden||Client|
|You must specify the Anonymous role.||N/A||Client|
|Invalid Argument||400 Bad Request||Client|
|The specified bucket is not valid.||400 Bad Request||Client|
|The request is not valid with the current state of the bucket.||409 Conflict||Client|
|The Content-MD5 you specified was an invalid.||400 Bad Request||Client|
|The specified location constraint is not valid. For more information about Regions, see How to Select a Region for Your Buckets.||400 Bad Request||Client|
|The operation is not valid for the current state of the object.||403 Forbidden||Client|
|One or more of the specified parts could not be found. The part might not have been uploaded, or the specified entity tag might not have matched the part's entity tag.||400 Bad Request||Client|
|The list of parts was not in ascending order.Parts list must specified in order by part number.||400 Bad Request||Client|
|All access to this object has been disabled.||403 Forbidden||Client|
|The content of the form does not meet the conditions specified in the policy document.||400 Bad Request||Client|
|The requested range cannot be satisfied.||416 Requested Range Not Satisfiable||Client|
|SOAP requests must be made over an HTTPS connection.||400 Bad Request||Client|
|The provided security credentials are not valid.||403 Forbidden||Client|
|The SOAP request body is invalid.||400 Bad Request||Client|
|The storage class you specified is not valid.||400 Bad Request||Client|
|The target bucket for logging does not exist, is not owned by you, or does not have the appropriate grants for the log-delivery group.||400 Bad Request||Client|
|The provided token is malformed or otherwise invalid.||400 Bad Request||Client|
|Couldn't parse the specified URI.||400 Bad Request||Client|
|Your key is too long.||400 Bad Request||Client|
|The XML you provided was not well-formed or did not validate against our published schema.||400 Bad Request||Client|
|The body of your POST request is not well-formed multipart/form-data.||400 Bad Request||Client|
|This happens when the user sends a malformed xml (xml that doesn't conform to the published xsd) for the configuration. The error message is, "The XML you provided was not well-formed or did not validate against our published schema."||400 Bad Request||Client|
|Your request was too big.||400 Bad Request||Client|
|Your POST request fields preceding the upload file were too large.||400 Bad Request||Client|
|Your metadata headers exceed the maximum allowed metadata size.||400 Bad Request||Client|
|The specified method is not allowed against this resource.||405 Method Not Allowed||Client|
|A SOAP attachment was expected, but none were found.||N/A||Client|
|You must provide the Content-Length HTTP header.||411 Length Required||Client|
|This happens when the user sends an empty xml document as a request. The error message is, "Request body is empty."||400 Bad Request||Client|
|The SOAP 1.1 request is missing a security element.||400 Bad Request||Client|
|Your request was missing a required header.||400 Bad Request||Client|
|There is no such thing as a logging status sub-resource for a key.||400 Bad Request||Client|
|The specified bucket does not exist.||404 Not Found||Client|
|The specified key does not exist.||404 Not Found||Client|
|The lifecycle configuration does not exist.||404 Not Found||Client|
|The specified multipart upload does not exist. The upload ID might be invalid, or the multipart upload might have been aborted or completed.||404 Not Found||Client|
|Indicates that the version ID specified in the request does not match an existing version.||404 Not Found||Client|
|A header you provided implies functionality that is not implemented.||501 Not Implemented||Server|
|Your account is not signed up for the Amazon S3 service. You must sign up before you can use Amazon S3. You can sign up at the following URL: http://aws.amazon.com/s3||403 Forbidden||Client|
|The specified bucket does not have a bucket policy.||404 Not Found||Client|
|A conflicting conditional operation is currently in progress against this resource. Please try again.||409 Conflict||Client|
|The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint.||301 Moved Permanently||Client|
|At least one of the preconditions you specified did not hold.||412 Precondition Failed||Client|
|Temporary redirect.||307 Moved Temporarily||Client|
|Object restore is already in progress.||409 Conflict||Client|
|Bucket POST must be of the enclosure-type multipart/form-data.||400 Bad Request||Client|
|Your socket connection to the server was not read from or written to within the timeout period.||400 Bad Request||Client|
|The difference between the request time and the server's time is too large.||403 Forbidden||Client|
|Requesting the torrent file of a bucket is not permitted.||400 Bad Request||Client|
|The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. For more information, see REST Authentication and SOAP Authentication for details.||403 Forbidden||Client|
|Please reduce your request rate.||503 Service Unavailable||Server|
|Please reduce your request rate.||503 Slow Down||Server|
|You are being redirected to the bucket while DNS updates.||307 Moved Temporarily||Client|
|The provided token must be refreshed.||400 Bad Request||Client|
|You have attempted to create more buckets than allowed.||400 Bad Request||Client|
|This request does not support content.||400 Bad Request||Client|
|The e-mail address you provided does not match any account on record.||400 Bad Request||Client|
|The bucket POST must contain the specified field name. If it is specified, please check the order of the fields.||400 Bad Request||Client|
When there is an error, the header information contains:
An appropriate 3xx, 4xx, or 5xx HTTP status code
The body or the response also contains information about the error. The following sample error response shows the structure of response elements common to all REST error responses.
<?xml version="1.0" encoding="UTF-8"?> <Error> <Code>NoSuchKey</Code> <Message>The resource you requested does not exist</Message> <Resource>/mybucket/myfoto.jpg</Resource> <RequestId>4442587FB7D0A2F9</RequestId> </Error>
The following table explains the REST error response elements
The error code is a string that uniquely identifies an error condition. It is meant to be read and understood by programs that detect and handle errors by type. For more information, see List of Error Codes.
Container for all error elements.
The error message contains a generic description of the error condition in English. It is intended for a human audience. Simple programs display the message directly to the end user if they encounter an error condition they don't know how or don't care to handle. Sophisticated programs with more exhaustive error handling and proper internationalization are more likely to ignore the error message.
ID of the request associated with the error.
The bucket or object that is involved in the error.
Many error responses contain additional structured data meant to be read and understood by a developer diagnosing programming errors. For example, if you send a Content-MD5 header with a REST PUT request that doesn't match the digest calculated on the server, you receive a BadDigest error. The error response also includes as detail elements the digest we calculated, and the digest you told us to expect. During development, you can use this information to diagnose the error. In production, a well-behaved program might include this information in its error log.
For information about general response elements, go to Error Responses.
In SOAP, an error result is returned to the client as a SOAP fault, with the HTTP response code 500. If you do not receive a SOAP fault, then your request was successful. The Amazon S3 SOAP fault code is comprised of a standard SOAP 1.1 fault code (either "Server" or "Client") concatenated with the Amazon S3-specific error code. For example: "Server.InternalError" or "Client.NoSuchBucket". The SOAP fault string element contains a generic, human readable error message in English. Finally, the SOAP fault detail element contains miscellaneous information relevant to the error.
For example, if you attempt to delete the object "Fred", which does not exist, the body of the SOAP response contains a "NoSuchKey" SOAP fault.
The following example shows a sample SOAP error response.
<soapenv:Body> <soapenv:Fault> <Faultcode>soapenv:Client.NoSuchKey</Faultcode> <Faultstring>The specified key does not exist.</Faultstring> <Detail> <Key>Fred</Key> </Detail> </soapenv:Fault> </soapenv:Body>
The following table explains the SOAP error response elements
Container for the key involved in the error
Container for error information.
The fault code is a string that uniquely identifies an error condition. It is meant to be read and understood by programs that detect and handle errors by type. For more information, see List of Error Codes.
The fault string contains a generic description of the error condition in English. It is intended for a human audience. Simple programs display the message directly to the end user if they encounter an error condition they don't know how or don't care to handle. Sophisticated programs with more exhaustive error handling and proper internationalization are more likely to ignore the fault string.
Identifies the key involved in the error