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.
Yandex Object Storage
    • Overview
    • Bucket
    • Object
    • Bucket versioning
    • Object lock
    • Partial object updates
    • Encryption
    • Object lifecycles
    • CORS
    • Hosting static websites
    • Pre-signed URLs
    • Multipart upload
    • Access control list (ACL)
    • Bucket policy
    • Uploading files via an HTML form
    • Storage class
    • Bucket actions logging mechanism
    • Backups
    • TLS protocol
    • Labels
    • S3 Select query language
    • Quotas and limits
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Bucket logs
  • Release notes
  • FAQ
  1. Concepts
  2. Bucket versioning

Bucket versioning

Written by
Yandex Cloud
Updated at March 19, 2025

Bucket versioning enables keeping a history of an object through its versions. Each version is a complete copy of an object and occupies space in Object Storage. Using version control protects your data from both accidental user actions and application faults.

Versioning is enabled at the bucket level and applies to every object in the bucket.

For more information on how to enable versioning, see Managing bucket versioning.

  • After you enable this feature, each uploaded object will get the version_id parameter. This will allow you to manage specific object versions.

  • Before versioning is enabled, each bucket object is assigned a version_id equal to null.

    When versioning is paused, the version_id of existing objects does not change. Each new object gets a null version ID. If the null version already exists, it will be overwritten.

  • Overwriting an object version results in a new object with the same ID and a randomly generated version_id.

    To access a previous version of an object, use the object ID and the version_id you need.

  • If versioning is enabled, you can restore previous object versions by following this guide.

Note

You cannot disable versioning once you enable it; however, you can pause new version creation. After you pause versioning, new objects will be saved as null versions.

When you delete an object version, it is marked as delete and no longer takes up any storage space.

You can remove irrelevant or deleted object versions from a bucket manually or by setting up an object lifecycle.

Was the article helpful?

Previous
Object
Next
Object lock
© 2025 Direct Cursus Technology L.L.C.