# Ensure Versioning Is Enabled on Critical Buckets

- Source: https://support.icompaas.com/support/solutions/articles/a_1791826029219272-ensure-versioning-is-enabled-on-critical-buckets
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [OVH Cloud](https://support.icompaas.com/support/solutions/c_1791819364512367) › [checks](https://support.icompaas.com/support/solutions/folders/f_1791819376721251)
- Last updated: 2026-10-12
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

**Description**

Ensure object versioning is enabled on Object Storage buckets that hold critical data, so every change or deletion keeps the previous version of the object, which can be restored if needed.

**Rationale**

Without versioning, overwriting or deleting an object removes the old data permanently. Mistakes, faulty applications, or ransomware can then destroy data with no way to recover it. Versioning keeps earlier versions, and it is also required for Object Lock.

**Impact**

-   Overwritten or deleted objects can be restored
    
-   Protects against accidental changes and ransomware
    
-   Increases storage use, so lifecycle rules for old versions are recommended
    

**Default Value**

By default, versioning is disabled on buckets.

**Pre-Requisites**

-   Permission to manage Object Storage in the Public Cloud project
    

**Test Plan**

1.  Log in to the OVHcloud Control Panel at [https://www.ovh.com/manager/](https://www.ovh.com/manager/).
    
2.  In the left-hand menu, select Public Cloud and choose your project.
    
3.  In the left-hand menu, select Object Storage.
    
4.  Select the bucket and, in the General information tab, check the versioning status.
    
5.  Alternatively, run: aws s3api get-bucket-versioning --bucket <bucket\_name>
    
6.  If versioning is not enabled on a critical bucket, follow the implementation steps.
    

**Implementation Steps**

1.  Log in to the OVHcloud Control Panel at [https://www.ovh.com/manager/](https://www.ovh.com/manager/).
    
2.  In the left-hand menu, select Public Cloud and choose your project.
    
3.  In the left-hand menu, select Object Storage.
    
4.  Select the bucket and, in the General information tab, enable versioning.
    
5.  Alternatively, run: aws s3api put-bucket-versioning --bucket <bucket\_name> --versioning-configuration Status=Enabled
    

**Backout Plan**

1.  Run: aws s3api put-bucket-versioning --bucket <bucket\_name> --versioning-configuration Status=Suspended. Existing versions are kept.
    

**Reference**

-   [https://support.us.ovhcloud.com/hc/en-us/articles/31431459806355-Object-Storage-Getting-started-with-versioning](https://support.us.ovhcloud.com/hc/en-us/articles/31431459806355-Object-Storage-Getting-started-with-versioning)

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.