Deletes the S3 bucket. All objects (including all object versions and delete markers) in the bucket must be deleted before the bucket itself can be deleted.
Directory buckets - If multipart uploads in a directory bucket are in progress, you can't delete the bucket until all the in-progress multipart uploads are aborted or completed.
Directory buckets - For directory buckets, you must make requests for this API operation to the Regional endpoint. These endpoints support path-style requests in the formathttps://s3express-control.region-code.amazonaws.com/bucket-name. Virtual-hosted-style requests aren't supported. For more information about endpoints in Availability Zones, seeRegional and Zonal endpoints for directory buckets in Availability Zones in theAmazon S3 User Guide. For more information about endpoints in Local Zones, seeConcepts for directory buckets in Local Zones in theAmazon S3 User Guide.
General purpose bucket permissions - You must have thes3:DeleteBucket permission on the specified bucket in a policy.
Directory bucket permissions - You must have thes3express:DeleteBucket permission in an IAM identity-based policy instead of a bucket policy. Cross-account access to this API operation isn't supported. This operation can only be performed by the AWS account that owns the resource. For more information about directory bucket policies and permissions, seeAWS Identity and Access Management (IAM) for S3 Express One Zone in theAmazon S3 User Guide.
Directory buckets - The HTTP Host header syntax iss3express-control.region-code.amazonaws.com.
The following operations are related toDeleteBucket:
You must URL encode any signed header values that contain spaces. For example, if your header value ismy file.txt, containing two spaces aftermy, you must URL encode this value tomy%20%20file.txt.
DELETE / HTTP/1.1Host:Bucket.s3.amazonaws.comx-amz-expected-bucket-owner:ExpectedBucketOwnerThe request uses the following URI parameters.
Specifies the bucket being deleted.
Directory buckets - When you use this operation with a directory bucket, you must use path-style requests in the formathttps://s3express-control.region-code.amazonaws.com/bucket-name. Virtual-hosted-style requests aren't supported. Directory bucket names must be unique in the chosen Zone (Availability Zone or Local Zone). Bucket names must also follow the formatbucket-base-name--zone-id--x-s3 (for example,DOC-EXAMPLE-BUCKET--usw2-az1--x-s3). For information about bucket naming restrictions, seeDirectory bucket naming rules in theAmazon S3 User Guide
Required: Yes
The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code403 Forbidden (access denied).
For directory buckets, this header is not supported in this API operation. If you specify this header, the request fails with the HTTP status code501 Not Implemented.
The request does not have a request body.
HTTP/1.1 204If the action is successful, the service sends back an HTTP 204 response with an empty HTTP body.
This request deletes the bucket namedamzn-s3-demo-bucket.
DELETE / HTTP/1.1Host: amzn-s3-demo-bucket.s3.<Region>.amazonaws.comDate: Wed, 01 Mar 2006 12:00:00 GMTAuthorization: authorization stringHTTP/1.1 204 No Contentx-amz-id-2: JuKZqmXuiwFeDQxhD7M8KtsKobSzWA1QEjLbTMTagkKdBX2z7Il/jGhDeJ3j6s80x-amz-request-id: 32FE2CEB32F5EE25Date: Wed, 01 Mar 2006 12:00:00 GMTConnection: closeServer: AmazonS3For more information about using this API in one of the language-specific AWS SDKs, see the following: