Amazon Simple Storage Service
API Reference (API Version 2006-03-01)

Error Responses

This section provides reference information about Amazon S3 errors.


SOAP support over HTTP is deprecated, but it is still available over HTTPS. New Amazon S3 features will not be supported for SOAP. We recommend that you use either the REST API or the AWS SDKs.

REST Error Responses

When there is an error, the header information contains:

  • Content-Type: application/xml

  • 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"?>
  <Message>The resource you requested does not exist</Message>

The following table explains the REST error response elements

Name Description

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.

Type: String

Ancestor: Error


Container for all error elements.

Type: Container

Ancestor: None


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.

Type: String

Ancestor: Error


ID of the request associated with the error.

Type: String

Ancestor: Error


The bucket or object that is involved in the error.

Type: String

Ancestor: 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.

List of Error Codes

The following table lists Amazon S3 error codes.

Error CodeDescriptionHTTP Status CodeSOAP Fault Code Prefix
AccessDeniedAccess Denied403 ForbiddenClient
AccountProblemThere is a problem with your AWS account that prevents the operation from completing successfully. Please use Contact Us.403 ForbiddenClient


The email address you provided is associated with more than one account.400 Bad RequestClient
BadDigestThe Content-MD5 you specified did not match what we received.400 Bad RequestClient
BucketAlreadyExistsThe 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 ConflictClient
BucketAlreadyOwnedByYouYour previous request to create the named bucket succeeded and you already own it. You get this error in all AWS regions except US East (N. Virginia) region, us-east-1. In us-east-1 region, you will get 200 OK, but it is no-op (if bucket exists it Amazon S3 will not do anything).

409 Conflict (in all regions except US East (N. Virginia) region).

