Bucket Management: Renaming and Deleting
    • 12 Feb 2025
    • 3 Minutes to read
    • PDF

    Bucket Management: Renaming and Deleting

    • PDF

    Article summary

    Renaming a Bucket

    You cannot rename a bucket if it or any object in it has object lock or compliance enabled.
    1. Clickactions-ellipsisto access options for the bucket you want to rename.
    2. Click Rename. In this example, we will rename widget-schematics.

    3. Enter a new bucket name.

    4. Click Rename Bucket.

      The bucket name is changed and displayed in the Bucket list. For examole:

    If you attempt to rename an object that has object lock enabled or if any object in the bucket has object lock enabled, this alert is displayed:

    Deleting a Bucket

    A bucket should be empty before you can delete it.

    When you delete a bucket, all objects stored with the Wasabi service are subject to Wasabi’s minimum storage policy, which applies even if the bucket is deleted. For additional information, refer to: wasabi.com/pricing.
    Bucket log files that are mapped from other buckets will be deleted if configured already.
    You cannot delete non-empty compliance buckets.
    You cannot delete a bucket if it contains any object that has object lock enabled.

    This section describes:

    Deleting a Standard-Sized Bucket

    1. Clickactions-ellipsisto access options for the bucket you want to delete.
    2. Click Delete. In this example, we will delete widget-with-object-lock.

    3. A message asks you to confirm that you want to delete the bucket. Do so cautiously because deleting a bucket removes all objects stored in the bucket.

      Type the name of the bucket to proceed.

    4. Click Delete if you are sure you want to delete the bucket (otherwise, click Cancel).
    5. If there are still files in the bucket, a message requests that you click Delete if you want to delete all of the files.

    If the multi-user authentication feature has been set for your account, a bucket deletion triggers a notification to a security contact who will need to approve the deletion. In this case, the Delete option for the bucket changes to Awaiting Deletion Approval. Once approved, the bucket will be deleted.

    If you attempt to delete a bucket that contains any object that has object enabled, this alert is displayed:

    Deleting a Large Bucket

    If a bucket is large (with numerous objects), the delete request may time out in the browser before the operation completes. One solution is to use a third-party application, such as Postman, to send the delete request. Another option is to create a Lifecycle rule to remove objects and reduce the bucket to a more manageable size. Then, the bucket can be deleted in the Console. The following describes the second option.

    1. Clickactions-ellipsisto access options for the bucket you want to delete.
    2. Click Settings.
    3. Click the Lifecycle tab.
    4. Click Create New Rule.

    5. Enter a name for the Lifecycle rule.
    6. Choose to apply the rule to all objects in the bucket.
    7. Select Expire current version of objects and enter 1 for the number of days after object creation.
    8. Select Permanently delete noncurrent versions of objects and enter 1 for the number of days after an object becomes noncurrent.

    9. Scroll down and click Create to save the Lifecycle rule configuration.
    It may take a few days for the Lifecycle rule to be added to the queue and start processing the bucket.

    After the rule has had time to process objects in the bucket, you will see the bucket utilization drop. This will enable you to delete the bucket from the Console. 

    Deleting an Object Locked Bucket 

    You cannot delete a bucket that has objects under retention. While you wait for the retention period to expire, you can set up a Lifecycle rule to start cleaning out the bucket by removing the objects that are no longer under retention. To set up a Lifecycle rule, refer to the procedure in Deleting a Large Bucket above.

    If you are using a backup application, make sure all references to the bucket are removed from the application so that the retention period is not continually reset while the application communicates with the bucket. 

    If you are unsure of how long objects are under retention in the bucket, Wasabi Support created a Python script that can run through the bucket and determine the longest retention period of all objects.