Organiza tus páginas con colecciones
Guarda y categoriza el contenido según tus preferencias.
En esta página, se explica cómo borrar buckets de almacenamiento en entornos aislados de Google Distributed Cloud (GDC). En este documento, se describen los requisitos previos y los métodos para borrar buckets a través de la consola de GDC y la interfaz de línea de comandos (CLI). Obtén más información para borrar buckets con políticas de retención mediante la destrucción criptográfica, un proceso en el que se borra la clave de encriptación asociada al bucket de almacenamiento. Esta información te permite administrar de forma segura y permanente el ciclo de vida de tu almacenamiento de objetos, lo que proporciona higiene y cumplimiento de los datos.
Esta página está destinada a públicos como los administradores de TI dentro del grupo de operadores de infraestructura o los desarrolladores dentro del grupo de operadores de aplicaciones que son responsables de administrar los recursos de almacenamiento de objetos en entornos aislados de GDC. Para obtener más información, consulta Audiences for GDC air-gapped documentation (Públicos para la documentación de GDC aislada del aire).
Antes de comenzar
Un espacio de nombres del proyecto administra los recursos del bucket en el servidor de la API de Management. Debes tener un proyecto para trabajar con buckets y objetos.
También debes tener los permisos de bucket adecuados para realizar la siguiente operación. Consulta Cómo otorgar acceso al bucket.
Borrar buckets de almacenamiento
Console
En el menú de navegación, haz clic en Object Storage.
Haz clic en borrarBorrar al final de la fila del bucket que se borrará.
Espera unos minutos y actualiza la página para verificar que se haya borrado el bucket.
CLI
Puedes borrar buckets de almacenamiento con la CLI. Los buckets deben estar vacíos antes de que puedas borrarlos.
Usa el comando GET o DESCRIBE de la sección Ver configuración del bucket para obtener el nombre completamente calificado del bucket.
Si el bucket no está vacío, borra los archivos que contiene:
Puedes ejecutar el siguiente comando para verificar que el bucket se haya destruido criptográficamente de forma correcta. El BucketReady debe ser False y el Reason debe ser BucketCryptoShredded.
[[["Fácil de comprender","easyToUnderstand","thumb-up"],["Resolvió mi problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Información o código de muestra incorrectos","incorrectInformationOrSampleCode","thumb-down"],["Faltan la información o los ejemplos que necesito","missingTheInformationSamplesINeed","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-09-04 (UTC)"],[[["\u003cp\u003eThis page details how to delete Google Distributed Cloud (GDC) air-gapped storage buckets, requiring a project namespace and appropriate bucket permissions.\u003c/p\u003e\n"],["\u003cp\u003eBuckets with retention policies cannot be deleted until the locked date expires, but they can be crypto shredded beforehand.\u003c/p\u003e\n"],["\u003cp\u003eDeleting buckets via the CLI requires them to be empty; files must be removed first using the \u003ccode\u003egdcloud storage rm --recursive\u003c/code\u003e command.\u003c/p\u003e\n"],["\u003cp\u003eCrypto shredding a bucket involves deleting its AEADKey, making the data permanently unrecoverable, and this is only available for buckets using \u003ccode\u003ev1\u003c/code\u003e encryption.\u003c/p\u003e\n"],["\u003cp\u003eOnce a bucket is crypto shredded the \u003ccode\u003eBucketReady\u003c/code\u003e status will be \u003ccode\u003eFalse\u003c/code\u003e and \u003ccode\u003eReason\u003c/code\u003e to be \u003ccode\u003eBucketCryptoShredded\u003c/code\u003e.\u003c/p\u003e\n"]]],[],null,["# Delete storage buckets\n\nThis page guides you through how to delete storage buckets within Google Distributed Cloud (GDC) air-gapped environments. It covers prerequisites and methods for deleting buckets through the GDC console and command line interface (CLI). Learn how to delete buckets with retention policies by crypto shredding---a process where you delete the encryption key associated with the storage bucket. This information lets you securely and permanently manage the lifecycle of your object storage, providing data hygiene and compliance\n\nThis page is for audiences such as IT admins within the infrastructure operator group or developers within the application operator group who are responsible for managing object storage resources in GDC air-gapped environments. For more information, see [Audiences for GDC air-gapped documentation](/distributed-cloud/hosted/docs/latest/gdch/resources/audiences).\n\nBefore you begin\n----------------\n\nA project namespace manages bucket resources in the Management API server. You\nmust have a [project](/distributed-cloud/hosted/docs/latest/gdch/platform/pa-user/project-management) to work with buckets and objects.\n\nYou must also have the appropriate bucket permissions to perform the following\noperation. See [Grant bucket access](/distributed-cloud/hosted/docs/latest/gdch/platform/pa-user/grant-obtain-storage-access#grant_bucket_access).\n\nDelete storage buckets\n----------------------\n\n**Warning:** Buckets with retention policy would be blocked for deletion until the locked date expire. Therefore, you can crypto shred the bucket before it can be deleted following [Crypto shred bucket](/distributed-cloud/hosted/docs/latest/gdch/platform/pa-user/delete-storage-buckets#crypto_shred_bucket). \n\n### Console\n\n1. In the navigation menu, click **Object Storage**.\n2. Click delete **Delete** at the end of the row of the bucket to be deleted.\n3. Wait a few minutes and refresh the page to check that the bucket is deleted.\n\n### CLI\n\nYou can delete storage buckets by using the CLI. **Buckets must be empty before\nyou can delete them.**\n\n1. Use the `GET` or `DESCRIBE` command from the [View bucket configuration](/distributed-cloud/hosted/docs/latest/gdch/platform/pa-user/list-view-storage-buckets#view_bucket_configurations) section to get the fully qualified bucket name.\n\n2. If the bucket is not empty, delete files within the bucket:\n\n gdcloud storage rm --recursive -a s3://\u003cvar translate=\"no\"\u003eBUCKET\u003c/var\u003e/**\n\n3. Delete the empty bucket:\n\n kubectl delete buckets/\u003cvar translate=\"no\"\u003eBUCKET_NAME\u003c/var\u003e --namespace \u003cvar translate=\"no\"\u003eNAMESPACE_NAME\u003c/var\u003e\n\nCrypto shred bucket\n-------------------\n\n| **Note:** Only `v1` encryption bucket can be crypto shred, for `v2` encryption bucket, use [Crypto shred objects in buckets with encryption v2](/distributed-cloud/hosted/docs/latest/gdch/platform/pa-user/delete-storage-objects#crypto_shred_objects_in_buckets_with_encryption_v2)\n| **Warning:** This step is not recoverable and you will lose all data encrypted in the bucket.\n\nRetrieve the information about the AEADKey based on [Verify bucket resource creation](/distributed-cloud/hosted/docs/latest/gdch/platform/pa-user/create-storage-buckets#verify_bucket_and_related_resource_creation) and follow [Delete a key](/distributed-cloud/hosted/docs/latest/gdch/application/ao-user/kms/create-delete-keys#delete) to delete the AEADKey, then the entire bucket would be crypto shredded.\n\nYou can run the following command to verify the bucket has been successfully crypto shredded. The `BucketReady` should be `False` and `Reason` to be `BucketCryptoShredded`. \n\n kubectl get Buckets \u003cvar translate=\"no\"\u003eBUCKET_NAME\u003c/var\u003e -n \u003cvar translate=\"no\"\u003eNAMESPACE_NAME\u003c/var\u003e"]]