BucketNotEmptyThe bucket you tried to delete is not empty.409 ConflictClient
CredentialsNotSupportedThis request does not support credentials.400 Bad RequestClient
CrossLocationLoggingProhibitedCross-location logging not allowed. Buckets in one geographic location cannot log information to a bucket in another location.403 ForbiddenClient
EntityTooSmallYour proposed upload is smaller than the minimum allowed object size.400 Bad RequestClient
EntityTooLargeYour proposed upload exceeds the maximum allowed object size.400 Bad RequestClient
ExpiredTokenThe provided token has expired.400 Bad RequestClient
IllegalVersioningConfigurationException Indicates that the versioning configuration specified in the request is invalid.400 Bad RequestClient
IncompleteBodyYou did not provide the number of bytes specified by the Content-Length HTTP header400 Bad RequestClient
IncorrectNumberOfFilesInPostRequestPOST requires exactly one file upload per request.400 Bad RequestClient
InlineDataTooLargeInline data exceeds the maximum allowed size.400 Bad RequestClient
InternalErrorWe encountered an internal error. Please try again.500 Internal Server ErrorServer
InvalidAccessKeyIdThe AWS access key Id you provided does not exist in our records.403 ForbiddenClient
InvalidAddressingHeaderYou must specify the Anonymous role.N/AClient
InvalidArgumentInvalid Argument400 Bad RequestClient
InvalidBucketNameThe specified bucket is not valid.400 Bad RequestClient
InvalidBucketStateThe request is not valid with the current state of the bucket.409 ConflictClient
InvalidDigestThe Content-MD5 you specified is not valid.400 Bad RequestClient
InvalidEncryptionAlgorithmErrorThe encryption request you specified is not valid. The valid value is AES256.400 Bad RequestClient
InvalidLocationConstraintThe specified location constraint is not valid. For more information about regions, see How to Select a Region for Your Buckets. 400 Bad RequestClient
InvalidObjectStateThe operation is not valid for the current state of the object.403 ForbiddenClient
InvalidPartOne 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 RequestClient
InvalidPartOrderThe list of parts was not in ascending order.Parts list must specified in order by part number.400 Bad RequestClient
InvalidPayerAll access to this object has been disabled.403 ForbiddenClient
InvalidPolicyDocumentThe content of the form does not meet the conditions specified in the policy document.400 Bad RequestClient
InvalidRangeThe requested range cannot be satisfied.416 Requested Range Not SatisfiableClient
InvalidRequestPlease use AWS4-HMAC-SHA256.400 Bad RequestN/A
InvalidRequestSOAP requests must be made over an HTTPS connection.400 Bad RequestClient
InvalidRequestS3 Transfer Acceleration is not supported for buckets with non-DNS compliant names.400 Bad RequestN/A
InvalidRequestS3 Transfer Acceleration is not supported for buckets with periods (.) in their names.400 Bad RequestN/A
InvalidRequestS3 Transfer Accelerate endpoint only supports virtual style requests.400 Bad RequestN/A
InvalidRequestS3 Transfer Accelerate is not configured on this bucket.400 Bad RequestN/A
InvalidRequestS3 Transfer Accelerate is disabled on this bucket.400 Bad RequestN/A
InvalidRequestS3 Transfer Acceleration is not supported on this bucket. Contact AWS Support for more information.400 Bad RequestN/A
InvalidRequestS3 Transfer Acceleration cannot be enabled on this bucket. Contact AWS Support for more information.400 Bad RequestN/A
InvalidSecurityThe provided security credentials are not valid.403 ForbiddenClient
InvalidSOAPRequestThe SOAP request body is invalid.400 Bad RequestClient
InvalidStorageClassThe storage class you specified is not valid.400 Bad RequestClient
InvalidTargetBucketForLoggingThe 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 RequestClient
InvalidTokenThe provided token is malformed or otherwise invalid.400 Bad RequestClient
InvalidURICouldn't parse the specified URI.400 Bad RequestClient
KeyTooLongYour key is too long.400 Bad RequestClient
MalformedACLErrorThe XML you provided was not well-formed or did not validate against our published schema.400 Bad RequestClient
MalformedPOSTRequest The body of your POST request is not well-formed multipart/form-data.400 Bad RequestClient
MalformedXMLThis happens when the user sends 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 RequestClient
MaxMessageLengthExceededYour request was too big.400 Bad RequestClient
MaxPostPreDataLengthExceededErrorYour POST request fields preceding the upload file were too large.400 Bad RequestClient
MetadataTooLargeYour metadata headers exceed the maximum allowed metadata size.400 Bad RequestClient
MethodNotAllowedThe specified method is not allowed against this resource.405 Method Not AllowedClient
MissingAttachmentA SOAP attachment was expected, but none were found.N/AClient
MissingContentLengthYou must provide the Content-Length HTTP header.411 Length RequiredClient
MissingRequestBodyErrorThis happens when the user sends an empty xml document as a request. The error message is, "Request body is empty." 400 Bad RequestClient
MissingSecurityElementThe SOAP 1.1 request is missing a security element.400 Bad RequestClient
MissingSecurityHeaderYour request is missing a required header.400 Bad RequestClient
NoLoggingStatusForKeyThere is no such thing as a logging status subresource for a key.400 Bad RequestClient
NoSuchBucketThe specified bucket does not exist.404 Not FoundClient
NoSuchKeyThe specified key does not exist.404 Not FoundClient
NoSuchLifecycleConfigurationThe lifecycle configuration does not exist. 404 Not FoundClient
NoSuchUploadThe specified multipart upload does not exist. The upload ID might be invalid, or the multipart upload might have been aborted or completed.404 Not FoundClient
NoSuchVersion Indicates that the version ID specified in the request does not match an existing version.404 Not FoundClient
NotImplementedA header you provided implies functionality that is not implemented.501 Not ImplementedServer
NotSignedUpYour 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: ForbiddenClient
NoSuchBucketPolicyThe specified bucket does not have a bucket policy.404 Not FoundClient
OperationAbortedA conflicting conditional operation is currently in progress against this resource. Try again.409 ConflictClient
PermanentRedirectThe bucket you are attempting to access must be addressed using the specified endpoint. Send all future requests to this endpoint.301 Moved PermanentlyClient
PreconditionFailedAt least one of the preconditions you specified did not hold.412 Precondition FailedClient
RedirectTemporary redirect.307 Moved TemporarilyClient
RestoreAlreadyInProgressObject restore is already in progress.409 ConflictClient
RequestIsNotMultiPartContentBucket POST must be of the enclosure-type multipart/form-data.400 Bad RequestClient
RequestTimeoutYour socket connection to the server was not read from or written to within the timeout period.400 Bad RequestClient
RequestTimeTooSkewedThe difference between the request time and the server's time is too large.403 ForbiddenClient
RequestTorrentOfBucketErrorRequesting the torrent file of a bucket is not permitted.400 Bad RequestClient
SignatureDoesNotMatchThe 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 ForbiddenClient
ServiceUnavailableReduce your request rate.503 Service UnavailableServer
SlowDownReduce your request rate.503 Slow DownServer
TemporaryRedirectYou are being redirected to the bucket while DNS updates.307 Moved TemporarilyClient
TokenRefreshRequiredThe provided token must be refreshed.400 Bad RequestClient
TooManyBucketsYou have attempted to create more buckets than allowed.400 Bad RequestClient
UnexpectedContentThis request does not support content.400 Bad RequestClient
UnresolvableGrantByEmailAddressThe email address you provided does not match any account on record.400 Bad RequestClient
UserKeyMustBeSpecifiedThe bucket POST must contain the specified field name. If it is specified, check the order of the fields.400 Bad RequestClient