Bucket Deletion

evroc takes the preservation of your data seriously. To ensure this we have extra safeguards in place in order to make sure your data is not accidentally lost. This means that you need to take some additional precautionary actions before deleting a Bucket that you are no longer interested in. This page documents the steps needed to permanently delete a Bucket along with all its data.

Empty Bucket

A Bucket must be empty before it can be deleted. A Bucket is considered empty when all of its Objects are deleted. For a Bucket with Object Versioning enabled this includes all previous Object Versions and Deletion Markers.

If a non-empty Bucket is marked for deletion it will go into a "Pending Deletion" state. Getting into this state is irreversible, and the Bucket will stay in this state until all its Objects (and Object Versions, if applicable) are deleted. In this state the Bucket resource itself can no longer be updated, however the contained Objects can still be accessed and modified.

Object Locking

A Bucket with Object Locking enabled cannot be deleted if it contains any locked Objects.

Purging

The evroc CLI supports the flag --purge which will first empty the Bucket of all Objects before marking it for deletion. This can be convenient for cleaning up Buckets after e.g. tests. For more information about this flag refer to the How To documentation.

NOTE: using --purge requires access to the Data APIs and therefore requires the called to be a Bucket Owner. For more information about Bucket Owners, see Access Control.