이 페이지에서는 Google Distributed Cloud (GDC) 에어 갭 환경 내에서 스토리지 버킷을 삭제하는 방법을 안내합니다. GDC 콘솔 및 명령줄 인터페이스 (CLI)를 통해 버킷을 삭제하기 위한 기본 요건과 방법을 설명합니다. 보관 정책이 있는 버킷을 암호 파쇄를 통해 삭제하는 방법을 알아보세요. 암호 파쇄는 스토리지 버킷과 연결된 암호화 키를 삭제하는 프로세스입니다. 이 정보를 사용하면 객체 스토리지의 수명 주기를 안전하게 영구적으로 관리하여 데이터 위생 및 규정 준수를 보장할 수 있습니다.
이 페이지는 GDC 오프라인 환경에서 객체 스토리지 리소스를 관리하는 인프라 운영자 그룹의 IT 관리자 또는 애플리케이션 운영자 그룹의 개발자와 같은 사용자를 대상으로 합니다. 자세한 내용은 GDC 오프라인 문서 대상을 참고하세요.
시작하기 전에
프로젝트 네임스페이스는 관리 API 서버에서 버킷 리소스를 관리합니다. 버킷 및 객체로 작업하려면 프로젝트가 있어야 합니다.
다음 작업을 수행하려면 적절한 버킷 권한도 있어야 합니다. 버킷 액세스 권한 부여를 참고하세요.
스토리지 버킷 삭제
콘솔
탐색 메뉴에서 객체 스토리지를 클릭합니다.
삭제할 버킷의 행 끝에 있는 삭제Delete를 클릭합니다.
몇 분 정도 기다린 후 페이지를 새로고침하여 버킷이 삭제되었는지 확인합니다.
CLI
CLI를 사용하여 스토리지 버킷을 삭제할 수 있습니다. 버킷을 삭제하려면 버킷이 비어 있어야 합니다.
버킷 구성 보기 섹션의 GET 또는 DESCRIBE 명령어를 사용하여 정규화된 버킷 이름을 가져옵니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 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"]]
