Empty a bucket

Emptying a bucket deletes every object in it, including all older versions, and keeps the bucket.

Before you begin

Copies of any objects you need. Emptying is permanent.
A bucket in the Ready state.
Permission to update and to delete datasets in the project. The Actions menu shows Empty with update permission, and emptying the bucket needs delete permission. A Member gets both through a policy that allows them.
The bucket unmounted from everything that uses it. The portal refuses to empty a bucket while it is mounted on an instance or Virtual Machine. It also refuses while a fine-tuning job that has not succeeded, a model endpoint, a deployment, or a Slurm Cluster uses the bucket. This holds whether the workload is running or stopped.
On a bucket with object lock, its locks cleared first. A version still under retention or legal hold stops the run and leaves the remaining objects in place. See Lock one object version or place a legal hold.

Empty the bucket

In the list, open the Actions menu of the bucket and select Empty.
Note what emptying does: it permanently deletes every object, including all older versions. Only the objects go, so the bucket stays. Depending on how many objects it holds, this can take a while. To remove the bucket as well, use Delete instead.
Type the bucket’s alias to confirm. Empty Bucket becomes available once it matches. Until it matches, the dialog says “Type the exact bucket name”.
Select Empty Bucket.

The portal shows “Emptying <alias> has been requested.” Emptying runs in the background.

Check the result

Open the Data Objects tab and refresh the list. The list is empty once emptying finishes. If a locked version stopped the run, clear those locks and empty again.

The bucket itself stays. To remove it too, delete the bucket. For help with a message, see Troubleshooting TIR Object Storage.