AWS services or capabilities described in AWS Documentation may vary by region/location. Click Getting Started with Amazon AWS to see specific differences applicable to the China (Beijing) Region.
            Deletes the policy of a specified bucket.
            
              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 format https://s3express-control.region-code.amazonaws.com/bucket-name. Virtual-hosted-style requests aren't supported. For more information about endpoints
            in Availability Zones, see Regional
            and Zonal endpoints for directory buckets in Availability Zones in the Amazon
            S3 User Guide. For more information about endpoints in Local Zones, see Concepts
            for directory buckets in Local Zones in the Amazon S3 User Guide.
            
            If you are using an identity other than the root user of the Amazon Web Services account
            that owns the bucket, the calling identity must both have the DeleteBucketPolicy
            permissions on the specified bucket and belong to the bucket owner's account in order
            to use this operation.
            
            If you don't have DeleteBucketPolicy permissions, Amazon S3 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, Amazon S3 returns a 405
            Method Not Allowed error.
            
            To ensure that bucket owners don't inadvertently lock themselves out of their own
            buckets, the root principal in a bucket owner's Amazon Web Services 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 Amazon Web Services Organizations policies.
            
General purpose bucket permissions - The s3:DeleteBucketPolicy permission
            is required in a policy. For more information about general purpose buckets bucket
            policies, see Using
            Bucket Policies and User Policies in the Amazon S3 User Guide.
            
Directory bucket permissions - To grant access to this API operation, you
            must have the s3express:DeleteBucketPolicy 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 Amazon Web Services account
            that owns the resource. For more information about directory bucket policies and permissions,
            see Amazon
            Web Services Identity and Access Management (IAM) for S3 Express One Zone in the
            Amazon S3 User Guide.
            
Directory buckets  - The HTTP Host header syntax is s3express-control.region-code.amazonaws.com.
            
            The following operations are related to DeleteBucketPolicy
            You must URL encode any signed header values that contain spaces. For example, if
            your header value is my file.txt, containing two spaces after my, you
            must URL encode this value to my%20%20file.txt.
            
This is an asynchronous operation using the standard naming convention for .NET 4.7.2 or higher.
Namespace: Amazon.S3
Assembly: AWSSDK.S3.dll
Version: 3.x.y.z
public abstract Task<DeleteBucketPolicyResponse> DeleteBucketPolicyAsync( DeleteBucketPolicyRequest request, CancellationToken cancellationToken )
Container for the necessary parameters to execute the DeleteBucketPolicy service method.
A cancellation token that can be used by other objects or threads to receive notice of cancellation.
.NET: 
Supported in: 8.0 and newer, Core 3.1
.NET Standard: 
Supported in: 2.0
.NET Framework: 
Supported in: 4.7.2 and newer