DeleteBucketPolicy

This implementation of the DELETE action uses the policy subresource to delete the policy of a specified bucket

If you are using an identity other than the root user of the Petabox account that owns the bucket, the calling identity must have the DeleteBucketPolicy permissions on the specified bucket and belong to the bucket owner's account to use this operation.

If you don't have DeleteBucketPolicy permissions, Petabox returns a 403 Access Denied error. If you have the correct permissions, but you're not using an identity that belongs to the bucket owner's account, Petabox returns a 405 Method Not Allowed error.

Request Syntax

DELETE /?policy HTTP/1.1
Host: Bucket.s3.petabox.io
x-amz-expected-bucket-owner: ExpectedBucketOwner

URI Request Parameters

The request uses the following URI parameters.

Bucket

The bucket name.

Required: Yes

x-amz-expected-bucket-owner

The account ID of the expected bucket owner. If the bucket is owned by a different account, the request fails with the HTTP status code 403 Forbidden (access denied).

Request Body

The request does not have a request body.

Response Syntax

HTTP/1.1 204

Response Elements

If the action is successful, the service sends back an HTTP 204 response with an empty HTTP body.

Examples

Sample Request

This request deletes the bucket named BucketName.

DELETE /?policy HTTP/1.1
Host: BucketName.s3.<Region>.petabox.io  
Date: Tue, 04 Apr 2010 20:34:56 GMT  
Authorization: signatureValue       

Sample Response

This example illustrates one usage of DeleteBucketPolicy.

HTTP/1.1 204 No Content 
x-amz-id-2: Uuag1LuByRx9e6j5OnimrSAMPLEtRPfTaOFg==  
x-amz-request-id: 656c76696e672SAMPLE5657374  
Date: Tue, 04 Apr 2010 20:34:56 GMT  
Connection: keep-alive  
Server: Petabox   

Last updated