Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
  • Blog
  • Pricing
  • Documentation
Yandex project
© 2025 Yandex.Cloud LLC
Yandex Object Storage
  • Terraform reference
    • Authentication with the API
      • How to use the API
      • Signing requests
        • All services and methods
        • Common request headers
        • Common response headers
        • Responses
  • Monitoring metrics
  • Audit Trails events
  • Bucket logs
  • Release notes
  • FAQ

In this article:

  • Successful response
  • Error response
  • Error codes
  1. API reference
  2. REST (Amazon S3-compatible)
  3. REST
  4. Responses

Responses

Written by
Yandex Cloud
Updated at March 19, 2025
  • Successful response
  • Error response
    • Error codes

Successful responseSuccessful response

If there are no errors, Object Storage returns a 2xx HTTP code. The response code and body are request-specific and given in request descriptions.

Error responseError response

In case of an error, Object Storage returns a message with the relevant HTTP code and its additional description in XML format.

<?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>
Tag Description
Code Error code.

You can find a list of codes below.
Message Error description in English.
RequestId ID of the request that resulted in an error.

It equals the X-Amz-Request-Id header value.
Resource Bucket or object the error occurred with.

Error codesError codes

HTTP

Error code

Description

301

PermanentRedirect

The specified bucket should always be accessed using the address returned in the response.

307

Redirect

The specified bucket should temporarily be accessed using the address returned in the response.

307

TemporaryRedirect

Redirect while the DNS is being updated.

400

BadDigest

The hash provided in the Content-MD5 header does not match the one calculated on the Object Storage side.

400

CloudTotalAliveSizeQuotaExceed

After uploading the object, the quota will be exceeded. Request a quota increase or delete the objects you do not need and then upload the object again.

400

CredentialsNotSupported

Credentials are not supported.

400

EntityTooSmall

The size of an object to upload is smaller than the minimum allowed size.

400

EntityTooLarge

The size of an object to upload is greater than the maximum allowed size.

400

ExpiredToken

The token is expired.

400

IncompleteBody

The sent data size is smaller than stated in the Content-Length header.

400

IncorrectNumberOfFilesInPostRequest

The POST method requires exactly one file upload per request.

400

InlineDataTooLarge

The request data exceeds the maximum allowed size.

400

InvalidDigest

The hash provided in the Content-MD5 header is invalid.

400

InvalidArgument

The argument is invalid.

400

InvalidBucketName

The name of the bucket is invalid.

400

InvalidPart

One or more parts of a multipart upload were not found. Make sure the list is correct. The missing parts may not have been uploaded.

400

InvalidPartOrder

The list of parts of a multipart upload is incorrect. The parts must be sorted by number in ascending order.

400

InvalidRequest

Use AWS4-HMAC-SHA256.

400

BucketMaxSizeExceeded

Attempt to exceed the maximum bucket size.

The response contains the following error description: "You have attempted to exceed the max size configured for the bucket."

400

InvalidStorageClass

The storage class is invalid.

400

InvalidTargetBucketForLogging

The bucket does not exist, or you are not the owner of the bucket, or the log delivery group does not have sufficient permissions.

400

InvalidToken

The token is malformed or otherwise invalid.

400

InvalidURI

Failed to parse the provided URI.

400

KeyTooLongError

The key is too long.

400

MalformedACLError

The provided XML document is malformed or does not match the schema.

400

MalformedPOSTRequest

The request body does not match the multipart/form-data format.

400

MalformedXML

The provided XML document is malformed or does not match the schema.

400

MaxMessageLengthExceeded

The maximum allowed request length is exceeded.

400

MaxPostPreDataLengthExceededError

The HTTP message header exceeded the allowed length.

400

MetadataTooLarge

The metadata headers exceed the allowed size.

400

MissingRequestBodyError

The request body is empty.

The error occurs when sending an empty XML document.

400

MissingSecurityHeader

The required header is missing.

400

NoLoggingStatusForKey

There is no logging status for the key.

400

RequestIsNotMultiPartContent

The request must contain data of the multipart/form-data type.

400

RequestTimeout

Read/write timeout.

400

TokenRefreshRequired

Refresh your token.

400

TooManyBuckets

After creating the object, the quota will be exceeded. Request a quota increase or delete the buckets you do not need and then create the bucket again.

400

UnexpectedContent

There should be no content in the request.

400

UnresolvableGrantByEmailAddress

The email address does not match any recorded account.

400

UserKeyMustBeSpecified

The request must contain the header specified in the error description.

403

AccessDenied

Access is denied.

403

AccountProblem

There is an account problem preventing successful completion of the operation.

Contact Yandex Cloud support team.

403

InvalidAccessKeyId

Unknown key.

403

InvalidObjectState

The request cannot be executed for the current state of the object.

403

InvalidPayer

Access to the object is blocked.

403

InvalidSecurity

The provided secret keys are not valid.

403

NotSignedUp

This account is not allowed to use Object Storage.

403

RequestTimeTooSkewed

The difference between the request sending time and the time on the server is too big.

403

SignatureDoesNotMatch

The provided request signature does not match the one calculated by Object Storage.

404

NoSuchBucket

The specified bucket does not exist.

404

NoSuchKey

The specified key does not exist.

404

NoSuchUpload

The specified multipart upload does not exist.

The error occurs in the following cases:
- Invalid upload ID is specified.
- Upload is aborted.
- Upload is complete.

404

NoSuchTagSet

The specified bucket does not have any tag assigned.

405

MethodNotAllowed

The HTTP method is not allowed for the specified resource.

409

BucketAlreadyExists

A bucket with the same name already exists. Choose a different name.

409

BucketNotEmpty

The bucket you are trying to delete is not empty.

409

InvalidBucketState

The request cannot be executed for the current state of the bucket.

409

OperationAborted

Conflicting conditional operations.

411

MissingContentLength

Add Content-Length to the headers.

412

Precondition Failed

One of the conditions specified in the request is not satisfied.

416

InvalidRange

Invalid range in the Range header.

429

TooManyRequests

Too many requests to Object Storage. Reduce the request rate.

500

InternalError

Internal error in Object Storage. Repeat the request.

501

NotImplemented

The provided header is not processed by Object Storage.

503

ServiceUnavailable

Object Storage is not available.
Reduce your request rate.

503

SlowDown

Reduce your request rate.

See alsoSee also

  • Debugging requests using the AWS CLI
  • Example of sending a signed request using curl
  • Code example for generating a signature

Was the article helpful?

Previous
Common response headers
Next
Overview
Yandex project
© 2025 Yandex.Cloud LLC