> For the complete documentation index, see [llms.txt](https://docs.impossiblecloud.com/impossible-cloud-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.impossiblecloud.com/impossible-cloud-help/impossible-cloud-storage-guide/buckets-and-objects/emptying-a-bucket.md).

# Emptying a Bucket

The 'Empty Bucket' feature provides a straightforward way for root users to delete all objects within a selected bucket via the Impossible Cloud interface. This tool is especially valuable when you need to ensure a bucket is completely cleared of its contents, which can be challenging to accomplish manually if dealing with large quantities of data, various object versions, or protected items. It simplifies what would otherwise require scripting expertise and command-line operations.

{% hint style="warning" %}
Note that this feature will only delete the contents of the bucket. The bucket itself will remain intact. If you wish to delete the bucket entirely, this must be done as a separate action after emptying the contents.
{% endhint %}

### Prerequisites

* You must have root access to the Impossible Cloud account.
* Ensure the bucket you choose is the one you intend to empty.

### **Step-by-Step Guide**

1. **Access Bucket Settings**
   * Navigate to the 'Buckets' tab on your Impossible Cloud dashboard.
   * Click the cogwheel icon beside the bucket you wish to empty to open its settings.
2. **Schedule the Emptying Process**
   * Find and activate the 'Emptying the bucket' setting, noted as not scheduled by default.
3. **Confirm the Deletion Process**
   * Read the pop-up details regarding the permanence of the action and exceptions for Object Lock.
   * Type "permanently delete" to confirm and activate the 'Permanently Delete' button.
4. **Finalize the Schedule**
   * Click on the ‘Permanently Delete’ button to confirm the deletion. This action will initiate the bucket emptying process, which will begin in 24 hours from the time of confirmation. This 24-hour delay is fixed and cannot be altered by the user.
   * The settings page will then display the scheduled time for the process.
5. **Monitor Status or Cancel**
   * On the bucket's page, a notification will inform you of the scheduled emptying.
   * As a root user, you can cancel the process before it commences if necessary.
6. **Check Completion**
   * After the scheduled time, the bucket's page will indicate the completion of the emptying process.
   * Verify that the bucket is empty before using it again.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.impossiblecloud.com/impossible-cloud-help/impossible-cloud-storage-guide/buckets-and-objects/emptying-a-bucket.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.