[Yandex Cloud documentation](../../../index.md) > [Yandex Object Storage](../../index.md) > [Step-by-step guides](../index.md) > Objects > Deleting all objects # Deleting all objects from a bucket {% note warning %} By default, the delete operation is irreversible. You can only [restore](restore-object-version.md) the objects that were uploaded with [versioning](../../concepts/versioning.md) on. {% endnote %} {% note info %} To automatically delete partially loaded objects in Object Storage, configure a [lifecycle](../buckets/lifecycles.md) rule. {% endnote %} To clear a bucket and avoid storage[charges](../../pricing.md): {% list tabs group=instructions %} - Yandex Cloud CLI {#cli} If you do not have the Yandex Cloud CLI yet, [install and initialize it](../../../cli/quickstart.md#install). The folder used by default is the one specified when [creating](../../../cli/operations/profile/profile-create.md) the CLI profile. To change the default folder, use the `yc config set folder-id ` command. You can also specify a different folder for any command using `--folder-name` or `--folder-id`. If you access a resource by its name, the search will be limited to the default folder. If you access a resource by its ID, the search will be global, i.e., through all folders based on access permissions. 1. See the description of the CLI command for deleting objects: ```bash yc storage s3api delete-objects --help ``` 1. Get a list of buckets in the default folder: ```bash yc storage bucket list ``` Result: ```text +------------------+----------------------+-------------+-----------------------+---------------------+ | NAME | FOLDER ID | MAX SIZE | DEFAULT STORAGE CLASS | CREATED AT | +------------------+----------------------+-------------+-----------------------+---------------------+ | first-bucket | b1gmit33ngp6******** | 53687091200 | STANDARD | 2022-12-16 13:58:18 | +------------------+----------------------+-------------+-----------------------+---------------------+ ``` 1. Prepare a JSON file listing the objects to delete. Here is an example of its contents: ```json { "Objects": [ { "Key": "" }, { "Key": "" }, ... ] } ``` Where: * `Objects`: Array of objects to delete. * `Key`: Object [key](../../concepts/object.md#key). 1. Run this command: ```bash yc storage s3api delete-objects \ --bucket \ --delete ``` Where: * `--bucket`: Name of your bucket. * `--delete`: Path to the JSON file listing the objects to delete. Result: ```bash deleted: - key: file-1 version_id: "null" - key: file-2 version_id: "null" request_id: 4c35e7d4******** ``` Alternative command: ```bash yc storage s3 rm \ s3:/// \ --recursive ``` Where `--recursive` is the parameter to delete all objects. Result: ```text delete: s3://my-bucket/object-1.txt delete: s3://my-bucket/object-2.txt ... delete: s3://my-bucket/object-n.txt ``` - AWS CLI {#aws-cli} If you do not have the AWS CLI yet, [install and configure it](../../tools/aws-cli.md). {% note info %} The commands in this section follow the [Bash](https://en.wikipedia.org/wiki/Bash_(Unix_shell)) syntax. If using Windows, [read](../../../overview/concepts/console-syntax-guide.md) about using Bash in Microsoft Windows and use [Windows Subsystem for Linux (WSL)](https://docs.microsoft.com/en-us/windows/wsl/install), [Git Bash](https://git-scm.com/install/windows), or another bash-compatible terminal. {% endnote %} 1. Create a variable containing the bucket name: ```bash BUCKET_NAME= ``` 1. Delete all object versions from the bucket: ```bash aws s3api delete-objects \ --endpoint-url https://storage.yandexcloud.net \ --bucket $BUCKET_NAME \ --delete \ "$(aws s3api list-object-versions \ --endpoint-url https://storage.yandexcloud.net \ --bucket $BUCKET_NAME \ --query '{Objects: Versions[].{Key: Key, VersionId: VersionId}}' \ --max-items 1000)" ``` The `--max-items` argument specifies the number of object versions the command provides in a single request. The value cannot exceed `1000`, because `delete-objects` accepts a maximum of 1,000 keys at a time. If `--max-items` causes an error, you can use `--max-keys`. Both produce the same result, but `--max-items` operates on the client side, whereas `--max-keys`, on the server side. If you need to delete more than 1,000 object versions, repeat the command several times. Result: ```json { "Deleted": [ { "Key": "object_000", "VersionId": "0005CDD3********" }, { "Key": "object_001", "VersionId": "0005CDD3********" }, ... ] } ``` 1. For buckets with enabled [versioning](../../concepts/versioning.md), remove all delete markers: ```bash aws s3api delete-objects \ --endpoint-url https://storage.yandexcloud.net \ --bucket $BUCKET_NAME \ --delete \ "$(aws s3api list-object-versions \ --endpoint-url https://storage.yandexcloud.net \ --bucket $BUCKET_NAME \ --query '{Objects: DeleteMarkers[].{Key: Key, VersionId: VersionId}}' \ --max-items 1000)" ``` The `--max-items` parameter specifies the number of delete markers the command provides in a single request. The value cannot exceed `1000`, because `delete-objects` accepts a maximum of 1,000 keys at a time. If `--max-items` causes an error, you can use `--max-keys`. Both produce the same result, but `--max-items` operates on the client side, whereas `--max-keys`, on the server side. If you need to delete more than 1,000 delete markers, repeat the command several times. Result: ```json { "Deleted": [ { "Key": "object_034", "DeleteMarker": true, "DeleteMarkerVersionId": "0005CDD3********" }, { "Key": "object_057", "DeleteMarker": true, "DeleteMarkerVersionId": "0005CDD3********" }, ... ] } ``` 1. Delete partially uploaded objects: ```bash aws s3api list-multipart-uploads \ --endpoint-url https://storage.yandexcloud.net \ --bucket $BUCKET_NAME \ | jq -r '.Uploads[] | "--key \"\(.Key)\" --upload-id \(.UploadId)"' \ | while read -r line; do eval "aws s3api abort-multipart-upload \ --endpoint-url https://storage.yandexcloud.net \ --bucket $BUCKET_NAME \ $line"; done ``` 1. Get a list of object parts remaining in the bucket: ```bash aws s3api list-multipart-uploads \ --endpoint-url https://storage.yandexcloud.net \ --bucket $BUCKET_NAME \ | jq -r '.Uploads[] | "--key \"\(.Key)\" --upload-id \(.UploadId)"' \ | while read -r line; do eval "aws s3api list-parts \ --endpoint-url https://storage.yandexcloud.net \ --bucket $BUCKET_NAME \ $line"; done ``` The list may include parts of objects whose upload started before and completed after the preceding step. If the list is not empty, repeat steps 4 and 5. - Python (boto3) {#boto3} Run the following code: ```python import boto3 bucket_name = '' s3 = boto3.resource('s3', endpoint_url='https://storage.yandexcloud.net', aws_access_key_id='', aws_secret_access_key='') bucket = s3.Bucket(bucket_name) # Deleting all versions (works for non-versioned buckets too). bucket.object_versions.delete() # Aborting all multipart uploads, which also deletes all parts. for multipart_upload in bucket.multipart_uploads.iterator(): # Part uploads that are currently in progress may or may not succeed, # so it might be necessary to abort a multipart upload multiple times. while len(list(multipart_upload.parts.all())) > 0: multipart_upload.abort() ``` - API {#api} Use the [deleteMultipleObjects](../../s3/api-ref/object/deletemultipleobjects.md) S3 API method. {% endlist %} In the management console, the information about the number of objects and storage space used in the bucket is updated with a few minutes' delay.