Use per-bucket versioning to retain previous object versions when applications overwrite a key. Versioning is separate from an independent backup and from the service’s termination-retention window.

Change the intended bucket

1. Open the active service’s Storage settings page.
2. Select the exact bucket.
3. Review the current versioning state.
4. Use Enable or Suspend as intended.
5. Read back the resulting state before changing application behaviour.

The host must enable Client: Storage settings. A suspended or terminated service can refuse settings changes.

Understand retained versions

Existing versions continue occupying storage. Suspending versioning does not erase them, and enabling it now cannot recover versions that were never retained.

A normal delete in a versioned bucket can create a delete marker rather than permanently removing previous data. Use an authorised version-aware storage workflow to inspect or retrieve a particular version; the module’s toggle is not an object-version recovery browser. AWS describes this distinction in its version-deletion guide.

Check usage and lifecycle together

Old versions count towards measured usage. Removing the current visible file may therefore leave storage above its quota. Review the usage guide and the bucket’s cleanup policy before expecting capacity to fall.

Keep any intended recovery copy before permanently deleting versions. Neither a module update nor changing a billing status can recreate data already purged.

See the PD AWS S3 Blesta guide for related tasks, or explore the module.