Impossible Cloud Documentation
  • Company overview
    • What is Impossible Cloud
  • Getting Started
    • Getting Started with Impossible Cloud Storage
      • Setting up
      • Next steps
      • Getting support
  • Feature Release Notes
    • 29th April 2025
  • Impossible cloud storage Guide
    • Storage Console URLs and API Endpoints
    • Storage Console
      • Accessing the console
        • Signing up for Impossible Cloud Storage
        • Signing in to Impossible Cloud Storage
        • Session lifetime limits
      • Interacting with the console
        • Navigating the menu
        • Using the panel
    • Buckets and Objects
      • Creating a bucket
      • Storing objects in a bucket
      • Interacting with objects
      • Creating folders in a bucket
      • Interacting with folders and buckets
      • Public File Sharing via URLs
      • Emptying a Bucket
      • Limitations
      • Versioning and object lock
        • Enabling versioning
        • Using versioning
        • Enabling object lock
        • Using object lock
    • Access keys
    • CLI User Guide
      • AWS CLI installation instructions
      • AWS CLI configuration
      • Using Impossible Cloud with AWS CLI
      • AWS CLI basic commands
      • AWS CLI advanced commands
        • Examples
      • AWS CLI for cloud-to-cloud migration scenarios
      • AWS CLI Credentials & Config chain
      • AWS CLI: IAM
        • Limitations
        • List of supported operations
        • Operations Descriptions and Examples
    • Usage
      • Storage Calculation
      • Fair use policy
    • Profile settings
      • Multi-Factor Authentication (MFA)
        • Enabling and Disabling MFA
        • MFA Reset
        • Organization-Wide Policies
  • Security
    • Securing Your Data
    • Identity Access Management (IAM)
      • Managing Users
      • Managing Groups
      • Managing Policies
    • CORS support
      • Limitations
      • CORS Configuration
  • Integrations with other applications
    • Backup Software Integrations Guides
    • Cloud Storage Browsers Integrations Guides
    • Media Management Software Integrations Guides
    • NAS Applications Integrations Guides
  • Other support resources
    • Impossible Cloud Management Console (ICMC)
    • Knowledge Base
    • Help Center
    • System Status
Powered by GitBook
On this page

Was this helpful?

Export as PDF
  1. Impossible cloud storage Guide
  2. Buckets and Objects

Versioning and object lock

PreviousLimitationsNextEnabling versioning

Last updated 1 year ago

Was this helpful?

As an enterprise-grade cloud service provider, we offer sophisticated versioning and object lock features in our Impossible Cloud Storage product. These features are designed to provide our users with advanced data protection and management capabilities. Our product is built following the industry standard, Amazon S3, so users can expect the underlying features to be similar to what they're accustomed to from other cloud providers.

  • Versioning: Our versioning feature allows you to save, retrieve, and restore any version of an object saved in a bucket. Versioning provides an extra layer of security by offering a way to restore deleted or overwritten items. This makes it simple to recover from user or application errors. Versioning is also helpful for data archiving and preservation.

  • Object lock: Our object lock feature is a data protection function that allows users to select particular objects to be immutable. This means that the objects cannot be altered or deleted by any user. Users can also set a period for an object to remain immutable, after which it can be modified or deleted. It's important to note that object lock requires versioning

Object lock differs from versioning in that object lock prevents users from permanently deleting each version of the object - while versioning simply allows users to create and delete versions of an object. Thus, with object lock you can store objects using a write-once-read-many (WORM) model.

There are three different types of retention modes:

  • Compliance: A protected object version can neither be overwritten nor deleted by any user. Additionally, its retention mode cannot be changed, and its retention period cannot be shortened. This enables the highest data protection functionality.

  • Governance: A protected object can neither be overwritten nor deleted. Additionally, its lock settings cannot be altered unless the user has been assigned the necessary permissions. Therefore, you can still grant some users permission to modify the retention settings or delete the object if required. You can also use governance mode to test retention-period settings before creating a compliance mode retention period.

  • Legal hold: This operation prevents an object version from being overwritten or deleted even if the retention period expires. Only designated users can overrule this hold.

Object lock can, for instance, help you meet regulatory requirements that require WORM storage or protect you from ransomware cases - as objects remain unchanged on our platform. For details, see our .

use cases