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
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
All solutions
    • All solutions for Object Storage
    • Resolving the Bucket not empty error when deleting a bucket from Object Storage
    • Resolving errors of access to a bucket with an assigned security policy
    • Resolving error 429
    • Resolving the "409 BucketAlreadyExists" error
    • Resolving the error of access to S3 buckets from a DataProc 1.4 cluster
    • Resolving error 403 (header is not provided when using the OPTION method)
    • Resolving certificate error
    • Resolving GATEWAY_REQUEST_ERROR
    • Resolving issues with incorrect MIME-types of objects when uploading them to Object Storage
    • Moving data from an Object Storage bucket to an ice storage
    • Restricting access to an Object Storage bucket using an IP range from Cloud CDN
    • Moving bucket contents to another bucket in the same the folder
    • Accessing Object Storage API directly, bypassing the SDK
    • Viewing and deleting incomplete uploads
    • How to determine the speed of data upload and download
    • How to configure cache-control headers for objects in a bucket during HTTP requests
    • How to restrict access to a bucket for a user
    • How to connect your own domain to a bucket
    • How to change the storage class

In this article:

  • Issue description
  • Solution
  1. Object Storage
  2. Resolving error 429

Resolving error 429

Written by
Yandex Cloud
Updated at October 30, 2024
  • Issue description
  • Solution

Issue descriptionIssue description

When trying to delete several files simultaneously, you see this error:

message: ; status: 429; description: ; code: undefined; Request ID: undefined; Trace ID: undefined;

SolutionSolution

This error tells you are sending too many requests. When this error occurs, we recommend reducing the frequency of calls to Object Storage.

Note

You can see all the error codes and API Object Storage responses in the documentation.

For bulk deletion of objects, we recommend using AWS CLI to recursively delete files with this command:

aws s3 --endpoint-url=https://storage.yandexcloud.net rm s3://bucket-name --recursive

You can also recursively delete all files with an identical prefix. The following command will delete all files having the my-folder/ prefix in my-bucket:

aws s3 --endpoint-url=https://storage.yandexcloud.net rm s3://my-bucket/my-folder/ --recursive

A guide for installing and configuring the AWS CLI is also available in our documentation.

Was the article helpful?

Previous
Resolving errors of access to a bucket with an assigned security policy
Next
Resolving the "409 BucketAlreadyExists" error
© 2025 Direct Cursus Technology L.L.C.