> For the complete documentation index, see [llms.txt](https://clients.medianova.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://clients.medianova.com/products/object-storage-stook/bucket-configuration/object-lock.md). # Object Lock Prevent objects in a Stook Bucket from being deleted until a configured retention period expires. Configure Object Lock to protect objects in a Stook Bucket from deletion for a defined retention period. Object Lock applies retention to objects written after the feature is enabled. It can be used for data that must be retained for a fixed period, such as backups, audit logs, or records subject to retention requirements. {% hint style="danger" %} Object Lock cannot be disabled after it is enabled for a Stook Bucket. Review the retention period before saving the configuration. {% endhint %} {% hint style="info" %} For complete request parameters, response schemas, and error responses, see [Bucket Settings API](/api-documentation/object-storage-stook/buckets/settings.md). {% endhint %} ## How Object Lock Works Object Lock protects each object for the configured **Retention period**, starting when the object is written. The following behavior applies: * Objects cannot normally be deleted before their retention period expires. * After the retention period expires, objects can be deleted normally. * Object Lock applies only to objects written after it is enabled. * Objects already stored in the Stook Bucket are not protected retroactively. * Changing the retention period affects only objects written after the change. * Existing objects retain the retention period assigned when they were written. Object Lock uses **governance mode**. In governance mode, a request that explicitly bypasses retention can delete a protected object version before its retention period expires if the access key has permission to bypass the retention. The master key and access keys with **All S3 Actions** have this permission. Access keys limited to specific actions do not. ## Requirements Before enabling Object Lock: * Set Versioning to **On**. * Select a retention period between 1 and 365 days. While Object Lock is enabled, Versioning cannot be suspended. ## Configure Object Lock {% stepper %} {% step %} ### **Enable Versioning** If Versioning is not already enabled, set Versioning to **On** and save the configuration. {% endstep %} {% step %} ### **Open Object Lock** On the **Bucket configuration** page, select **Object lock**.
{% endstep %} {% step %} ### **Enable Object Lock** Turn on **Enabled**. {% endstep %} {% step %} ### **Set the retention period** Enter the **Retention period** in days. The supported range is 1 to 365 days. {% endstep %} {% step %} ### **Save the configuration** Select **Save Changes**. {% endstep %} {% endstepper %} ## Configuration Fields
FieldDescriptionDefault
EnabledProtects objects written after Object Lock is enabled. Object Lock cannot be disabled after activation.Off
Retention periodNumber of days each new object is protected after it is written. Supported range: 1–365 days.—
{% hint style="info" %} For a retention period longer than 365 days, contact . {% endhint %} ## Change the Retention Period You can change the configured retention period after Object Lock is enabled. The new retention period applies only to objects written after the change. Objects already stored retain the retention period assigned when they were written. For example, changing the retention period from 30 days to 90 days does not extend the retention period of objects that were previously written with a 30-day retention period. ## Delete a Stook Bucket with Object Lock A Stook Bucket can be deleted only when it is empty, including all object versions and delete markers. Objects that are still within their retention period cannot normally be deleted. Therefore, a bucket protected by Object Lock can be emptied only as the retention periods of its objects expire. To empty the Stook Bucket: 1. Wait for the applicable retention periods to expire, then delete the objects and their versions. 2. Configure a lifecycle rule with an expiration period longer than the Object Lock retention period so that objects can be removed automatically after their retention periods expire. See Lifecycle Rules. 3. Contact [Medianova Support](mailto:support@medianova.com) if data must be removed before its retention period expires. ## Configure Object Lock with the API Use the bucket settings endpoint to enable Object Lock: ```http PATCH /api/v2/stook/{organization_uuid}/bucket/{bucket_uuid}/settings ``` Send: ```json { "object_lock_enabled": true, "object_lock_days": 90 } ``` The request enables Object Lock and configures a 90-day retention period for new objects. Object Lock cannot be disabled after it has been enabled. ## Troubleshooting ### Object Lock requires Versioning Set **Versioning** to **On** and save the configuration before enabling Object Lock. ### A retention period is required Enter a **Retention period** between 1 and 365 days. ### The retention period exceeds the supported maximum The standard supported retention period is up to 365 days. Enter a value of 365 days or less. For a longer retention period, contact . ### Object Lock cannot be disabled Object Lock cannot be switched off after it has been enabled for the Stook Bucket. Objects already stored with retention protection keep their assigned retention periods until they expire. ### Versioning cannot be suspended Versioning must remain **On** while Object Lock is enabled. ### Deleting an object version returns AccessDenied The object version may still be within its retention period. Wait until the retention period expires before deleting the version. ## Related Topics * [Bucket Configuration](/products/object-storage-stook/bucket-configuration.md) * [Versioning](/products/object-storage-stook/bucket-configuration/versioning.md) * [MFA Delete](/products/object-storage-stook/bucket-configuration/mfa-delete.md) * [Manage Access Keys](/products/object-storage-stook/manage-access-keys.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://clients.medianova.com/products/object-storage-stook/bucket-configuration/object-lock.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.