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.
Important
To ensure that bucket owners don't inadvertently lock themselves out of their own buckets, the root principal in a bucket owner's Petabox account can perform the GetBucketPolicy, PutBucketPolicy, and DeleteBucketPolicy API actions, even if their bucket policy explicitly denies the root principal's access. Bucket owner root principals can only be blocked from performing these API actions by VPC endpoint policies and Petabox Organizations policies.
Request Syntax
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
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.
Sample Response
This example illustrates one usage of DeleteBucketPolicy.
Last updated