DeleteBucketEncryption
This implementation of the DELETE action resets the default encryption for the bucket as server-side encryption with Amazon S3 managed keys (SSE-S3).
General purpose buckets - For information about the bucket default encryption feature, seeAmazon S3 Bucket Default Encryption in theAmazon S3 User Guide.
Directory buckets - For directory buckets, there are only two supported options for server-side encryption: SSE-S3 and SSE-KMS. For information about the default encryption configuration in directory buckets, seeSetting default server-side encryption behavior for directory buckets.
- Permissions
General purpose bucket permissions - The
s3:PutEncryptionConfigurationpermission is required in a policy. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, seePermissions Related to Bucket Operations andManaging Access Permissions to Your Amazon S3 Resources.Directory bucket permissions - To grant access to this API operation, you must have the
s3express:PutEncryptionConfigurationpermission 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.
- HTTP Host header syntax
Directory buckets - The HTTP Host header syntax is
s3express-control.region-code.amazonaws.com.
The following operations are related toDeleteBucketEncryption:
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.
Request Syntax
DELETE /?encryption HTTP/1.1Host:Bucket.s3.amazonaws.comx-amz-expected-bucket-owner:ExpectedBucketOwnerURI Request Parameters
The request uses the following URI parameters.
- Bucket
The name of the bucket containing the server-side encryption configuration to delete.
Directory buckets - When you use this operation with a directory bucket, you must use path-style requests in the format
https://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 GuideRequired: Yes
- x-amz-expected-bucket-owner
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 code
403 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 code
501 Not Implemented.
Request Body
The request does not have a request body.
Response Syntax
HTTP/1.1 204Response Elements
If the action is successful, the service sends back an HTTP 204 response with an empty HTTP body.
Examples
Sample Request for a general purpose bucket
The followingDELETE request resets the default encryption for the bucket as server-side encryption with Amazon S3 managed keys (SSE-S3).
DELETE ?/encryption HTTP/1.1Host: amzn-s3-demo-bucket.s3.<Region>.amazonaws.com Date: Wed, 06 Sep 2017 12:00:00 GMTAuthorization: signatureValueSample Response for a general purpose bucket
The following successful response shows Amazon S3 returning a204 No Content response confirming that default encryption for the bucket has been reset as server-side encryption with Amazon S3 managed keys (SSE-S3).
HTTP/1.1 204 No Contentx-amz-id-2: 0FmFIWsh/PpBuzZ0JFRC55ZGVmQW4SHJ7xVDqKwhEdJmf3q63RtrvH8ZuxW1Bol5x-amz-request-id: 0CF038E9BCF63097Date: Wed, 06 Sep 2017 12:00:00 GMTServer: AmazonS3See Also
For more information about using this API in one of the language-specific AWS SDKs, see the following:
