S3AsyncClient (AWS Java SDK :: Services

All Superinterfaces:

AutoCloseable, SdkAutoCloseable, SdkClient
```
@Generated(value="software.amazon.awssdk:codegen")
public interface S3AsyncClient
extends SdkClient
```
Service client for accessing Amazon S3 asynchronously. This can be created using the static builder() method.

Field Summary

Fields
Modifier and Type Field and Description

static String SERVICE_NAME

Fields
Modifier and Type	Field and Description
`static String`	`SERVICE_NAME`

Method Summary

All Methods Static Methods Instance Methods Default Methods
Modifier and Type	Method and Description
`default CompletableFuture<AbortMultipartUploadResponse>`	`abortMultipartUpload(AbortMultipartUploadRequest abortMultipartUploadRequest)` This operation aborts a multipart upload.
`default CompletableFuture<AbortMultipartUploadResponse>`	`abortMultipartUpload(Consumer<AbortMultipartUploadRequest.Builder> abortMultipartUploadRequest)` This operation aborts a multipart upload.
`static S3AsyncClientBuilder`	`builder()` Create a builder that can be used to configure and create a `S3AsyncClient`.
`default CompletableFuture<CompleteMultipartUploadResponse>`	`completeMultipartUpload(CompleteMultipartUploadRequest completeMultipartUploadRequest)` Completes a multipart upload by assembling previously uploaded parts.
`default CompletableFuture<CompleteMultipartUploadResponse>`	`completeMultipartUpload(Consumer<CompleteMultipartUploadRequest.Builder> completeMultipartUploadRequest)` Completes a multipart upload by assembling previously uploaded parts.
`default CompletableFuture<CopyObjectResponse>`	`copyObject(Consumer<CopyObjectRequest.Builder> copyObjectRequest)` Creates a copy of an object that is already stored in Amazon S3.
`default CompletableFuture<CopyObjectResponse>`	`copyObject(CopyObjectRequest copyObjectRequest)` Creates a copy of an object that is already stored in Amazon S3.
`static S3AsyncClient`	`create()` Create a `S3AsyncClient` with the region loaded from the `DefaultAwsRegionProviderChain` and credentials loaded from the `DefaultCredentialsProvider`.
`default CompletableFuture<CreateBucketResponse>`	`createBucket(Consumer<CreateBucketRequest.Builder> createBucketRequest)` Creates a new bucket.
`default CompletableFuture<CreateBucketResponse>`	`createBucket(CreateBucketRequest createBucketRequest)` Creates a new bucket.
`default CompletableFuture<CreateMultipartUploadResponse>`	`createMultipartUpload(Consumer<CreateMultipartUploadRequest.Builder> createMultipartUploadRequest)` This operation initiates a multipart upload and returns an upload ID.
`default CompletableFuture<CreateMultipartUploadResponse>`	`createMultipartUpload(CreateMultipartUploadRequest createMultipartUploadRequest)` This operation initiates a multipart upload and returns an upload ID.
`default CompletableFuture<DeleteBucketResponse>`	`deleteBucket(Consumer<DeleteBucketRequest.Builder> deleteBucketRequest)` Deletes the bucket.
`default CompletableFuture<DeleteBucketResponse>`	`deleteBucket(DeleteBucketRequest deleteBucketRequest)` Deletes the bucket.
`default CompletableFuture<DeleteBucketAnalyticsConfigurationResponse>`	`deleteBucketAnalyticsConfiguration(Consumer<DeleteBucketAnalyticsConfigurationRequest.Builder> deleteBucketAnalyticsConfigurationRequest)` Deletes an analytics configuration for the bucket (specified by the analytics configuration ID).
`default CompletableFuture<DeleteBucketAnalyticsConfigurationResponse>`	`deleteBucketAnalyticsConfiguration(DeleteBucketAnalyticsConfigurationRequest deleteBucketAnalyticsConfigurationRequest)` Deletes an analytics configuration for the bucket (specified by the analytics configuration ID).
`default CompletableFuture<DeleteBucketCorsResponse>`	`deleteBucketCors(Consumer<DeleteBucketCorsRequest.Builder> deleteBucketCorsRequest)` Deletes the `cors` configuration information set for the bucket.
`default CompletableFuture<DeleteBucketCorsResponse>`	`deleteBucketCors(DeleteBucketCorsRequest deleteBucketCorsRequest)` Deletes the `cors` configuration information set for the bucket.
`default CompletableFuture<DeleteBucketEncryptionResponse>`	`deleteBucketEncryption(Consumer<DeleteBucketEncryptionRequest.Builder> deleteBucketEncryptionRequest)` This implementation of the DELETE operation removes default encryption from the bucket.
`default CompletableFuture<DeleteBucketEncryptionResponse>`	`deleteBucketEncryption(DeleteBucketEncryptionRequest deleteBucketEncryptionRequest)` This implementation of the DELETE operation removes default encryption from the bucket.
`default CompletableFuture<DeleteBucketInventoryConfigurationResponse>`	`deleteBucketInventoryConfiguration(Consumer<DeleteBucketInventoryConfigurationRequest.Builder> deleteBucketInventoryConfigurationRequest)` Deletes an inventory configuration (identified by the inventory ID) from the bucket.
`default CompletableFuture<DeleteBucketInventoryConfigurationResponse>`	`deleteBucketInventoryConfiguration(DeleteBucketInventoryConfigurationRequest deleteBucketInventoryConfigurationRequest)` Deletes an inventory configuration (identified by the inventory ID) from the bucket.
`default CompletableFuture<DeleteBucketLifecycleResponse>`	`deleteBucketLifecycle(Consumer<DeleteBucketLifecycleRequest.Builder> deleteBucketLifecycleRequest)` Deletes the lifecycle configuration from the specified bucket.
`default CompletableFuture<DeleteBucketLifecycleResponse>`	`deleteBucketLifecycle(DeleteBucketLifecycleRequest deleteBucketLifecycleRequest)` Deletes the lifecycle configuration from the specified bucket.
`default CompletableFuture<DeleteBucketMetricsConfigurationResponse>`	`deleteBucketMetricsConfiguration(Consumer<DeleteBucketMetricsConfigurationRequest.Builder> deleteBucketMetricsConfigurationRequest)` Deletes a metrics configuration for the Amazon CloudWatch request metrics (specified by the metrics configuration ID) from the bucket.
`default CompletableFuture<DeleteBucketMetricsConfigurationResponse>`	`deleteBucketMetricsConfiguration(DeleteBucketMetricsConfigurationRequest deleteBucketMetricsConfigurationRequest)` Deletes a metrics configuration for the Amazon CloudWatch request metrics (specified by the metrics configuration ID) from the bucket.
`default CompletableFuture<DeleteBucketPolicyResponse>`	`deleteBucketPolicy(Consumer<DeleteBucketPolicyRequest.Builder> deleteBucketPolicyRequest)` This implementation of the DELETE operation uses the policy subresource to delete the policy of a specified bucket.
`default CompletableFuture<DeleteBucketPolicyResponse>`	`deleteBucketPolicy(DeleteBucketPolicyRequest deleteBucketPolicyRequest)` This implementation of the DELETE operation uses the policy subresource to delete the policy of a specified bucket.
`default CompletableFuture<DeleteBucketReplicationResponse>`	`deleteBucketReplication(Consumer<DeleteBucketReplicationRequest.Builder> deleteBucketReplicationRequest)` Deletes the replication configuration from the bucket.
`default CompletableFuture<DeleteBucketReplicationResponse>`	`deleteBucketReplication(DeleteBucketReplicationRequest deleteBucketReplicationRequest)` Deletes the replication configuration from the bucket.
`default CompletableFuture<DeleteBucketTaggingResponse>`	`deleteBucketTagging(Consumer<DeleteBucketTaggingRequest.Builder> deleteBucketTaggingRequest)` Deletes the tags from the bucket.
`default CompletableFuture<DeleteBucketTaggingResponse>`	`deleteBucketTagging(DeleteBucketTaggingRequest deleteBucketTaggingRequest)` Deletes the tags from the bucket.
`default CompletableFuture<DeleteBucketWebsiteResponse>`	`deleteBucketWebsite(Consumer<DeleteBucketWebsiteRequest.Builder> deleteBucketWebsiteRequest)` This operation removes the website configuration for a bucket.
`default CompletableFuture<DeleteBucketWebsiteResponse>`	`deleteBucketWebsite(DeleteBucketWebsiteRequest deleteBucketWebsiteRequest)` This operation removes the website configuration for a bucket.
`default CompletableFuture<DeleteObjectResponse>`	`deleteObject(Consumer<DeleteObjectRequest.Builder> deleteObjectRequest)` Removes the null version (if there is one) of an object and inserts a delete marker, which becomes the latest version of the object.
`default CompletableFuture<DeleteObjectResponse>`	`deleteObject(DeleteObjectRequest deleteObjectRequest)` Removes the null version (if there is one) of an object and inserts a delete marker, which becomes the latest version of the object.
`default CompletableFuture<DeleteObjectsResponse>`	`deleteObjects(Consumer<DeleteObjectsRequest.Builder> deleteObjectsRequest)` This operation enables you to delete multiple objects from a bucket using a single HTTP request.
`default CompletableFuture<DeleteObjectsResponse>`	`deleteObjects(DeleteObjectsRequest deleteObjectsRequest)` This operation enables you to delete multiple objects from a bucket using a single HTTP request.
`default CompletableFuture<DeleteObjectTaggingResponse>`	`deleteObjectTagging(Consumer<DeleteObjectTaggingRequest.Builder> deleteObjectTaggingRequest)` Removes the entire tag set from the specified object.
`default CompletableFuture<DeleteObjectTaggingResponse>`	`deleteObjectTagging(DeleteObjectTaggingRequest deleteObjectTaggingRequest)` Removes the entire tag set from the specified object.
`default CompletableFuture<DeletePublicAccessBlockResponse>`	`deletePublicAccessBlock(Consumer<DeletePublicAccessBlockRequest.Builder> deletePublicAccessBlockRequest)` Removes the `PublicAccessBlock` configuration for an Amazon S3 bucket.
`default CompletableFuture<DeletePublicAccessBlockResponse>`	`deletePublicAccessBlock(DeletePublicAccessBlockRequest deletePublicAccessBlockRequest)` Removes the `PublicAccessBlock` configuration for an Amazon S3 bucket.
`default CompletableFuture<GetBucketAccelerateConfigurationResponse>`	`getBucketAccelerateConfiguration(Consumer<GetBucketAccelerateConfigurationRequest.Builder> getBucketAccelerateConfigurationRequest)` This implementation of the GET operation uses the `accelerate` subresource to return the Transfer Acceleration state of a bucket, which is either `Enabled` or `Suspended`.
`default CompletableFuture<GetBucketAccelerateConfigurationResponse>`	`getBucketAccelerateConfiguration(GetBucketAccelerateConfigurationRequest getBucketAccelerateConfigurationRequest)` This implementation of the GET operation uses the `accelerate` subresource to return the Transfer Acceleration state of a bucket, which is either `Enabled` or `Suspended`.
`default CompletableFuture<GetBucketAclResponse>`	`getBucketAcl(Consumer<GetBucketAclRequest.Builder> getBucketAclRequest)` This implementation of the `GET` operation uses the `acl` subresource to return the access control list (ACL) of a bucket.
`default CompletableFuture<GetBucketAclResponse>`	`getBucketAcl(GetBucketAclRequest getBucketAclRequest)` This implementation of the `GET` operation uses the `acl` subresource to return the access control list (ACL) of a bucket.
`default CompletableFuture<GetBucketAnalyticsConfigurationResponse>`	`getBucketAnalyticsConfiguration(Consumer<GetBucketAnalyticsConfigurationRequest.Builder> getBucketAnalyticsConfigurationRequest)` This implementation of the GET operation returns an analytics configuration (identified by the analytics configuration ID) from the bucket.
`default CompletableFuture<GetBucketAnalyticsConfigurationResponse>`	`getBucketAnalyticsConfiguration(GetBucketAnalyticsConfigurationRequest getBucketAnalyticsConfigurationRequest)` This implementation of the GET operation returns an analytics configuration (identified by the analytics configuration ID) from the bucket.
`default CompletableFuture<GetBucketCorsResponse>`	`getBucketCors(Consumer<GetBucketCorsRequest.Builder> getBucketCorsRequest)` Returns the cors configuration information set for the bucket.
`default CompletableFuture<GetBucketCorsResponse>`	`getBucketCors(GetBucketCorsRequest getBucketCorsRequest)` Returns the cors configuration information set for the bucket.
`default CompletableFuture<GetBucketEncryptionResponse>`	`getBucketEncryption(Consumer<GetBucketEncryptionRequest.Builder> getBucketEncryptionRequest)` Returns the default encryption configuration for an Amazon S3 bucket.
`default CompletableFuture<GetBucketEncryptionResponse>`	`getBucketEncryption(GetBucketEncryptionRequest getBucketEncryptionRequest)` Returns the default encryption configuration for an Amazon S3 bucket.
`default CompletableFuture<GetBucketInventoryConfigurationResponse>`	`getBucketInventoryConfiguration(Consumer<GetBucketInventoryConfigurationRequest.Builder> getBucketInventoryConfigurationRequest)` Returns an inventory configuration (identified by the inventory configuration ID) from the bucket.
`default CompletableFuture<GetBucketInventoryConfigurationResponse>`	`getBucketInventoryConfiguration(GetBucketInventoryConfigurationRequest getBucketInventoryConfigurationRequest)` Returns an inventory configuration (identified by the inventory configuration ID) from the bucket.
`default CompletableFuture<GetBucketLifecycleConfigurationResponse>`	`getBucketLifecycleConfiguration(Consumer<GetBucketLifecycleConfigurationRequest.Builder> getBucketLifecycleConfigurationRequest)`
`default CompletableFuture<GetBucketLifecycleConfigurationResponse>`	`getBucketLifecycleConfiguration(GetBucketLifecycleConfigurationRequest getBucketLifecycleConfigurationRequest)`
`default CompletableFuture<GetBucketLocationResponse>`	`getBucketLocation(Consumer<GetBucketLocationRequest.Builder> getBucketLocationRequest)` Returns the Region the bucket resides in.
`default CompletableFuture<GetBucketLocationResponse>`	`getBucketLocation(GetBucketLocationRequest getBucketLocationRequest)` Returns the Region the bucket resides in.
`default CompletableFuture<GetBucketLoggingResponse>`	`getBucketLogging(Consumer<GetBucketLoggingRequest.Builder> getBucketLoggingRequest)` Returns the logging status of a bucket and the permissions users have to view and modify that status.
`default CompletableFuture<GetBucketLoggingResponse>`	`getBucketLogging(GetBucketLoggingRequest getBucketLoggingRequest)` Returns the logging status of a bucket and the permissions users have to view and modify that status.
`default CompletableFuture<GetBucketMetricsConfigurationResponse>`	`getBucketMetricsConfiguration(Consumer<GetBucketMetricsConfigurationRequest.Builder> getBucketMetricsConfigurationRequest)` Gets a metrics configuration (specified by the metrics configuration ID) from the bucket.
`default CompletableFuture<GetBucketMetricsConfigurationResponse>`	`getBucketMetricsConfiguration(GetBucketMetricsConfigurationRequest getBucketMetricsConfigurationRequest)` Gets a metrics configuration (specified by the metrics configuration ID) from the bucket.
`default CompletableFuture<GetBucketNotificationConfigurationResponse>`	`getBucketNotificationConfiguration(Consumer<GetBucketNotificationConfigurationRequest.Builder> getBucketNotificationConfigurationRequest)` Returns the notification configuration of a bucket.
`default CompletableFuture<GetBucketNotificationConfigurationResponse>`	`getBucketNotificationConfiguration(GetBucketNotificationConfigurationRequest getBucketNotificationConfigurationRequest)` Returns the notification configuration of a bucket.
`default CompletableFuture<GetBucketPolicyResponse>`	`getBucketPolicy(Consumer<GetBucketPolicyRequest.Builder> getBucketPolicyRequest)` Returns the policy of a specified bucket.
`default CompletableFuture<GetBucketPolicyResponse>`	`getBucketPolicy(GetBucketPolicyRequest getBucketPolicyRequest)` Returns the policy of a specified bucket.
`default CompletableFuture<GetBucketPolicyStatusResponse>`	`getBucketPolicyStatus(Consumer<GetBucketPolicyStatusRequest.Builder> getBucketPolicyStatusRequest)` Retrieves the policy status for an Amazon S3 bucket, indicating whether the bucket is public.
`default CompletableFuture<GetBucketPolicyStatusResponse>`	`getBucketPolicyStatus(GetBucketPolicyStatusRequest getBucketPolicyStatusRequest)` Retrieves the policy status for an Amazon S3 bucket, indicating whether the bucket is public.
`default CompletableFuture<GetBucketReplicationResponse>`	`getBucketReplication(Consumer<GetBucketReplicationRequest.Builder> getBucketReplicationRequest)` Returns the replication configuration of a bucket.
`default CompletableFuture<GetBucketReplicationResponse>`	`getBucketReplication(GetBucketReplicationRequest getBucketReplicationRequest)` Returns the replication configuration of a bucket.
`default CompletableFuture<GetBucketRequestPaymentResponse>`	`getBucketRequestPayment(Consumer<GetBucketRequestPaymentRequest.Builder> getBucketRequestPaymentRequest)` Returns the request payment configuration of a bucket.
`default CompletableFuture<GetBucketRequestPaymentResponse>`	`getBucketRequestPayment(GetBucketRequestPaymentRequest getBucketRequestPaymentRequest)` Returns the request payment configuration of a bucket.
`default CompletableFuture<GetBucketTaggingResponse>`	`getBucketTagging(Consumer<GetBucketTaggingRequest.Builder> getBucketTaggingRequest)` Returns the tag set associated with the bucket.
`default CompletableFuture<GetBucketTaggingResponse>`	`getBucketTagging(GetBucketTaggingRequest getBucketTaggingRequest)` Returns the tag set associated with the bucket.
`default CompletableFuture<GetBucketVersioningResponse>`	`getBucketVersioning(Consumer<GetBucketVersioningRequest.Builder> getBucketVersioningRequest)` Returns the versioning state of a bucket.
`default CompletableFuture<GetBucketVersioningResponse>`	`getBucketVersioning(GetBucketVersioningRequest getBucketVersioningRequest)` Returns the versioning state of a bucket.
`default CompletableFuture<GetBucketWebsiteResponse>`	`getBucketWebsite(Consumer<GetBucketWebsiteRequest.Builder> getBucketWebsiteRequest)` Returns the website configuration for a bucket.
`default CompletableFuture<GetBucketWebsiteResponse>`	`getBucketWebsite(GetBucketWebsiteRequest getBucketWebsiteRequest)` Returns the website configuration for a bucket.
`default <ReturnT> CompletableFuture<ReturnT>`	`getObject(Consumer<GetObjectRequest.Builder> getObjectRequest, AsyncResponseTransformer<GetObjectResponse,ReturnT> asyncResponseTransformer)` Retrieves objects from Amazon S3.
`default CompletableFuture<GetObjectResponse>`	`getObject(Consumer<GetObjectRequest.Builder> getObjectRequest, Path destinationPath)` Retrieves objects from Amazon S3.
`default <ReturnT> CompletableFuture<ReturnT>`	`getObject(GetObjectRequest getObjectRequest, AsyncResponseTransformer<GetObjectResponse,ReturnT> asyncResponseTransformer)` Retrieves objects from Amazon S3.
`default CompletableFuture<GetObjectResponse>`	`getObject(GetObjectRequest getObjectRequest, Path destinationPath)` Retrieves objects from Amazon S3.
`default CompletableFuture<GetObjectAclResponse>`	`getObjectAcl(Consumer<GetObjectAclRequest.Builder> getObjectAclRequest)` Returns the access control list (ACL) of an object.
`default CompletableFuture<GetObjectAclResponse>`	`getObjectAcl(GetObjectAclRequest getObjectAclRequest)` Returns the access control list (ACL) of an object.
`default CompletableFuture<GetObjectLegalHoldResponse>`	`getObjectLegalHold(Consumer<GetObjectLegalHoldRequest.Builder> getObjectLegalHoldRequest)` Gets an object's current Legal Hold status.
`default CompletableFuture<GetObjectLegalHoldResponse>`	`getObjectLegalHold(GetObjectLegalHoldRequest getObjectLegalHoldRequest)` Gets an object's current Legal Hold status.
`default CompletableFuture<GetObjectLockConfigurationResponse>`	`getObjectLockConfiguration(Consumer<GetObjectLockConfigurationRequest.Builder> getObjectLockConfigurationRequest)` Gets the Object Lock configuration for a bucket.
`default CompletableFuture<GetObjectLockConfigurationResponse>`	`getObjectLockConfiguration(GetObjectLockConfigurationRequest getObjectLockConfigurationRequest)` Gets the Object Lock configuration for a bucket.
`default CompletableFuture<GetObjectRetentionResponse>`	`getObjectRetention(Consumer<GetObjectRetentionRequest.Builder> getObjectRetentionRequest)` Retrieves an object's retention settings.
`default CompletableFuture<GetObjectRetentionResponse>`	`getObjectRetention(GetObjectRetentionRequest getObjectRetentionRequest)` Retrieves an object's retention settings.
`default CompletableFuture<GetObjectTaggingResponse>`	`getObjectTagging(Consumer<GetObjectTaggingRequest.Builder> getObjectTaggingRequest)` Returns the tag-set of an object.
`default CompletableFuture<GetObjectTaggingResponse>`	`getObjectTagging(GetObjectTaggingRequest getObjectTaggingRequest)` Returns the tag-set of an object.
`default <ReturnT> CompletableFuture<ReturnT>`	`getObjectTorrent(Consumer<GetObjectTorrentRequest.Builder> getObjectTorrentRequest, AsyncResponseTransformer<GetObjectTorrentResponse,ReturnT> asyncResponseTransformer)` Return torrent files from a bucket.
`default CompletableFuture<GetObjectTorrentResponse>`	`getObjectTorrent(Consumer<GetObjectTorrentRequest.Builder> getObjectTorrentRequest, Path destinationPath)` Return torrent files from a bucket.
`default <ReturnT> CompletableFuture<ReturnT>`	`getObjectTorrent(GetObjectTorrentRequest getObjectTorrentRequest, AsyncResponseTransformer<GetObjectTorrentResponse,ReturnT> asyncResponseTransformer)` Return torrent files from a bucket.
`default CompletableFuture<GetObjectTorrentResponse>`	`getObjectTorrent(GetObjectTorrentRequest getObjectTorrentRequest, Path destinationPath)` Return torrent files from a bucket.
`default CompletableFuture<GetPublicAccessBlockResponse>`	`getPublicAccessBlock(Consumer<GetPublicAccessBlockRequest.Builder> getPublicAccessBlockRequest)` Retrieves the `PublicAccessBlock` configuration for an Amazon S3 bucket.
`default CompletableFuture<GetPublicAccessBlockResponse>`	`getPublicAccessBlock(GetPublicAccessBlockRequest getPublicAccessBlockRequest)` Retrieves the `PublicAccessBlock` configuration for an Amazon S3 bucket.
`default CompletableFuture<HeadBucketResponse>`	`headBucket(Consumer<HeadBucketRequest.Builder> headBucketRequest)` This operation is useful to determine if a bucket exists and you have permission to access it.
`default CompletableFuture<HeadBucketResponse>`	`headBucket(HeadBucketRequest headBucketRequest)` This operation is useful to determine if a bucket exists and you have permission to access it.
`default CompletableFuture<HeadObjectResponse>`	`headObject(Consumer<HeadObjectRequest.Builder> headObjectRequest)` The HEAD operation retrieves metadata from an object without returning the object itself.
`default CompletableFuture<HeadObjectResponse>`	`headObject(HeadObjectRequest headObjectRequest)` The HEAD operation retrieves metadata from an object without returning the object itself.
`default CompletableFuture<ListBucketAnalyticsConfigurationsResponse>`	`listBucketAnalyticsConfigurations(Consumer<ListBucketAnalyticsConfigurationsRequest.Builder> listBucketAnalyticsConfigurationsRequest)` Lists the analytics configurations for the bucket.
`default CompletableFuture<ListBucketAnalyticsConfigurationsResponse>`	`listBucketAnalyticsConfigurations(ListBucketAnalyticsConfigurationsRequest listBucketAnalyticsConfigurationsRequest)` Lists the analytics configurations for the bucket.
`default CompletableFuture<ListBucketInventoryConfigurationsResponse>`	`listBucketInventoryConfigurations(Consumer<ListBucketInventoryConfigurationsRequest.Builder> listBucketInventoryConfigurationsRequest)` Returns a list of inventory configurations for the bucket.
`default CompletableFuture<ListBucketInventoryConfigurationsResponse>`	`listBucketInventoryConfigurations(ListBucketInventoryConfigurationsRequest listBucketInventoryConfigurationsRequest)` Returns a list of inventory configurations for the bucket.
`default CompletableFuture<ListBucketMetricsConfigurationsResponse>`	`listBucketMetricsConfigurations(Consumer<ListBucketMetricsConfigurationsRequest.Builder> listBucketMetricsConfigurationsRequest)` Lists the metrics configurations for the bucket.
`default CompletableFuture<ListBucketMetricsConfigurationsResponse>`	`listBucketMetricsConfigurations(ListBucketMetricsConfigurationsRequest listBucketMetricsConfigurationsRequest)` Lists the metrics configurations for the bucket.
`default CompletableFuture<ListBucketsResponse>`	`listBuckets()` Returns a list of all buckets owned by the authenticated sender of the request.
`default CompletableFuture<ListBucketsResponse>`	`listBuckets(Consumer<ListBucketsRequest.Builder> listBucketsRequest)` Returns a list of all buckets owned by the authenticated sender of the request.
`default CompletableFuture<ListBucketsResponse>`	`listBuckets(ListBucketsRequest listBucketsRequest)` Returns a list of all buckets owned by the authenticated sender of the request.
`default CompletableFuture<ListMultipartUploadsResponse>`	`listMultipartUploads(Consumer<ListMultipartUploadsRequest.Builder> listMultipartUploadsRequest)` This operation lists in-progress multipart uploads.
`default CompletableFuture<ListMultipartUploadsResponse>`	`listMultipartUploads(ListMultipartUploadsRequest listMultipartUploadsRequest)` This operation lists in-progress multipart uploads.
`default ListMultipartUploadsPublisher`	`listMultipartUploadsPaginator(Consumer<ListMultipartUploadsRequest.Builder> listMultipartUploadsRequest)` This operation lists in-progress multipart uploads.
`default ListMultipartUploadsPublisher`	`listMultipartUploadsPaginator(ListMultipartUploadsRequest listMultipartUploadsRequest)` This operation lists in-progress multipart uploads.
`default CompletableFuture<ListObjectsResponse>`	`listObjects(Consumer<ListObjectsRequest.Builder> listObjectsRequest)` Returns some or all (up to 1,000) of the objects in a bucket.
`default CompletableFuture<ListObjectsResponse>`	`listObjects(ListObjectsRequest listObjectsRequest)` Returns some or all (up to 1,000) of the objects in a bucket.
`default CompletableFuture<ListObjectsV2Response>`	`listObjectsV2(Consumer<ListObjectsV2Request.Builder> listObjectsV2Request)` Returns some or all (up to 1,000) of the objects in a bucket.
`default CompletableFuture<ListObjectsV2Response>`	`listObjectsV2(ListObjectsV2Request listObjectsV2Request)` Returns some or all (up to 1,000) of the objects in a bucket.
`default ListObjectsV2Publisher`	`listObjectsV2Paginator(Consumer<ListObjectsV2Request.Builder> listObjectsV2Request)` Returns some or all (up to 1,000) of the objects in a bucket.
`default ListObjectsV2Publisher`	`listObjectsV2Paginator(ListObjectsV2Request listObjectsV2Request)` Returns some or all (up to 1,000) of the objects in a bucket.
`default CompletableFuture<ListObjectVersionsResponse>`	`listObjectVersions(Consumer<ListObjectVersionsRequest.Builder> listObjectVersionsRequest)` Returns metadata about all of the versions of objects in a bucket.
`default CompletableFuture<ListObjectVersionsResponse>`	`listObjectVersions(ListObjectVersionsRequest listObjectVersionsRequest)` Returns metadata about all of the versions of objects in a bucket.
`default ListObjectVersionsPublisher`	`listObjectVersionsPaginator(Consumer<ListObjectVersionsRequest.Builder> listObjectVersionsRequest)` Returns metadata about all of the versions of objects in a bucket.
`default ListObjectVersionsPublisher`	`listObjectVersionsPaginator(ListObjectVersionsRequest listObjectVersionsRequest)` Returns metadata about all of the versions of objects in a bucket.
`default CompletableFuture<ListPartsResponse>`	`listParts(Consumer<ListPartsRequest.Builder> listPartsRequest)` Lists the parts that have been uploaded for a specific multipart upload.
`default CompletableFuture<ListPartsResponse>`	`listParts(ListPartsRequest listPartsRequest)` Lists the parts that have been uploaded for a specific multipart upload.
`default ListPartsPublisher`	`listPartsPaginator(Consumer<ListPartsRequest.Builder> listPartsRequest)` Lists the parts that have been uploaded for a specific multipart upload.
`default ListPartsPublisher`	`listPartsPaginator(ListPartsRequest listPartsRequest)` Lists the parts that have been uploaded for a specific multipart upload.
`default CompletableFuture<PutBucketAccelerateConfigurationResponse>`	`putBucketAccelerateConfiguration(Consumer<PutBucketAccelerateConfigurationRequest.Builder> putBucketAccelerateConfigurationRequest)` Sets the accelerate configuration of an existing bucket.
`default CompletableFuture<PutBucketAccelerateConfigurationResponse>`	`putBucketAccelerateConfiguration(PutBucketAccelerateConfigurationRequest putBucketAccelerateConfigurationRequest)` Sets the accelerate configuration of an existing bucket.
`default CompletableFuture<PutBucketAclResponse>`	`putBucketAcl(Consumer<PutBucketAclRequest.Builder> putBucketAclRequest)` Sets the permissions on an existing bucket using access control lists (ACL).
`default CompletableFuture<PutBucketAclResponse>`	`putBucketAcl(PutBucketAclRequest putBucketAclRequest)` Sets the permissions on an existing bucket using access control lists (ACL).
`default CompletableFuture<PutBucketAnalyticsConfigurationResponse>`	`putBucketAnalyticsConfiguration(Consumer<PutBucketAnalyticsConfigurationRequest.Builder> putBucketAnalyticsConfigurationRequest)` Sets an analytics configuration for the bucket (specified by the analytics configuration ID).
`default CompletableFuture<PutBucketAnalyticsConfigurationResponse>`	`putBucketAnalyticsConfiguration(PutBucketAnalyticsConfigurationRequest putBucketAnalyticsConfigurationRequest)` Sets an analytics configuration for the bucket (specified by the analytics configuration ID).
`default CompletableFuture<PutBucketCorsResponse>`	`putBucketCors(Consumer<PutBucketCorsRequest.Builder> putBucketCorsRequest)` Sets the `cors` configuration for your bucket.
`default CompletableFuture<PutBucketCorsResponse>`	`putBucketCors(PutBucketCorsRequest putBucketCorsRequest)` Sets the `cors` configuration for your bucket.
`default CompletableFuture<PutBucketEncryptionResponse>`	`putBucketEncryption(Consumer<PutBucketEncryptionRequest.Builder> putBucketEncryptionRequest)` This implementation of the `PUT` operation uses the `encryption` subresource to set the default encryption state of an existing bucket.
`default CompletableFuture<PutBucketEncryptionResponse>`	`putBucketEncryption(PutBucketEncryptionRequest putBucketEncryptionRequest)` This implementation of the `PUT` operation uses the `encryption` subresource to set the default encryption state of an existing bucket.
`default CompletableFuture<PutBucketInventoryConfigurationResponse>`	`putBucketInventoryConfiguration(Consumer<PutBucketInventoryConfigurationRequest.Builder> putBucketInventoryConfigurationRequest)` This implementation of the `PUT` operation adds an inventory configuration (identified by the inventory ID) to the bucket.
`default CompletableFuture<PutBucketInventoryConfigurationResponse>`	`putBucketInventoryConfiguration(PutBucketInventoryConfigurationRequest putBucketInventoryConfigurationRequest)` This implementation of the `PUT` operation adds an inventory configuration (identified by the inventory ID) to the bucket.
`default CompletableFuture<PutBucketLifecycleConfigurationResponse>`	`putBucketLifecycleConfiguration(Consumer<PutBucketLifecycleConfigurationRequest.Builder> putBucketLifecycleConfigurationRequest)` Creates a new lifecycle configuration for the bucket or replaces an existing lifecycle configuration.
`default CompletableFuture<PutBucketLifecycleConfigurationResponse>`	`putBucketLifecycleConfiguration(PutBucketLifecycleConfigurationRequest putBucketLifecycleConfigurationRequest)` Creates a new lifecycle configuration for the bucket or replaces an existing lifecycle configuration.
`default CompletableFuture<PutBucketLoggingResponse>`	`putBucketLogging(Consumer<PutBucketLoggingRequest.Builder> putBucketLoggingRequest)` Set the logging parameters for a bucket and to specify permissions for who can view and modify the logging parameters.
`default CompletableFuture<PutBucketLoggingResponse>`	`putBucketLogging(PutBucketLoggingRequest putBucketLoggingRequest)` Set the logging parameters for a bucket and to specify permissions for who can view and modify the logging parameters.
`default CompletableFuture<PutBucketMetricsConfigurationResponse>`	`putBucketMetricsConfiguration(Consumer<PutBucketMetricsConfigurationRequest.Builder> putBucketMetricsConfigurationRequest)` Sets a metrics configuration (specified by the metrics configuration ID) for the bucket.
`default CompletableFuture<PutBucketMetricsConfigurationResponse>`	`putBucketMetricsConfiguration(PutBucketMetricsConfigurationRequest putBucketMetricsConfigurationRequest)` Sets a metrics configuration (specified by the metrics configuration ID) for the bucket.
`default CompletableFuture<PutBucketNotificationConfigurationResponse>`	`putBucketNotificationConfiguration(Consumer<PutBucketNotificationConfigurationRequest.Builder> putBucketNotificationConfigurationRequest)` Enables notifications of specified events for a bucket.
`default CompletableFuture<PutBucketNotificationConfigurationResponse>`	`putBucketNotificationConfiguration(PutBucketNotificationConfigurationRequest putBucketNotificationConfigurationRequest)` Enables notifications of specified events for a bucket.
`default CompletableFuture<PutBucketPolicyResponse>`	`putBucketPolicy(Consumer<PutBucketPolicyRequest.Builder> putBucketPolicyRequest)` Applies an Amazon S3 bucket policy to an Amazon S3 bucket.
`default CompletableFuture<PutBucketPolicyResponse>`	`putBucketPolicy(PutBucketPolicyRequest putBucketPolicyRequest)` Applies an Amazon S3 bucket policy to an Amazon S3 bucket.
`default CompletableFuture<PutBucketReplicationResponse>`	`putBucketReplication(Consumer<PutBucketReplicationRequest.Builder> putBucketReplicationRequest)` Creates a replication configuration or replaces an existing one.
`default CompletableFuture<PutBucketReplicationResponse>`	`putBucketReplication(PutBucketReplicationRequest putBucketReplicationRequest)` Creates a replication configuration or replaces an existing one.
`default CompletableFuture<PutBucketRequestPaymentResponse>`	`putBucketRequestPayment(Consumer<PutBucketRequestPaymentRequest.Builder> putBucketRequestPaymentRequest)` Sets the request payment configuration for a bucket.
`default CompletableFuture<PutBucketRequestPaymentResponse>`	`putBucketRequestPayment(PutBucketRequestPaymentRequest putBucketRequestPaymentRequest)` Sets the request payment configuration for a bucket.
`default CompletableFuture<PutBucketTaggingResponse>`	`putBucketTagging(Consumer<PutBucketTaggingRequest.Builder> putBucketTaggingRequest)` Sets the tags for a bucket.
`default CompletableFuture<PutBucketTaggingResponse>`	`putBucketTagging(PutBucketTaggingRequest putBucketTaggingRequest)` Sets the tags for a bucket.
`default CompletableFuture<PutBucketVersioningResponse>`	`putBucketVersioning(Consumer<PutBucketVersioningRequest.Builder> putBucketVersioningRequest)` Sets the versioning state of an existing bucket.
`default CompletableFuture<PutBucketVersioningResponse>`	`putBucketVersioning(PutBucketVersioningRequest putBucketVersioningRequest)` Sets the versioning state of an existing bucket.
`default CompletableFuture<PutBucketWebsiteResponse>`	`putBucketWebsite(Consumer<PutBucketWebsiteRequest.Builder> putBucketWebsiteRequest)` Sets the configuration of the website that is specified in the `website` subresource.
`default CompletableFuture<PutBucketWebsiteResponse>`	`putBucketWebsite(PutBucketWebsiteRequest putBucketWebsiteRequest)` Sets the configuration of the website that is specified in the `website` subresource.
`default CompletableFuture<PutObjectResponse>`	`putObject(Consumer<PutObjectRequest.Builder> putObjectRequest, AsyncRequestBody requestBody)` Adds an object to a bucket.
`default CompletableFuture<PutObjectResponse>`	`putObject(Consumer<PutObjectRequest.Builder> putObjectRequest, Path sourcePath)` Adds an object to a bucket.
`default CompletableFuture<PutObjectResponse>`	`putObject(PutObjectRequest putObjectRequest, AsyncRequestBody requestBody)` Adds an object to a bucket.
`default CompletableFuture<PutObjectResponse>`	`putObject(PutObjectRequest putObjectRequest, Path sourcePath)` Adds an object to a bucket.
`default CompletableFuture<PutObjectAclResponse>`	`putObjectAcl(Consumer<PutObjectAclRequest.Builder> putObjectAclRequest)` Uses the `acl` subresource to set the access control list (ACL) permissions for an object that already exists in a bucket.
`default CompletableFuture<PutObjectAclResponse>`	`putObjectAcl(PutObjectAclRequest putObjectAclRequest)` Uses the `acl` subresource to set the access control list (ACL) permissions for an object that already exists in a bucket.
`default CompletableFuture<PutObjectLegalHoldResponse>`	`putObjectLegalHold(Consumer<PutObjectLegalHoldRequest.Builder> putObjectLegalHoldRequest)` Applies a Legal Hold configuration to the specified object.
`default CompletableFuture<PutObjectLegalHoldResponse>`	`putObjectLegalHold(PutObjectLegalHoldRequest putObjectLegalHoldRequest)` Applies a Legal Hold configuration to the specified object.
`default CompletableFuture<PutObjectLockConfigurationResponse>`	`putObjectLockConfiguration(Consumer<PutObjectLockConfigurationRequest.Builder> putObjectLockConfigurationRequest)` Places an Object Lock configuration on the specified bucket.
`default CompletableFuture<PutObjectLockConfigurationResponse>`	`putObjectLockConfiguration(PutObjectLockConfigurationRequest putObjectLockConfigurationRequest)` Places an Object Lock configuration on the specified bucket.
`default CompletableFuture<PutObjectRetentionResponse>`	`putObjectRetention(Consumer<PutObjectRetentionRequest.Builder> putObjectRetentionRequest)` Places an Object Retention configuration on an object.
`default CompletableFuture<PutObjectRetentionResponse>`	`putObjectRetention(PutObjectRetentionRequest putObjectRetentionRequest)` Places an Object Retention configuration on an object.
`default CompletableFuture<PutObjectTaggingResponse>`	`putObjectTagging(Consumer<PutObjectTaggingRequest.Builder> putObjectTaggingRequest)` Sets the supplied tag-set to an object that already exists in a bucket
`default CompletableFuture<PutObjectTaggingResponse>`	`putObjectTagging(PutObjectTaggingRequest putObjectTaggingRequest)` Sets the supplied tag-set to an object that already exists in a bucket
`default CompletableFuture<PutPublicAccessBlockResponse>`	`putPublicAccessBlock(Consumer<PutPublicAccessBlockRequest.Builder> putPublicAccessBlockRequest)` Creates or modifies the `PublicAccessBlock` configuration for an Amazon S3 bucket.
`default CompletableFuture<PutPublicAccessBlockResponse>`	`putPublicAccessBlock(PutPublicAccessBlockRequest putPublicAccessBlockRequest)` Creates or modifies the `PublicAccessBlock` configuration for an Amazon S3 bucket.
`default CompletableFuture<RestoreObjectResponse>`	`restoreObject(Consumer<RestoreObjectRequest.Builder> restoreObjectRequest)` Restores an archived copy of an object back into Amazon S3
`default CompletableFuture<RestoreObjectResponse>`	`restoreObject(RestoreObjectRequest restoreObjectRequest)` Restores an archived copy of an object back into Amazon S3
`default CompletableFuture<UploadPartResponse>`	`uploadPart(Consumer<UploadPartRequest.Builder> uploadPartRequest, AsyncRequestBody requestBody)` Uploads a part in a multipart upload.
`default CompletableFuture<UploadPartResponse>`	`uploadPart(Consumer<UploadPartRequest.Builder> uploadPartRequest, Path sourcePath)` Uploads a part in a multipart upload.
`default CompletableFuture<UploadPartResponse>`	`uploadPart(UploadPartRequest uploadPartRequest, AsyncRequestBody requestBody)` Uploads a part in a multipart upload.
`default CompletableFuture<UploadPartResponse>`	`uploadPart(UploadPartRequest uploadPartRequest, Path sourcePath)` Uploads a part in a multipart upload.
`default CompletableFuture<UploadPartCopyResponse>`	`uploadPartCopy(Consumer<UploadPartCopyRequest.Builder> uploadPartCopyRequest)` Uploads a part by copying data from an existing object as data source.
`default CompletableFuture<UploadPartCopyResponse>`	`uploadPartCopy(UploadPartCopyRequest uploadPartCopyRequest)` Uploads a part by copying data from an existing object as data source.
`default S3Utilities`	`utilities()` Creates an instance of `S3Utilities` object with the configuration set on this client.

Methods inherited from interface software.amazon.awssdk.core.SdkClient
serviceName

Methods inherited from interface software.amazon.awssdk.utils.SdkAutoCloseable
close

- Field Detail
  - SERVICE_NAME
```
static final String SERVICE_NAME
```
    See Also:
    
    Constant Field Values
- Method Detail
  - create
```
static S3AsyncClient create()
```
    Create a S3AsyncClient with the region loaded from the DefaultAwsRegionProviderChain and credentials loaded from the DefaultCredentialsProvider.
  - builder
```
static S3AsyncClientBuilder builder()
```
    Create a builder that can be used to configure and create a S3AsyncClient.
  - abortMultipartUpload
```
default CompletableFuture<AbortMultipartUploadResponse> abortMultipartUpload(AbortMultipartUploadRequest abortMultipartUploadRequest)
```
    This operation aborts a multipart upload. After a multipart upload is aborted, no additional parts can be uploaded using that upload ID. The storage consumed by any previously uploaded parts will be freed. However, if any part uploads are currently in progress, those part uploads might or might not succeed. As a result, it might be necessary to abort a given multipart upload multiple times in order to completely free all storage consumed by all parts.
    
    To verify that all parts have been removed, so you don't get charged for the part storage, you should call the ListParts operation and ensure that the parts list is empty.
    
    For information about permissions required to use the multipart upload API, see Multipart Upload API and Permissions.
    
    The following operations are related to AbortMultipartUpload:
    Parameters:
    
    abortMultipartUploadRequest -
    
    Returns:
    A Java Future containing the result of the AbortMultipartUpload operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    NoSuchUploadException The specified multipart upload does not exist.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - abortMultipartUpload
```
default CompletableFuture<AbortMultipartUploadResponse> abortMultipartUpload(Consumer<AbortMultipartUploadRequest.Builder> abortMultipartUploadRequest)
```
    This operation aborts a multipart upload. After a multipart upload is aborted, no additional parts can be uploaded using that upload ID. The storage consumed by any previously uploaded parts will be freed. However, if any part uploads are currently in progress, those part uploads might or might not succeed. As a result, it might be necessary to abort a given multipart upload multiple times in order to completely free all storage consumed by all parts.
    
    To verify that all parts have been removed, so you don't get charged for the part storage, you should call the ListParts operation and ensure that the parts list is empty.
    
    For information about permissions required to use the multipart upload API, see Multipart Upload API and Permissions.
    
    The following operations are related to AbortMultipartUpload:
    This is a convenience which creates an instance of the AbortMultipartUploadRequest.Builder avoiding the need to create one manually via AbortMultipartUploadRequest.builder()
    Parameters:
    
    abortMultipartUploadRequest - A Consumer that will call methods on AbortMultipartUploadRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the AbortMultipartUpload operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    NoSuchUploadException The specified multipart upload does not exist.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - completeMultipartUpload
```
default CompletableFuture<CompleteMultipartUploadResponse> completeMultipartUpload(CompleteMultipartUploadRequest completeMultipartUploadRequest)
```
    Completes a multipart upload by assembling previously uploaded parts.
    
    You first initiate the multipart upload and then upload all parts using the UploadPart operation. After successfully uploading all relevant parts of an upload, you call this operation to complete the upload. Upon receiving this request, Amazon S3 concatenates all the parts in ascending order by part number to create a new object. In the Complete Multipart Upload request, you must provide the parts list. You must ensure that the parts list is complete. This operation concatenates the parts that you provide in the list. For each part in the list, you must provide the part number and the ETag value, returned after that part was uploaded.
    
    Processing of a Complete Multipart Upload request could take several minutes to complete. After Amazon S3 begins processing the request, it sends an HTTP response header that specifies a 200 OK response. While processing is in progress, Amazon S3 periodically sends white space characters to keep the connection from timing out. Because a request could fail after the initial 200 OK response has been sent, it is important that you check the response body to determine whether the request succeeded.
    
    Note that if CompleteMultipartUpload fails, applications should be prepared to retry the failed requests. For more information, see Amazon S3 Error Best Practices.
    
    For more information about multipart uploads, see Uploading Objects Using Multipart Upload.
    
    For information about permissions required to use the multipart upload API, see Multipart Upload API and Permissions.
    
    GetBucketLifecycle has the following special errors:
    - Error code: EntityTooSmall
      
      Description: Your proposed upload is smaller than the minimum allowed object size. Each part must be at least 5 MB in size, except the last part.
      
      400 Bad Request
    - Error code: InvalidPart
      
      Description: One or more of the specified parts could not be found. The part might not have been uploaded, or the specified entity tag might not have matched the part's entity tag.
      
      400 Bad Request
    - Error code: InvalidPartOrder
      
      Description: The list of parts was not in ascending order. The parts list must be specified in order by part number.
      
      400 Bad Request
    - Error code: NoSuchUpload
      
      Description: The specified multipart upload does not exist. The upload ID might be invalid, or the multipart upload might have been aborted or completed.
      
      404 Not Found
    The following operations are related to DeleteBucketMetricsConfiguration:
    Parameters:
    
    completeMultipartUploadRequest -
    
    Returns:
    A Java Future containing the result of the CompleteMultipartUpload operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - completeMultipartUpload
```
default CompletableFuture<CompleteMultipartUploadResponse> completeMultipartUpload(Consumer<CompleteMultipartUploadRequest.Builder> completeMultipartUploadRequest)
```
    Completes a multipart upload by assembling previously uploaded parts.
    
    You first initiate the multipart upload and then upload all parts using the UploadPart operation. After successfully uploading all relevant parts of an upload, you call this operation to complete the upload. Upon receiving this request, Amazon S3 concatenates all the parts in ascending order by part number to create a new object. In the Complete Multipart Upload request, you must provide the parts list. You must ensure that the parts list is complete. This operation concatenates the parts that you provide in the list. For each part in the list, you must provide the part number and the ETag value, returned after that part was uploaded.
    
    Processing of a Complete Multipart Upload request could take several minutes to complete. After Amazon S3 begins processing the request, it sends an HTTP response header that specifies a 200 OK response. While processing is in progress, Amazon S3 periodically sends white space characters to keep the connection from timing out. Because a request could fail after the initial 200 OK response has been sent, it is important that you check the response body to determine whether the request succeeded.
    
    Note that if CompleteMultipartUpload fails, applications should be prepared to retry the failed requests. For more information, see Amazon S3 Error Best Practices.
    
    For more information about multipart uploads, see Uploading Objects Using Multipart Upload.
    
    For information about permissions required to use the multipart upload API, see Multipart Upload API and Permissions.
    
    GetBucketLifecycle has the following special errors:
    - Error code: EntityTooSmall
      
      Description: Your proposed upload is smaller than the minimum allowed object size. Each part must be at least 5 MB in size, except the last part.
      
      400 Bad Request
    - Error code: InvalidPart
      
      Description: One or more of the specified parts could not be found. The part might not have been uploaded, or the specified entity tag might not have matched the part's entity tag.
      
      400 Bad Request
    - Error code: InvalidPartOrder
      
      Description: The list of parts was not in ascending order. The parts list must be specified in order by part number.
      
      400 Bad Request
    - Error code: NoSuchUpload
      
      Description: The specified multipart upload does not exist. The upload ID might be invalid, or the multipart upload might have been aborted or completed.
      
      404 Not Found
    The following operations are related to DeleteBucketMetricsConfiguration:
    This is a convenience which creates an instance of the CompleteMultipartUploadRequest.Builder avoiding the need to create one manually via CompleteMultipartUploadRequest.builder()
    Parameters:
    
    completeMultipartUploadRequest - A Consumer that will call methods on CompleteMultipartUploadRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the CompleteMultipartUpload operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - copyObject
```
default CompletableFuture<CopyObjectResponse> copyObject(CopyObjectRequest copyObjectRequest)
```
    Creates a copy of an object that is already stored in Amazon S3.
    
    You can store individual objects of up to 5 TB in Amazon S3. You create a copy of your object up to 5 GB in size in a single atomic operation using this API. However, for copying an object greater than 5 GB, you must use the multipart upload Upload Part - Copy API. For more information, see Copy Object Using the REST Multipart Upload API.
    
    When copying an object, you can preserve all metadata (default) or specify new metadata. However, the ACL is not preserved and is set to private for the user making the request. To override the default ACL setting, specify a new ACL when generating a copy request. For more information, see Using ACLs.
    
    Amazon S3 transfer acceleration does not support cross-region copies. If you request a cross-region copy using a transfer acceleration endpoint, you get a 400 Bad Request error. For more information about transfer acceleration, see Transfer Acceleration.
    
    All copy requests must be authenticated. Additionally, you must have read access to the source object and write access to the destination bucket. For more information, see REST Authentication. Both the Region that you want to copy the object from and the Region that you want to copy the object to must be enabled for your account.
    
    To only copy an object under certain conditions, such as whether the Etag matches or whether the object was modified before or after a specified date, use the request parameters x-amz-copy-source-if-match, x-amz-copy-source-if-none-match, x-amz-copy-source-if-unmodified-since, or x-amz-copy-source-if-modified-since.
    
    All headers with the x-amz- prefix, including x-amz-copy-source, must be signed.
    
    You can use this operation to change the storage class of an object that is already stored in Amazon S3 using the StorageClass parameter. For more information, see Storage Classes.
    
    The source object that you are copying can be encrypted or unencrypted. If the source object is encrypted, it can be encrypted by server-side encryption using AWS managed encryption keys or by using a customer-provided encryption key. When copying an object, you can request that Amazon S3 encrypt the target object by using either the AWS managed encryption keys or by using your own encryption key. You can do this regardless of the form of server-side encryption that was used to encrypt the source, or even if the source object was not encrypted. For more information about server-side encryption, see Using Server-Side Encryption.
    
    A copy request might return an error when Amazon S3 receives the copy request or while Amazon S3 is copying the files. If the error occurs before the copy operation starts, you receive a standard Amazon S3 error. If the error occurs during the copy operation, the error response is embedded in the 200 OK response. This means that a 200 OK response can contain either a success or an error. Design your application to parse the contents of the response and handle it appropriately.
    
    If the copy is successful, you receive a response with information about the copied object.
    
    If the request is an HTTP 1.1 request, the response is chunk encoded. If it were not, it would not contain the content-length, and you would need to read the entire body.
    
    Consider the following when using request headers:
    - Consideration 1 – If both the x-amz-copy-source-if-match and x-amz-copy-source-if-unmodified-since headers are present in the request and evaluate as follows, Amazon S3 returns 200 OK and copies the data:
      
      x-amz-copy-source-if-match condition evaluates to true
      
      x-amz-copy-source-if-unmodified-since condition evaluates to false
    - Consideration 2 – If both of the x-amz-copy-source-if-none-match and x-amz-copy-source-if-modified-since headers are present in the request and evaluate as follows, Amazon S3 returns the 412 Precondition Failed response code:
      
      x-amz-copy-source-if-none-match condition evaluates to false
      
      x-amz-copy-source-if-modified-since condition evaluates to true
    The copy request charge is based on the storage class and Region you specify for the destination object. For pricing information, see Amazon S3 Pricing.
    
    Following are other considerations when using CopyObject:
    Versioning
    
    By default, x-amz-copy-source identifies the current version of an object to copy. (If the current version is a delete marker, Amazon S3 behaves as if the object was deleted.) To copy a different version, use the versionId subresource.
    
    If you enable versioning on the target bucket, Amazon S3 generates a unique version ID for the object being copied. This version ID is different from the version ID of the source object. Amazon S3 returns the version ID of the copied object in the x-amz-version-id response header in the response.
    
    If you do not enable versioning or suspend it on the target bucket, the version ID that Amazon S3 generates is always null.
    
    If the source object's storage class is GLACIER, you must restore a copy of this object before you can use it as a source object for the copy operation. For more information, see .
    
    Access Permissions
    
    When copying an object, you can optionally specify the accounts or groups that should be granted specific permissions on the new object. There are two ways to grant the permissions using the request headers:
    
    Specify a canned ACL with the x-amz-acl request header. For more information, see Canned ACL.
    
    Specify access permissions explicitly with the x-amz-grant-read, x-amz-grant-read-acp, x-amz-grant-write-acp, and x-amz-grant-full-control headers. These parameters map to the set of permissions that Amazon S3 supports in an ACL. For more information, see Access Control List (ACL) Overview.
    
    You can use either a canned ACL or specify access permissions explicitly. You cannot do both.
    
    Server-Side- Encryption-Specific Request Headers
    
    To encrypt the target object, you must provide the appropriate encryption-related request headers. The one you use depends on whether you want to use AWS managed encryption keys or provide your own encryption key.
    
    To encrypt the target object using server-side encryption with an AWS managed encryption key, provide the following request headers, as appropriate.
    
    x-amz-server-side-encryption
    
    x-amz-server-side-encryption-aws-kms-key-id
    
    x-amz-server-side-encryption-context
    
    If you specify x-amz-server-side-encryption:aws:kms, but don't provide x-amz-server-side-encryption-aws-kms-key-id, Amazon S3 uses the AWS managed CMK in AWS KMS to protect the data. If you want to use a customer managed AWS KMS CMK, you must provide the x-amz-server-side-encryption-aws-kms-key-id of the symmetric customer managed CMK. Amazon S3 only supports symmetric CMKs and not asymmetric CMKs. For more information, see Using Symmetric and Asymmetric Keys in the AWS Key Management Service Developer Guide.
    
    All GET and PUT requests for an object protected by AWS KMS fail if you don't make them with SSL or by using SigV4.
    
    For more information about server-side encryption with CMKs stored in AWS KMS (SSE-KMS), see Protecting Data Using Server-Side Encryption with CMKs stored in KMS.
    
    To encrypt the target object using server-side encryption with an encryption key that you provide, use the following headers.
    
    x-amz-server-side-encryption-customer-algorithm
    
    x-amz-server-side-encryption-customer-key
    
    x-amz-server-side-encryption-customer-key-MD5
    
    If the source object is encrypted using server-side encryption with customer-provided encryption keys, you must use the following headers.
    
    x-amz-copy-source-server-side-encryption-customer-algorithm
    
    x-amz-copy-source-server-side-encryption-customer-key
    
    x-amz-copy-source-server-side-encryption-customer-key-MD5
    
    For more information about server-side encryption with CMKs stored in AWS KMS (SSE-KMS), see Protecting Data Using Server-Side Encryption with CMKs stored in Amazon KMS.
    
    Access-Control-List (ACL)-Specific Request Headers
    
    You also can use the following access control–related headers with this operation. By default, all objects are private. Only the owner has full access control. When adding a new object, you can grant permissions to individual AWS accounts or to predefined groups defined by Amazon S3. These permissions are then added to the access control list (ACL) on the object. For more information, see Using ACLs. With this operation, you can grant access permissions using one of the following two methods:
    
    Specify a canned ACL (x-amz-acl) — Amazon S3 supports a set of predefined ACLs, known as canned ACLs. Each canned ACL has a predefined set of grantees and permissions. For more information, see Canned ACL.
    
    Specify access permissions explicitly — To explicitly grant access permissions to specific AWS accounts or groups, use the following headers. Each header maps to specific permissions that Amazon S3 supports in an ACL. For more information, see Access Control List (ACL) Overview. In the header, you specify a list of grantees who get the specific permission. To grant permissions explicitly, use:
    
    x-amz-grant-read
    
    x-amz-grant-write
    
    x-amz-grant-read-acp
    
    x-amz-grant-write-acp
    
    x-amz-grant-full-control
    
    You specify each grantee as a type=value pair, where the type is one of the following:
    
    emailAddress – if the value specified is the email address of an AWS account
    
    id – if the value specified is the canonical user ID of an AWS account
    
    uri – if you are granting permissions to a predefined group
    
    For example, the following x-amz-grant-read header grants the AWS accounts identified by email addresses permissions to read object data and its metadata:
    
    x-amz-grant-read: emailAddress="[email protected]", emailAddress="[email protected]"
    The following operations are related to CopyObject:
    - PutObject
    - GetObject
    For more information, see Copying Objects.
    Parameters:
    
    copyObjectRequest -
    
    Returns:
    A Java Future containing the result of the CopyObject operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    ObjectNotInActiveTierErrorException The source object of the COPY operation is not in the active tier and is only stored in Amazon S3 Glacier.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - copyObject
```
default CompletableFuture<CopyObjectResponse> copyObject(Consumer<CopyObjectRequest.Builder> copyObjectRequest)
```
    Creates a copy of an object that is already stored in Amazon S3.
    
    You can store individual objects of up to 5 TB in Amazon S3. You create a copy of your object up to 5 GB in size in a single atomic operation using this API. However, for copying an object greater than 5 GB, you must use the multipart upload Upload Part - Copy API. For more information, see Copy Object Using the REST Multipart Upload API.
    
    When copying an object, you can preserve all metadata (default) or specify new metadata. However, the ACL is not preserved and is set to private for the user making the request. To override the default ACL setting, specify a new ACL when generating a copy request. For more information, see Using ACLs.
    
    Amazon S3 transfer acceleration does not support cross-region copies. If you request a cross-region copy using a transfer acceleration endpoint, you get a 400 Bad Request error. For more information about transfer acceleration, see Transfer Acceleration.
    
    All copy requests must be authenticated. Additionally, you must have read access to the source object and write access to the destination bucket. For more information, see REST Authentication. Both the Region that you want to copy the object from and the Region that you want to copy the object to must be enabled for your account.
    
    To only copy an object under certain conditions, such as whether the Etag matches or whether the object was modified before or after a specified date, use the request parameters x-amz-copy-source-if-match, x-amz-copy-source-if-none-match, x-amz-copy-source-if-unmodified-since, or x-amz-copy-source-if-modified-since.
    
    All headers with the x-amz- prefix, including x-amz-copy-source, must be signed.
    
    You can use this operation to change the storage class of an object that is already stored in Amazon S3 using the StorageClass parameter. For more information, see Storage Classes.
    
    The source object that you are copying can be encrypted or unencrypted. If the source object is encrypted, it can be encrypted by server-side encryption using AWS managed encryption keys or by using a customer-provided encryption key. When copying an object, you can request that Amazon S3 encrypt the target object by using either the AWS managed encryption keys or by using your own encryption key. You can do this regardless of the form of server-side encryption that was used to encrypt the source, or even if the source object was not encrypted. For more information about server-side encryption, see Using Server-Side Encryption.
    
    A copy request might return an error when Amazon S3 receives the copy request or while Amazon S3 is copying the files. If the error occurs before the copy operation starts, you receive a standard Amazon S3 error. If the error occurs during the copy operation, the error response is embedded in the 200 OK response. This means that a 200 OK response can contain either a success or an error. Design your application to parse the contents of the response and handle it appropriately.
    
    If the copy is successful, you receive a response with information about the copied object.
    
    If the request is an HTTP 1.1 request, the response is chunk encoded. If it were not, it would not contain the content-length, and you would need to read the entire body.
    
    Consider the following when using request headers:
    - Consideration 1 – If both the x-amz-copy-source-if-match and x-amz-copy-source-if-unmodified-since headers are present in the request and evaluate as follows, Amazon S3 returns 200 OK and copies the data:
      
      x-amz-copy-source-if-match condition evaluates to true
      
      x-amz-copy-source-if-unmodified-since condition evaluates to false
    - Consideration 2 – If both of the x-amz-copy-source-if-none-match and x-amz-copy-source-if-modified-since headers are present in the request and evaluate as follows, Amazon S3 returns the 412 Precondition Failed response code:
      
      x-amz-copy-source-if-none-match condition evaluates to false
      
      x-amz-copy-source-if-modified-since condition evaluates to true
    The copy request charge is based on the storage class and Region you specify for the destination object. For pricing information, see Amazon S3 Pricing.
    
    Following are other considerations when using CopyObject:
    Versioning
    
    By default, x-amz-copy-source identifies the current version of an object to copy. (If the current version is a delete marker, Amazon S3 behaves as if the object was deleted.) To copy a different version, use the versionId subresource.
    
    If you enable versioning on the target bucket, Amazon S3 generates a unique version ID for the object being copied. This version ID is different from the version ID of the source object. Amazon S3 returns the version ID of the copied object in the x-amz-version-id response header in the response.
    
    If you do not enable versioning or suspend it on the target bucket, the version ID that Amazon S3 generates is always null.
    
    If the source object's storage class is GLACIER, you must restore a copy of this object before you can use it as a source object for the copy operation. For more information, see .
    
    Access Permissions
    
    When copying an object, you can optionally specify the accounts or groups that should be granted specific permissions on the new object. There are two ways to grant the permissions using the request headers:
    
    Specify a canned ACL with the x-amz-acl request header. For more information, see Canned ACL.
    
    Specify access permissions explicitly with the x-amz-grant-read, x-amz-grant-read-acp, x-amz-grant-write-acp, and x-amz-grant-full-control headers. These parameters map to the set of permissions that Amazon S3 supports in an ACL. For more information, see Access Control List (ACL) Overview.
    
    You can use either a canned ACL or specify access permissions explicitly. You cannot do both.
    
    Server-Side- Encryption-Specific Request Headers
    
    To encrypt the target object, you must provide the appropriate encryption-related request headers. The one you use depends on whether you want to use AWS managed encryption keys or provide your own encryption key.
    
    To encrypt the target object using server-side encryption with an AWS managed encryption key, provide the following request headers, as appropriate.
    
    x-amz-server-side-encryption
    
    x-amz-server-side-encryption-aws-kms-key-id
    
    x-amz-server-side-encryption-context
    
    If you specify x-amz-server-side-encryption:aws:kms, but don't provide x-amz-server-side-encryption-aws-kms-key-id, Amazon S3 uses the AWS managed CMK in AWS KMS to protect the data. If you want to use a customer managed AWS KMS CMK, you must provide the x-amz-server-side-encryption-aws-kms-key-id of the symmetric customer managed CMK. Amazon S3 only supports symmetric CMKs and not asymmetric CMKs. For more information, see Using Symmetric and Asymmetric Keys in the AWS Key Management Service Developer Guide.
    
    All GET and PUT requests for an object protected by AWS KMS fail if you don't make them with SSL or by using SigV4.
    
    For more information about server-side encryption with CMKs stored in AWS KMS (SSE-KMS), see Protecting Data Using Server-Side Encryption with CMKs stored in KMS.
    
    To encrypt the target object using server-side encryption with an encryption key that you provide, use the following headers.
    
    x-amz-server-side-encryption-customer-algorithm
    
    x-amz-server-side-encryption-customer-key
    
    x-amz-server-side-encryption-customer-key-MD5
    
    If the source object is encrypted using server-side encryption with customer-provided encryption keys, you must use the following headers.
    
    x-amz-copy-source-server-side-encryption-customer-algorithm
    
    x-amz-copy-source-server-side-encryption-customer-key
    
    x-amz-copy-source-server-side-encryption-customer-key-MD5
    
    For more information about server-side encryption with CMKs stored in AWS KMS (SSE-KMS), see Protecting Data Using Server-Side Encryption with CMKs stored in Amazon KMS.
    
    Access-Control-List (ACL)-Specific Request Headers
    
    You also can use the following access control–related headers with this operation. By default, all objects are private. Only the owner has full access control. When adding a new object, you can grant permissions to individual AWS accounts or to predefined groups defined by Amazon S3. These permissions are then added to the access control list (ACL) on the object. For more information, see Using ACLs. With this operation, you can grant access permissions using one of the following two methods:
    
    Specify a canned ACL (x-amz-acl) — Amazon S3 supports a set of predefined ACLs, known as canned ACLs. Each canned ACL has a predefined set of grantees and permissions. For more information, see Canned ACL.
    
    Specify access permissions explicitly — To explicitly grant access permissions to specific AWS accounts or groups, use the following headers. Each header maps to specific permissions that Amazon S3 supports in an ACL. For more information, see Access Control List (ACL) Overview. In the header, you specify a list of grantees who get the specific permission. To grant permissions explicitly, use:
    
    x-amz-grant-read
    
    x-amz-grant-write
    
    x-amz-grant-read-acp
    
    x-amz-grant-write-acp
    
    x-amz-grant-full-control
    
    You specify each grantee as a type=value pair, where the type is one of the following:
    
    emailAddress – if the value specified is the email address of an AWS account
    
    id – if the value specified is the canonical user ID of an AWS account
    
    uri – if you are granting permissions to a predefined group
    
    For example, the following x-amz-grant-read header grants the AWS accounts identified by email addresses permissions to read object data and its metadata:
    
    x-amz-grant-read: emailAddress="[email protected]", emailAddress="[email protected]"
    The following operations are related to CopyObject:
    - PutObject
    - GetObject
    For more information, see Copying Objects.
    
    This is a convenience which creates an instance of the CopyObjectRequest.Builder avoiding the need to create one manually via CopyObjectRequest.builder()
    Parameters:
    
    copyObjectRequest - A Consumer that will call methods on CopyObjectRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the CopyObject operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    ObjectNotInActiveTierErrorException The source object of the COPY operation is not in the active tier and is only stored in Amazon S3 Glacier.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - createBucket
```
default CompletableFuture<CreateBucketResponse> createBucket(CreateBucketRequest createBucketRequest)
```
    Creates a new bucket. To create a bucket, you must register with Amazon S3 and have a valid AWS Access Key ID to authenticate requests. Anonymous requests are never allowed to create buckets. By creating the bucket, you become the bucket owner.
    
    Not every string is an acceptable bucket name. For information on bucket naming restrictions, see Working with Amazon S3 Buckets.
    
    By default, the bucket is created in the US East (N. Virginia) Region. You can optionally specify a Region in the request body. You might choose a Region to optimize latency, minimize costs, or address regulatory requirements. For example, if you reside in Europe, you will probably find it advantageous to create buckets in the EU (Ireland) Region. For more information, see How to Select a Region for Your Buckets.
    
    If you send your create bucket request to the s3.amazonaws.com endpoint, the request goes to the us-east-1 Region. Accordingly, the signature calculations in Signature Version 4 must use us-east-1 as the Region, even if the location constraint in the request specifies another Region where the bucket is to be created. If you create a bucket in a Region other than US East (N. Virginia), your application must be able to handle 307 redirect. For more information, see Virtual Hosting of Buckets.
    
    When creating a bucket using this operation, you can optionally specify the accounts or groups that should be granted specific permissions on the bucket. There are two ways to grant the appropriate permissions using the request headers.
    - Specify a canned ACL using the x-amz-acl request header. Amazon S3 supports a set of predefined ACLs, known as canned ACLs. Each canned ACL has a predefined set of grantees and permissions. For more information, see Canned ACL.
    - Specify access permissions explicitly using the x-amz-grant-read, x-amz-grant-write, x-amz-grant-read-acp, x-amz-grant-write-acp, and x-amz-grant-full-control headers. These headers map to the set of permissions Amazon S3 supports in an ACL. For more information, see Access Control List (ACL) Overview.
      
      You specify each grantee as a type=value pair, where the type is one of the following:
      
      emailAddress – if the value specified is the email address of an AWS account
      
      id – if the value specified is the canonical user ID of an AWS account
      
      uri – if you are granting permissions to a predefined group
      
      For example, the following x-amz-grant-read header grants the AWS accounts identified by email addresses permissions to read object data and its metadata:
      
      x-amz-grant-read: emailAddress="[email protected]", emailAddress="[email protected]"
    You can use either a canned ACL or specify access permissions explicitly. You cannot do both.
    
    The following operations are related to CreateBucket:
    - PutObject
    - DeleteBucket
    Parameters:
    
    createBucketRequest -
    
    Returns:
    A Java Future containing the result of the CreateBucket operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    BucketAlreadyExistsException The requested bucket name is not available. The bucket namespace is shared by all users of the system. Please select a different name and try again.
    
    BucketAlreadyOwnedByYouException The bucket you tried to create already exists, and you own it. Amazon S3 returns this error in all AWS Regions except in the North Virginia Region. For legacy compatibility, if you re-create an existing bucket that you already own in the North Virginia Region, Amazon S3 returns 200 OK and resets the bucket access control lists (ACLs).
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - createBucket
```
default CompletableFuture<CreateBucketResponse> createBucket(Consumer<CreateBucketRequest.Builder> createBucketRequest)
```
    Creates a new bucket. To create a bucket, you must register with Amazon S3 and have a valid AWS Access Key ID to authenticate requests. Anonymous requests are never allowed to create buckets. By creating the bucket, you become the bucket owner.
    
    Not every string is an acceptable bucket name. For information on bucket naming restrictions, see Working with Amazon S3 Buckets.
    
    By default, the bucket is created in the US East (N. Virginia) Region. You can optionally specify a Region in the request body. You might choose a Region to optimize latency, minimize costs, or address regulatory requirements. For example, if you reside in Europe, you will probably find it advantageous to create buckets in the EU (Ireland) Region. For more information, see How to Select a Region for Your Buckets.
    
    If you send your create bucket request to the s3.amazonaws.com endpoint, the request goes to the us-east-1 Region. Accordingly, the signature calculations in Signature Version 4 must use us-east-1 as the Region, even if the location constraint in the request specifies another Region where the bucket is to be created. If you create a bucket in a Region other than US East (N. Virginia), your application must be able to handle 307 redirect. For more information, see Virtual Hosting of Buckets.
    
    When creating a bucket using this operation, you can optionally specify the accounts or groups that should be granted specific permissions on the bucket. There are two ways to grant the appropriate permissions using the request headers.
    - Specify a canned ACL using the x-amz-acl request header. Amazon S3 supports a set of predefined ACLs, known as canned ACLs. Each canned ACL has a predefined set of grantees and permissions. For more information, see Canned ACL.
    - Specify access permissions explicitly using the x-amz-grant-read, x-amz-grant-write, x-amz-grant-read-acp, x-amz-grant-write-acp, and x-amz-grant-full-control headers. These headers map to the set of permissions Amazon S3 supports in an ACL. For more information, see Access Control List (ACL) Overview.
      
      You specify each grantee as a type=value pair, where the type is one of the following:
      
      emailAddress – if the value specified is the email address of an AWS account
      
      id – if the value specified is the canonical user ID of an AWS account
      
      uri – if you are granting permissions to a predefined group
      
      For example, the following x-amz-grant-read header grants the AWS accounts identified by email addresses permissions to read object data and its metadata:
      
      x-amz-grant-read: emailAddress="[email protected]", emailAddress="[email protected]"
    You can use either a canned ACL or specify access permissions explicitly. You cannot do both.
    
    The following operations are related to CreateBucket:
    - PutObject
    - DeleteBucket
    This is a convenience which creates an instance of the CreateBucketRequest.Builder avoiding the need to create one manually via CreateBucketRequest.builder()
    Parameters:
    
    createBucketRequest - A Consumer that will call methods on CreateBucketRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the CreateBucket operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    BucketAlreadyExistsException The requested bucket name is not available. The bucket namespace is shared by all users of the system. Please select a different name and try again.
    
    BucketAlreadyOwnedByYouException The bucket you tried to create already exists, and you own it. Amazon S3 returns this error in all AWS Regions except in the North Virginia Region. For legacy compatibility, if you re-create an existing bucket that you already own in the North Virginia Region, Amazon S3 returns 200 OK and resets the bucket access control lists (ACLs).
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - createMultipartUpload
```
default CompletableFuture<CreateMultipartUploadResponse> createMultipartUpload(CreateMultipartUploadRequest createMultipartUploadRequest)
```
    This operation initiates a multipart upload and returns an upload ID. This upload ID is used to associate all of the parts in the specific multipart upload. You specify this upload ID in each of your subsequent upload part requests (see UploadPart). You also include this upload ID in the final request to either complete or abort the multipart upload request.
    
    For more information about multipart uploads, see Multipart Upload Overview.
    
    If you have configured a lifecycle rule to abort incomplete multipart uploads, the upload must complete within the number of days specified in the bucket lifecycle configuration. Otherwise, the incomplete multipart upload becomes eligible for an abort operation and Amazon S3 aborts the multipart upload. For more information, see Aborting Incomplete Multipart Uploads Using a Bucket Lifecycle Policy.
    
    For information about the permissions required to use the multipart upload API, see Multipart Upload API and Permissions.
    
    For request signing, multipart upload is just a series of regular requests. You initiate a multipart upload, send one or more requests to upload parts, and then complete the multipart upload process. You sign each request individually. There is nothing special about signing multipart upload requests. For more information about signing, see Authenticating Requests (AWS Signature Version 4).
    
    After you initiate a multipart upload and upload one or more parts, to stop being charged for storing the uploaded parts, you must either complete or abort the multipart upload. Amazon S3 frees up the space used to store the parts and stop charging you for storing them only after you either complete or abort a multipart upload.
    
    You can optionally request server-side encryption. For server-side encryption, Amazon S3 encrypts your data as it writes it to disks in its data centers and decrypts it when you access it. You can provide your own encryption key, or use AWS Key Management Service (AWS KMS) customer master keys (CMKs) or Amazon S3-managed encryption keys. If you choose to provide your own encryption key, the request headers you provide in UploadPart) and UploadPartCopy) requests must match the headers you used in the request to initiate the upload by using CreateMultipartUpload.
    
    To perform a multipart upload with encryption using an AWS KMS CMK, the requester must have permission to the kms:Encrypt, kms:Decrypt, kms:ReEncrypt*, kms:GenerateDataKey*, and kms:DescribeKey actions on the key. These permissions are required because Amazon S3 must decrypt and read data from the encrypted file parts before it completes the multipart upload.
    
    If your AWS Identity and Access Management (IAM) user or role is in the same AWS account as the AWS KMS CMK, then you must have these permissions on the key policy. If your IAM user or role belongs to a different account than the key, then you must have the permissions on both the key policy and your IAM user or role.
    
    For more information, see Protecting Data Using Server-Side Encryption.
    Access Permissions
    
    When copying an object, you can optionally specify the accounts or groups that should be granted specific permissions on the new object. There are two ways to grant the permissions using the request headers:
    
    Specify a canned ACL with the x-amz-acl request header. For more information, see Canned ACL.
    
    Specify access permissions explicitly with the x-amz-grant-read, x-amz-grant-read-acp, x-amz-grant-write-acp, and x-amz-grant-full-control headers. These parameters map to the set of permissions that Amazon S3 supports in an ACL. For more information, see Access Control List (ACL) Overview.
    
    You can use either a canned ACL or specify access permissions explicitly. You cannot do both.
    
    Server-Side- Encryption-Specific Request Headers
    
    You can optionally tell Amazon S3 to encrypt data at rest using server-side encryption. Server-side encryption is for data encryption at rest. Amazon S3 encrypts your data as it writes it to disks in its data centers and decrypts it when you access it. The option you use depends on whether you want to use AWS managed encryption keys or provide your own encryption key.
    
    Use encryption keys managed by Amazon S3 or customer master keys (CMKs) stored in AWS Key Management Service (AWS KMS) – If you want AWS to manage the keys used to encrypt data, specify the following headers in the request.
    
    x-amz-server-side-encryption
    
    x-amz-server-side-encryption-aws-kms-key-id
    
    x-amz-server-side-encryption-context
    
    If you specify x-amz-server-side-encryption:aws:kms, but don't provide x-amz-server-side-encryption-aws-kms-key-id, Amazon S3 uses the AWS managed CMK in AWS KMS to protect the data.
    
    All GET and PUT requests for an object protected by AWS KMS fail if you don't make them with SSL or by using SigV4.
    
    For more information about server-side encryption with CMKs stored in AWS KMS (SSE-KMS), see Protecting Data Using Server-Side Encryption with CMKs stored in AWS KMS.
    
    Use customer-provided encryption keys – If you want to manage your own encryption keys, provide all the following headers in the request.
    
    x-amz-server-side-encryption-customer-algorithm
    
    x-amz-server-side-encryption-customer-key
    
    x-amz-server-side-encryption-customer-key-MD5
    
    For more information about server-side encryption with CMKs stored in AWS KMS (SSE-KMS), see Protecting Data Using Server-Side Encryption with CMKs stored in AWS KMS.
    
    Access-Control-List (ACL)-Specific Request Headers
    
    You also can use the following access control–related headers with this operation. By default, all objects are private. Only the owner has full access control. When adding a new object, you can grant permissions to individual AWS accounts or to predefined groups defined by Amazon S3. These permissions are then added to the access control list (ACL) on the object. For more information, see Using ACLs. With this operation, you can grant access permissions using one of the following two methods:
    
    Specify a canned ACL (x-amz-acl) — Amazon S3 supports a set of predefined ACLs, known as canned ACLs. Each canned ACL has a predefined set of grantees and permissions. For more information, see Canned ACL.
    
    Specify access permissions explicitly — To explicitly grant access permissions to specific AWS accounts or groups, use the following headers. Each header maps to specific permissions that Amazon S3 supports in an ACL. For more information, see Access Control List (ACL) Overview. In the header, you specify a list of grantees who get the specific permission. To grant permissions explicitly, use:
    
    x-amz-grant-read
    
    x-amz-grant-write
    
    x-amz-grant-read-acp
    
    x-amz-grant-write-acp
    
    x-amz-grant-full-control
    
    You specify each grantee as a type=value pair, where the type is one of the following:
    
    emailAddress – if the value specified is the email address of an AWS account
    
    id – if the value specified is the canonical user ID of an AWS account
    
    uri – if you are granting permissions to a predefined group
    
    For example, the following x-amz-grant-read header grants the AWS accounts identified by email addresses permissions to read object data and its metadata:
    
    x-amz-grant-read: emailAddress="[email protected]", emailAddress="[email protected]"
    The following operations are related to CreateMultipartUpload:
    Parameters:
    
    createMultipartUploadRequest -
    
    Returns:
    A Java Future containing the result of the CreateMultipartUpload operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - createMultipartUpload
```
default CompletableFuture<CreateMultipartUploadResponse> createMultipartUpload(Consumer<CreateMultipartUploadRequest.Builder> createMultipartUploadRequest)
```
    This operation initiates a multipart upload and returns an upload ID. This upload ID is used to associate all of the parts in the specific multipart upload. You specify this upload ID in each of your subsequent upload part requests (see UploadPart). You also include this upload ID in the final request to either complete or abort the multipart upload request.
    
    For more information about multipart uploads, see Multipart Upload Overview.
    
    If you have configured a lifecycle rule to abort incomplete multipart uploads, the upload must complete within the number of days specified in the bucket lifecycle configuration. Otherwise, the incomplete multipart upload becomes eligible for an abort operation and Amazon S3 aborts the multipart upload. For more information, see Aborting Incomplete Multipart Uploads Using a Bucket Lifecycle Policy.
    
    For information about the permissions required to use the multipart upload API, see Multipart Upload API and Permissions.
    
    For request signing, multipart upload is just a series of regular requests. You initiate a multipart upload, send one or more requests to upload parts, and then complete the multipart upload process. You sign each request individually. There is nothing special about signing multipart upload requests. For more information about signing, see Authenticating Requests (AWS Signature Version 4).
    
    After you initiate a multipart upload and upload one or more parts, to stop being charged for storing the uploaded parts, you must either complete or abort the multipart upload. Amazon S3 frees up the space used to store the parts and stop charging you for storing them only after you either complete or abort a multipart upload.
    
    You can optionally request server-side encryption. For server-side encryption, Amazon S3 encrypts your data as it writes it to disks in its data centers and decrypts it when you access it. You can provide your own encryption key, or use AWS Key Management Service (AWS KMS) customer master keys (CMKs) or Amazon S3-managed encryption keys. If you choose to provide your own encryption key, the request headers you provide in UploadPart) and UploadPartCopy) requests must match the headers you used in the request to initiate the upload by using CreateMultipartUpload.
    
    To perform a multipart upload with encryption using an AWS KMS CMK, the requester must have permission to the kms:Encrypt, kms:Decrypt, kms:ReEncrypt*, kms:GenerateDataKey*, and kms:DescribeKey actions on the key. These permissions are required because Amazon S3 must decrypt and read data from the encrypted file parts before it completes the multipart upload.
    
    If your AWS Identity and Access Management (IAM) user or role is in the same AWS account as the AWS KMS CMK, then you must have these permissions on the key policy. If your IAM user or role belongs to a different account than the key, then you must have the permissions on both the key policy and your IAM user or role.
    
    For more information, see Protecting Data Using Server-Side Encryption.
    Access Permissions
    
    When copying an object, you can optionally specify the accounts or groups that should be granted specific permissions on the new object. There are two ways to grant the permissions using the request headers:
    
    Specify a canned ACL with the x-amz-acl request header. For more information, see Canned ACL.
    
    Specify access permissions explicitly with the x-amz-grant-read, x-amz-grant-read-acp, x-amz-grant-write-acp, and x-amz-grant-full-control headers. These parameters map to the set of permissions that Amazon S3 supports in an ACL. For more information, see Access Control List (ACL) Overview.
    
    You can use either a canned ACL or specify access permissions explicitly. You cannot do both.
    
    Server-Side- Encryption-Specific Request Headers
    
    You can optionally tell Amazon S3 to encrypt data at rest using server-side encryption. Server-side encryption is for data encryption at rest. Amazon S3 encrypts your data as it writes it to disks in its data centers and decrypts it when you access it. The option you use depends on whether you want to use AWS managed encryption keys or provide your own encryption key.
    
    Use encryption keys managed by Amazon S3 or customer master keys (CMKs) stored in AWS Key Management Service (AWS KMS) – If you want AWS to manage the keys used to encrypt data, specify the following headers in the request.
    
    x-amz-server-side-encryption
    
    x-amz-server-side-encryption-aws-kms-key-id
    
    x-amz-server-side-encryption-context
    
    If you specify x-amz-server-side-encryption:aws:kms, but don't provide x-amz-server-side-encryption-aws-kms-key-id, Amazon S3 uses the AWS managed CMK in AWS KMS to protect the data.
    
    All GET and PUT requests for an object protected by AWS KMS fail if you don't make them with SSL or by using SigV4.
    
    For more information about server-side encryption with CMKs stored in AWS KMS (SSE-KMS), see Protecting Data Using Server-Side Encryption with CMKs stored in AWS KMS.
    
    Use customer-provided encryption keys – If you want to manage your own encryption keys, provide all the following headers in the request.
    
    x-amz-server-side-encryption-customer-algorithm
    
    x-amz-server-side-encryption-customer-key
    
    x-amz-server-side-encryption-customer-key-MD5
    
    For more information about server-side encryption with CMKs stored in AWS KMS (SSE-KMS), see Protecting Data Using Server-Side Encryption with CMKs stored in AWS KMS.
    
    Access-Control-List (ACL)-Specific Request Headers
    
    You also can use the following access control–related headers with this operation. By default, all objects are private. Only the owner has full access control. When adding a new object, you can grant permissions to individual AWS accounts or to predefined groups defined by Amazon S3. These permissions are then added to the access control list (ACL) on the object. For more information, see Using ACLs. With this operation, you can grant access permissions using one of the following two methods:
    
    Specify a canned ACL (x-amz-acl) — Amazon S3 supports a set of predefined ACLs, known as canned ACLs. Each canned ACL has a predefined set of grantees and permissions. For more information, see Canned ACL.
    
    Specify access permissions explicitly — To explicitly grant access permissions to specific AWS accounts or groups, use the following headers. Each header maps to specific permissions that Amazon S3 supports in an ACL. For more information, see Access Control List (ACL) Overview. In the header, you specify a list of grantees who get the specific permission. To grant permissions explicitly, use:
    
    x-amz-grant-read
    
    x-amz-grant-write
    
    x-amz-grant-read-acp
    
    x-amz-grant-write-acp
    
    x-amz-grant-full-control
    
    You specify each grantee as a type=value pair, where the type is one of the following:
    
    emailAddress – if the value specified is the email address of an AWS account
    
    id – if the value specified is the canonical user ID of an AWS account
    
    uri – if you are granting permissions to a predefined group
    
    For example, the following x-amz-grant-read header grants the AWS accounts identified by email addresses permissions to read object data and its metadata:
    
    x-amz-grant-read: emailAddress="[email protected]", emailAddress="[email protected]"
    The following operations are related to CreateMultipartUpload:
    This is a convenience which creates an instance of the CreateMultipartUploadRequest.Builder avoiding the need to create one manually via CreateMultipartUploadRequest.builder()
    Parameters:
    
    createMultipartUploadRequest - A Consumer that will call methods on CreateMultipartUploadRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the CreateMultipartUpload operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - deleteBucket
```
default CompletableFuture<DeleteBucketResponse> deleteBucket(DeleteBucketRequest deleteBucketRequest)
```
    Deletes the bucket. All objects (including all object versions and delete markers) in the bucket must be deleted before the bucket itself can be deleted.
    
    Related Resources
    Parameters:
    
    deleteBucketRequest -
    
    Returns:
    A Java Future containing the result of the DeleteBucket operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - deleteBucket
```
default CompletableFuture<DeleteBucketResponse> deleteBucket(Consumer<DeleteBucketRequest.Builder> deleteBucketRequest)
```
    Deletes the bucket. All objects (including all object versions and delete markers) in the bucket must be deleted before the bucket itself can be deleted.
    
    Related Resources
    This is a convenience which creates an instance of the DeleteBucketRequest.Builder avoiding the need to create one manually via DeleteBucketRequest.builder()
    Parameters:
    
    deleteBucketRequest - A Consumer that will call methods on DeleteBucketRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the DeleteBucket operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - deleteBucketAnalyticsConfiguration
```
default CompletableFuture<DeleteBucketAnalyticsConfigurationResponse> deleteBucketAnalyticsConfiguration(DeleteBucketAnalyticsConfigurationRequest deleteBucketAnalyticsConfigurationRequest)
```
    Deletes an analytics configuration for the bucket (specified by the analytics configuration ID).
    
    To use this operation, you must have permissions to perform the s3:PutAnalyticsConfiguration action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.
    
    For information about the Amazon S3 analytics feature, see Amazon S3 Analytics – Storage Class Analysis.
    
    The following operations are related to DeleteBucketAnalyticsConfiguration:
    Parameters:
    
    deleteBucketAnalyticsConfigurationRequest -
    
    Returns:
    A Java Future containing the result of the DeleteBucketAnalyticsConfiguration operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - deleteBucketAnalyticsConfiguration
```
default CompletableFuture<DeleteBucketAnalyticsConfigurationResponse> deleteBucketAnalyticsConfiguration(Consumer<DeleteBucketAnalyticsConfigurationRequest.Builder> deleteBucketAnalyticsConfigurationRequest)
```
    Deletes an analytics configuration for the bucket (specified by the analytics configuration ID).
    
    To use this operation, you must have permissions to perform the s3:PutAnalyticsConfiguration action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.
    
    For information about the Amazon S3 analytics feature, see Amazon S3 Analytics – Storage Class Analysis.
    
    The following operations are related to DeleteBucketAnalyticsConfiguration:
    This is a convenience which creates an instance of the DeleteBucketAnalyticsConfigurationRequest.Builder avoiding the need to create one manually via DeleteBucketAnalyticsConfigurationRequest.builder()
    Parameters:
    
    deleteBucketAnalyticsConfigurationRequest - A Consumer that will call methods on DeleteBucketAnalyticsConfigurationRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the DeleteBucketAnalyticsConfiguration operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - deleteBucketCors
```
default CompletableFuture<DeleteBucketCorsResponse> deleteBucketCors(DeleteBucketCorsRequest deleteBucketCorsRequest)
```
    Deletes the cors configuration information set for the bucket.
    
    To use this operation, you must have permission to perform the s3:PutBucketCORS action. The bucket owner has this permission by default and can grant this permission to others.
    
    For information about cors, see Enabling Cross-Origin Resource Sharing in the Amazon Simple Storage Service Developer Guide.
    
    Related Resources:
    - RESTOPTIONSobject
    Parameters:
    
    deleteBucketCorsRequest -
    
    Returns:
    A Java Future containing the result of the DeleteBucketCors operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - deleteBucketCors
```
default CompletableFuture<DeleteBucketCorsResponse> deleteBucketCors(Consumer<DeleteBucketCorsRequest.Builder> deleteBucketCorsRequest)
```
    Deletes the cors configuration information set for the bucket.
    
    To use this operation, you must have permission to perform the s3:PutBucketCORS action. The bucket owner has this permission by default and can grant this permission to others.
    
    For information about cors, see Enabling Cross-Origin Resource Sharing in the Amazon Simple Storage Service Developer Guide.
    
    Related Resources:
    - RESTOPTIONSobject
    This is a convenience which creates an instance of the DeleteBucketCorsRequest.Builder avoiding the need to create one manually via DeleteBucketCorsRequest.builder()
    Parameters:
    
    deleteBucketCorsRequest - A Consumer that will call methods on DeleteBucketCorsRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the DeleteBucketCors operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - deleteBucketEncryption
```
default CompletableFuture<DeleteBucketEncryptionResponse> deleteBucketEncryption(DeleteBucketEncryptionRequest deleteBucketEncryptionRequest)
```
    This implementation of the DELETE operation removes default encryption from the bucket. For information about the Amazon S3 default encryption feature, see Amazon S3 Default Bucket Encryption in the Amazon Simple Storage Service Developer Guide.
    
    To use this operation, you must have permissions to perform the s3:PutEncryptionConfiguration action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to your Amazon S3 Resources in the Amazon Simple Storage Service Developer Guide.
    
    Related Resources
    - PutBucketEncryption
    - GetBucketEncryption
    Parameters:
    
    deleteBucketEncryptionRequest -
    
    Returns:
    A Java Future containing the result of the DeleteBucketEncryption operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - deleteBucketEncryption
```
default CompletableFuture<DeleteBucketEncryptionResponse> deleteBucketEncryption(Consumer<DeleteBucketEncryptionRequest.Builder> deleteBucketEncryptionRequest)
```
    This implementation of the DELETE operation removes default encryption from the bucket. For information about the Amazon S3 default encryption feature, see Amazon S3 Default Bucket Encryption in the Amazon Simple Storage Service Developer Guide.
    
    To use this operation, you must have permissions to perform the s3:PutEncryptionConfiguration action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to your Amazon S3 Resources in the Amazon Simple Storage Service Developer Guide.
    
    Related Resources
    - PutBucketEncryption
    - GetBucketEncryption
    This is a convenience which creates an instance of the DeleteBucketEncryptionRequest.Builder avoiding the need to create one manually via DeleteBucketEncryptionRequest.builder()
    Parameters:
    
    deleteBucketEncryptionRequest - A Consumer that will call methods on DeleteBucketEncryptionRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the DeleteBucketEncryption operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - deleteBucketInventoryConfiguration
```
default CompletableFuture<DeleteBucketInventoryConfigurationResponse> deleteBucketInventoryConfiguration(DeleteBucketInventoryConfigurationRequest deleteBucketInventoryConfigurationRequest)
```
    Deletes an inventory configuration (identified by the inventory ID) from the bucket.
    
    To use this operation, you must have permissions to perform the s3:PutInventoryConfiguration action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.
    
    For information about the Amazon S3 inventory feature, see Amazon S3 Inventory.
    
    Operations related to DeleteBucketInventoryConfiguration include:
    Parameters:
    
    deleteBucketInventoryConfigurationRequest -
    
    Returns:
    A Java Future containing the result of the DeleteBucketInventoryConfiguration operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - deleteBucketInventoryConfiguration
```
default CompletableFuture<DeleteBucketInventoryConfigurationResponse> deleteBucketInventoryConfiguration(Consumer<DeleteBucketInventoryConfigurationRequest.Builder> deleteBucketInventoryConfigurationRequest)
```
    Deletes an inventory configuration (identified by the inventory ID) from the bucket.
    
    To use this operation, you must have permissions to perform the s3:PutInventoryConfiguration action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.
    
    For information about the Amazon S3 inventory feature, see Amazon S3 Inventory.
    
    Operations related to DeleteBucketInventoryConfiguration include:
    This is a convenience which creates an instance of the DeleteBucketInventoryConfigurationRequest.Builder avoiding the need to create one manually via DeleteBucketInventoryConfigurationRequest.builder()
    Parameters:
    
    deleteBucketInventoryConfigurationRequest - A Consumer that will call methods on DeleteBucketInventoryConfigurationRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the DeleteBucketInventoryConfiguration operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - deleteBucketLifecycle
```
default CompletableFuture<DeleteBucketLifecycleResponse> deleteBucketLifecycle(DeleteBucketLifecycleRequest deleteBucketLifecycleRequest)
```
    Deletes the lifecycle configuration from the specified bucket. Amazon S3 removes all the lifecycle configuration rules in the lifecycle subresource associated with the bucket. Your objects never expire, and Amazon S3 no longer automatically deletes any objects on the basis of rules contained in the deleted lifecycle configuration.
    
    To use this operation, you must have permission to perform the s3:PutLifecycleConfiguration action. By default, the bucket owner has this permission and the bucket owner can grant this permission to others.
    
    There is usually some time lag before lifecycle configuration deletion is fully propagated to all the Amazon S3 systems.
    
    For more information about the object expiration, see Elements to Describe Lifecycle Actions.
    
    Related actions include:
    - PutBucketLifecycleConfiguration
    - GetBucketLifecycleConfiguration
    Parameters:
    
    deleteBucketLifecycleRequest -
    
    Returns:
    A Java Future containing the result of the DeleteBucketLifecycle operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - deleteBucketLifecycle
```
default CompletableFuture<DeleteBucketLifecycleResponse> deleteBucketLifecycle(Consumer<DeleteBucketLifecycleRequest.Builder> deleteBucketLifecycleRequest)
```
    Deletes the lifecycle configuration from the specified bucket. Amazon S3 removes all the lifecycle configuration rules in the lifecycle subresource associated with the bucket. Your objects never expire, and Amazon S3 no longer automatically deletes any objects on the basis of rules contained in the deleted lifecycle configuration.
    
    To use this operation, you must have permission to perform the s3:PutLifecycleConfiguration action. By default, the bucket owner has this permission and the bucket owner can grant this permission to others.
    
    There is usually some time lag before lifecycle configuration deletion is fully propagated to all the Amazon S3 systems.
    
    For more information about the object expiration, see Elements to Describe Lifecycle Actions.
    
    Related actions include:
    - PutBucketLifecycleConfiguration
    - GetBucketLifecycleConfiguration
    This is a convenience which creates an instance of the DeleteBucketLifecycleRequest.Builder avoiding the need to create one manually via DeleteBucketLifecycleRequest.builder()
    Parameters:
    
    deleteBucketLifecycleRequest - A Consumer that will call methods on DeleteBucketLifecycleRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the DeleteBucketLifecycle operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - deleteBucketMetricsConfiguration
```
default CompletableFuture<DeleteBucketMetricsConfigurationResponse> deleteBucketMetricsConfiguration(DeleteBucketMetricsConfigurationRequest deleteBucketMetricsConfigurationRequest)
```
    Deletes a metrics configuration for the Amazon CloudWatch request metrics (specified by the metrics configuration ID) from the bucket. Note that this doesn't include the daily storage metrics.
    
    To use this operation, you must have permissions to perform the s3:PutMetricsConfiguration action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.
    
    For information about CloudWatch request metrics for Amazon S3, see Monitoring Metrics with Amazon CloudWatch.
    
    The following operations are related to DeleteBucketMetricsConfiguration:
    Parameters:
    
    deleteBucketMetricsConfigurationRequest -
    
    Returns:
    A Java Future containing the result of the DeleteBucketMetricsConfiguration operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - deleteBucketMetricsConfiguration
```
default CompletableFuture<DeleteBucketMetricsConfigurationResponse> deleteBucketMetricsConfiguration(Consumer<DeleteBucketMetricsConfigurationRequest.Builder> deleteBucketMetricsConfigurationRequest)
```
    Deletes a metrics configuration for the Amazon CloudWatch request metrics (specified by the metrics configuration ID) from the bucket. Note that this doesn't include the daily storage metrics.
    
    To use this operation, you must have permissions to perform the s3:PutMetricsConfiguration action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.
    
    For information about CloudWatch request metrics for Amazon S3, see Monitoring Metrics with Amazon CloudWatch.
    
    The following operations are related to DeleteBucketMetricsConfiguration:
    This is a convenience which creates an instance of the DeleteBucketMetricsConfigurationRequest.Builder avoiding the need to create one manually via DeleteBucketMetricsConfigurationRequest.builder()
    Parameters:
    
    deleteBucketMetricsConfigurationRequest - A Consumer that will call methods on DeleteBucketMetricsConfigurationRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the DeleteBucketMetricsConfiguration operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - deleteBucketPolicy
```
default CompletableFuture<DeleteBucketPolicyResponse> deleteBucketPolicy(DeleteBucketPolicyRequest deleteBucketPolicyRequest)
```
    This implementation of the DELETE operation 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 AWS 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, 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.
    
    As a security precaution, the root user of the AWS account that owns a bucket can always use this operation, even if the policy explicitly denies the root user the ability to perform this action.
    
    For more information about bucket policies, see Using Bucket Policies and UserPolicies.
    
    The following operations are related to DeleteBucketPolicy
    - CreateBucket
    - DeleteObject
    Parameters:
    
    deleteBucketPolicyRequest -
    
    Returns:
    A Java Future containing the result of the DeleteBucketPolicy operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - deleteBucketPolicy
```
default CompletableFuture<DeleteBucketPolicyResponse> deleteBucketPolicy(Consumer<DeleteBucketPolicyRequest.Builder> deleteBucketPolicyRequest)
```
    This implementation of the DELETE operation 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 AWS 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, 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.
    
    As a security precaution, the root user of the AWS account that owns a bucket can always use this operation, even if the policy explicitly denies the root user the ability to perform this action.
    
    For more information about bucket policies, see Using Bucket Policies and UserPolicies.
    
    The following operations are related to DeleteBucketPolicy
    - CreateBucket
    - DeleteObject
    This is a convenience which creates an instance of the DeleteBucketPolicyRequest.Builder avoiding the need to create one manually via DeleteBucketPolicyRequest.builder()
    Parameters:
    
    deleteBucketPolicyRequest - A Consumer that will call methods on DeleteBucketPolicyRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the DeleteBucketPolicy operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - deleteBucketReplication
```
default CompletableFuture<DeleteBucketReplicationResponse> deleteBucketReplication(DeleteBucketReplicationRequest deleteBucketReplicationRequest)
```
    Deletes the replication configuration from the bucket.
    
    To use this operation, you must have permissions to perform the s3:PutReplicationConfiguration action. The bucket owner has these permissions by default and can grant it to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.
    
    It can take a while for the deletion of a replication configuration to fully propagate.
    
    For information about replication configuration, see Replication in the Amazon S3 Developer Guide.
    
    The following operations are related to DeleteBucketReplication:
    - PutBucketReplication
    - GetBucketReplication
    Parameters:
    
    deleteBucketReplicationRequest -
    
    Returns:
    A Java Future containing the result of the DeleteBucketReplication operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - deleteBucketReplication
```
default CompletableFuture<DeleteBucketReplicationResponse> deleteBucketReplication(Consumer<DeleteBucketReplicationRequest.Builder> deleteBucketReplicationRequest)
```
    Deletes the replication configuration from the bucket.
    
    To use this operation, you must have permissions to perform the s3:PutReplicationConfiguration action. The bucket owner has these permissions by default and can grant it to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.
    
    It can take a while for the deletion of a replication configuration to fully propagate.
    
    For information about replication configuration, see Replication in the Amazon S3 Developer Guide.
    
    The following operations are related to DeleteBucketReplication:
    - PutBucketReplication
    - GetBucketReplication
    This is a convenience which creates an instance of the DeleteBucketReplicationRequest.Builder avoiding the need to create one manually via DeleteBucketReplicationRequest.builder()
    Parameters:
    
    deleteBucketReplicationRequest - A Consumer that will call methods on DeleteBucketReplicationRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the DeleteBucketReplication operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - deleteBucketTagging
```
default CompletableFuture<DeleteBucketTaggingResponse> deleteBucketTagging(DeleteBucketTaggingRequest deleteBucketTaggingRequest)
```
    Deletes the tags from the bucket.
    
    To use this operation, you must have permission to perform the s3:PutBucketTagging action. By default, the bucket owner has this permission and can grant this permission to others.
    
    The following operations are related to DeleteBucketTagging:
    - GetBucketTagging
    - PutBucketTagging
    Parameters:
    
    deleteBucketTaggingRequest -
    
    Returns:
    A Java Future containing the result of the DeleteBucketTagging operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - deleteBucketTagging
```
default CompletableFuture<DeleteBucketTaggingResponse> deleteBucketTagging(Consumer<DeleteBucketTaggingRequest.Builder> deleteBucketTaggingRequest)
```
    Deletes the tags from the bucket.
    
    To use this operation, you must have permission to perform the s3:PutBucketTagging action. By default, the bucket owner has this permission and can grant this permission to others.
    
    The following operations are related to DeleteBucketTagging:
    - GetBucketTagging
    - PutBucketTagging
    This is a convenience which creates an instance of the DeleteBucketTaggingRequest.Builder avoiding the need to create one manually via DeleteBucketTaggingRequest.builder()
    Parameters:
    
    deleteBucketTaggingRequest - A Consumer that will call methods on DeleteBucketTaggingRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the DeleteBucketTagging operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - deleteBucketWebsite
```
default CompletableFuture<DeleteBucketWebsiteResponse> deleteBucketWebsite(DeleteBucketWebsiteRequest deleteBucketWebsiteRequest)
```
    This operation removes the website configuration for a bucket. Amazon S3 returns a 200 OK response upon successfully deleting a website configuration on the specified bucket. You will get a 200 OK response if the website configuration you are trying to delete does not exist on the bucket. Amazon S3 returns a 404 response if the bucket specified in the request does not exist.
    
    This DELETE operation requires the S3:DeleteBucketWebsite permission. By default, only the bucket owner can delete the website configuration attached to a bucket. However, bucket owners can grant other users permission to delete the website configuration by writing a bucket policy granting them the S3:DeleteBucketWebsite permission.
    
    For more information about hosting websites, see Hosting Websites on Amazon S3.
    
    The following operations are related to DeleteBucketWebsite:
    - GetBucketWebsite
    - PutBucketWebsite
    Parameters:
    
    deleteBucketWebsiteRequest -
    
    Returns:
    A Java Future containing the result of the DeleteBucketWebsite operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - deleteBucketWebsite
```
default CompletableFuture<DeleteBucketWebsiteResponse> deleteBucketWebsite(Consumer<DeleteBucketWebsiteRequest.Builder> deleteBucketWebsiteRequest)
```
    This operation removes the website configuration for a bucket. Amazon S3 returns a 200 OK response upon successfully deleting a website configuration on the specified bucket. You will get a 200 OK response if the website configuration you are trying to delete does not exist on the bucket. Amazon S3 returns a 404 response if the bucket specified in the request does not exist.
    
    This DELETE operation requires the S3:DeleteBucketWebsite permission. By default, only the bucket owner can delete the website configuration attached to a bucket. However, bucket owners can grant other users permission to delete the website configuration by writing a bucket policy granting them the S3:DeleteBucketWebsite permission.
    
    For more information about hosting websites, see Hosting Websites on Amazon S3.
    
    The following operations are related to DeleteBucketWebsite:
    - GetBucketWebsite
    - PutBucketWebsite
    This is a convenience which creates an instance of the DeleteBucketWebsiteRequest.Builder avoiding the need to create one manually via DeleteBucketWebsiteRequest.builder()
    Parameters:
    
    deleteBucketWebsiteRequest - A Consumer that will call methods on DeleteBucketWebsiteRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the DeleteBucketWebsite operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - deleteObject
```
default CompletableFuture<DeleteObjectResponse> deleteObject(DeleteObjectRequest deleteObjectRequest)
```
    Removes the null version (if there is one) of an object and inserts a delete marker, which becomes the latest version of the object. If there isn't a null version, Amazon S3 does not remove any objects.
    
    To remove a specific version, you must be the bucket owner and you must use the version Id subresource. Using this subresource permanently deletes the version. If the object deleted is a delete marker, Amazon S3 sets the response header, x-amz-delete-marker, to true.
    
    If the object you want to delete is in a bucket where the bucket versioning configuration is MFA Delete enabled, you must include the x-amz-mfa request header in the DELETE versionId request. Requests that include x-amz-mfa must use HTTPS.
    
    For more information about MFA Delete, see Using MFA Delete. To see sample requests that use versioning, see Sample Request.
    
    You can delete objects by explicitly calling the DELETE Object API or configure its lifecycle (PutBucketLifecycle) to enable Amazon S3 to remove them for you. If you want to block users or accounts from removing or deleting objects from your bucket, you must deny them the s3:DeleteObject, s3:DeleteObjectVersion, and s3:PutLifeCycleConfiguration actions.
    
    The following operation is related to DeleteObject:
    - PutObject
    Parameters:
    
    deleteObjectRequest -
    
    Returns:
    A Java Future containing the result of the DeleteObject operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - deleteObject
```
default CompletableFuture<DeleteObjectResponse> deleteObject(Consumer<DeleteObjectRequest.Builder> deleteObjectRequest)
```
    Removes the null version (if there is one) of an object and inserts a delete marker, which becomes the latest version of the object. If there isn't a null version, Amazon S3 does not remove any objects.
    
    To remove a specific version, you must be the bucket owner and you must use the version Id subresource. Using this subresource permanently deletes the version. If the object deleted is a delete marker, Amazon S3 sets the response header, x-amz-delete-marker, to true.
    
    If the object you want to delete is in a bucket where the bucket versioning configuration is MFA Delete enabled, you must include the x-amz-mfa request header in the DELETE versionId request. Requests that include x-amz-mfa must use HTTPS.
    
    For more information about MFA Delete, see Using MFA Delete. To see sample requests that use versioning, see Sample Request.
    
    You can delete objects by explicitly calling the DELETE Object API or configure its lifecycle (PutBucketLifecycle) to enable Amazon S3 to remove them for you. If you want to block users or accounts from removing or deleting objects from your bucket, you must deny them the s3:DeleteObject, s3:DeleteObjectVersion, and s3:PutLifeCycleConfiguration actions.
    
    The following operation is related to DeleteObject:
    - PutObject
    This is a convenience which creates an instance of the DeleteObjectRequest.Builder avoiding the need to create one manually via DeleteObjectRequest.builder()
    Parameters:
    
    deleteObjectRequest - A Consumer that will call methods on DeleteObjectRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the DeleteObject operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - deleteObjectTagging
```
default CompletableFuture<DeleteObjectTaggingResponse> deleteObjectTagging(DeleteObjectTaggingRequest deleteObjectTaggingRequest)
```
    Removes the entire tag set from the specified object. For more information about managing object tags, see Object Tagging.
    
    To use this operation, you must have permission to perform the s3:DeleteObjectTagging action.
    
    To delete tags of a specific object version, add the versionId query parameter in the request. You will need permission for the s3:DeleteObjectVersionTagging action.
    
    The following operations are related to DeleteBucketMetricsConfiguration:
    - PutObjectTagging
    - GetObjectTagging
    Parameters:
    
    deleteObjectTaggingRequest -
    
    Returns:
    A Java Future containing the result of the DeleteObjectTagging operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - deleteObjectTagging
```
default CompletableFuture<DeleteObjectTaggingResponse> deleteObjectTagging(Consumer<DeleteObjectTaggingRequest.Builder> deleteObjectTaggingRequest)
```
    Removes the entire tag set from the specified object. For more information about managing object tags, see Object Tagging.
    
    To use this operation, you must have permission to perform the s3:DeleteObjectTagging action.
    
    To delete tags of a specific object version, add the versionId query parameter in the request. You will need permission for the s3:DeleteObjectVersionTagging action.
    
    The following operations are related to DeleteBucketMetricsConfiguration:
    - PutObjectTagging
    - GetObjectTagging
    This is a convenience which creates an instance of the DeleteObjectTaggingRequest.Builder avoiding the need to create one manually via DeleteObjectTaggingRequest.builder()
    Parameters:
    
    deleteObjectTaggingRequest - A Consumer that will call methods on DeleteObjectTaggingRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the DeleteObjectTagging operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - deleteObjects
```
default CompletableFuture<DeleteObjectsResponse> deleteObjects(DeleteObjectsRequest deleteObjectsRequest)
```
    This operation enables you to delete multiple objects from a bucket using a single HTTP request. If you know the object keys that you want to delete, then this operation provides a suitable alternative to sending individual delete requests, reducing per-request overhead.
    
    The request contains a list of up to 1000 keys that you want to delete. In the XML, you provide the object key names, and optionally, version IDs if you want to delete a specific version of the object from a versioning-enabled bucket. For each key, Amazon S3 performs a delete operation and returns the result of that delete, success, or failure, in the response. Note that if the object specified in the request is not found, Amazon S3 returns the result as deleted.
    
    The operation supports two modes for the response: verbose and quiet. By default, the operation uses verbose mode in which the response includes the result of deletion of each key in your request. In quiet mode the response includes only keys where the delete operation encountered an error. For a successful deletion, the operation does not return any information about the delete in the response body.
    
    When performing this operation on an MFA Delete enabled bucket, that attempts to delete any versioned objects, you must include an MFA token. If you do not provide one, the entire request will fail, even if there are non-versioned objects you are trying to delete. If you provide an invalid token, whether there are versioned keys in the request or not, the entire Multi-Object Delete request will fail. For information about MFA Delete, see MFA Delete.
    
    Finally, the Content-MD5 header is required for all Multi-Object Delete requests. Amazon S3 uses the header value to ensure that your request body has not been altered in transit.
    
    The following operations are related to DeleteObjects:
    Parameters:
    
    deleteObjectsRequest -
    
    Returns:
    A Java Future containing the result of the DeleteObjects operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - deleteObjects
```
default CompletableFuture<DeleteObjectsResponse> deleteObjects(Consumer<DeleteObjectsRequest.Builder> deleteObjectsRequest)
```
    This operation enables you to delete multiple objects from a bucket using a single HTTP request. If you know the object keys that you want to delete, then this operation provides a suitable alternative to sending individual delete requests, reducing per-request overhead.
    
    The request contains a list of up to 1000 keys that you want to delete. In the XML, you provide the object key names, and optionally, version IDs if you want to delete a specific version of the object from a versioning-enabled bucket. For each key, Amazon S3 performs a delete operation and returns the result of that delete, success, or failure, in the response. Note that if the object specified in the request is not found, Amazon S3 returns the result as deleted.
    
    The operation supports two modes for the response: verbose and quiet. By default, the operation uses verbose mode in which the response includes the result of deletion of each key in your request. In quiet mode the response includes only keys where the delete operation encountered an error. For a successful deletion, the operation does not return any information about the delete in the response body.
    
    When performing this operation on an MFA Delete enabled bucket, that attempts to delete any versioned objects, you must include an MFA token. If you do not provide one, the entire request will fail, even if there are non-versioned objects you are trying to delete. If you provide an invalid token, whether there are versioned keys in the request or not, the entire Multi-Object Delete request will fail. For information about MFA Delete, see MFA Delete.
    
    Finally, the Content-MD5 header is required for all Multi-Object Delete requests. Amazon S3 uses the header value to ensure that your request body has not been altered in transit.
    
    The following operations are related to DeleteObjects:
    This is a convenience which creates an instance of the DeleteObjectsRequest.Builder avoiding the need to create one manually via DeleteObjectsRequest.builder()
    Parameters:
    
    deleteObjectsRequest - A Consumer that will call methods on DeleteObjectsRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the DeleteObjects operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - deletePublicAccessBlock
```
default CompletableFuture<DeletePublicAccessBlockResponse> deletePublicAccessBlock(DeletePublicAccessBlockRequest deletePublicAccessBlockRequest)
```
    Removes the PublicAccessBlock configuration for an Amazon S3 bucket. To use this operation, you must have the s3:PutBucketPublicAccessBlock permission. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.
    
    The following operations are related to DeleteBucketMetricsConfiguration:
    Parameters:
    
    deletePublicAccessBlockRequest -
    
    Returns:
    A Java Future containing the result of the DeletePublicAccessBlock operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - deletePublicAccessBlock
```
default CompletableFuture<DeletePublicAccessBlockResponse> deletePublicAccessBlock(Consumer<DeletePublicAccessBlockRequest.Builder> deletePublicAccessBlockRequest)
```
    Removes the PublicAccessBlock configuration for an Amazon S3 bucket. To use this operation, you must have the s3:PutBucketPublicAccessBlock permission. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.
    
    The following operations are related to DeleteBucketMetricsConfiguration:
    This is a convenience which creates an instance of the DeletePublicAccessBlockRequest.Builder avoiding the need to create one manually via DeletePublicAccessBlockRequest.builder()
    Parameters:
    
    deletePublicAccessBlockRequest - A Consumer that will call methods on DeletePublicAccessBlockRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the DeletePublicAccessBlock operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getBucketAccelerateConfiguration
```
default CompletableFuture<GetBucketAccelerateConfigurationResponse> getBucketAccelerateConfiguration(GetBucketAccelerateConfigurationRequest getBucketAccelerateConfigurationRequest)
```
    This implementation of the GET operation uses the accelerate subresource to return the Transfer Acceleration state of a bucket, which is either Enabled or Suspended. Amazon S3 Transfer Acceleration is a bucket-level feature that enables you to perform faster data transfers to and from Amazon S3.
    
    To use this operation, you must have permission to perform the s3:GetAccelerateConfiguration action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to your Amazon S3 Resources in the Amazon Simple Storage Service Developer Guide.
    
    You set the Transfer Acceleration state of an existing bucket to Enabled or Suspended by using the PutBucketAccelerateConfiguration operation.
    
    A GET accelerate request does not return a state value for a bucket that has no transfer acceleration state. A bucket has no Transfer Acceleration state if a state has never been set on the bucket.
    
    For more information about transfer acceleration, see Transfer Acceleration in the Amazon Simple Storage Service Developer Guide.
    
    Related Resources
    - PutBucketAccelerateConfiguration
    Parameters:
    
    getBucketAccelerateConfigurationRequest -
    
    Returns:
    A Java Future containing the result of the GetBucketAccelerateConfiguration operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getBucketAccelerateConfiguration
```
default CompletableFuture<GetBucketAccelerateConfigurationResponse> getBucketAccelerateConfiguration(Consumer<GetBucketAccelerateConfigurationRequest.Builder> getBucketAccelerateConfigurationRequest)
```
    This implementation of the GET operation uses the accelerate subresource to return the Transfer Acceleration state of a bucket, which is either Enabled or Suspended. Amazon S3 Transfer Acceleration is a bucket-level feature that enables you to perform faster data transfers to and from Amazon S3.
    
    To use this operation, you must have permission to perform the s3:GetAccelerateConfiguration action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to your Amazon S3 Resources in the Amazon Simple Storage Service Developer Guide.
    
    You set the Transfer Acceleration state of an existing bucket to Enabled or Suspended by using the PutBucketAccelerateConfiguration operation.
    
    A GET accelerate request does not return a state value for a bucket that has no transfer acceleration state. A bucket has no Transfer Acceleration state if a state has never been set on the bucket.
    
    For more information about transfer acceleration, see Transfer Acceleration in the Amazon Simple Storage Service Developer Guide.
    
    Related Resources
    - PutBucketAccelerateConfiguration
    This is a convenience which creates an instance of the GetBucketAccelerateConfigurationRequest.Builder avoiding the need to create one manually via GetBucketAccelerateConfigurationRequest.builder()
    Parameters:
    
    getBucketAccelerateConfigurationRequest - A Consumer that will call methods on GetBucketAccelerateConfigurationRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the GetBucketAccelerateConfiguration operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getBucketAcl
```
default CompletableFuture<GetBucketAclResponse> getBucketAcl(GetBucketAclRequest getBucketAclRequest)
```
    This implementation of the GET operation uses the acl subresource to return the access control list (ACL) of a bucket. To use GET to return the ACL of the bucket, you must have READ_ACP access to the bucket. If READ_ACP permission is granted to the anonymous user, you can return the ACL of the bucket without using an authorization header.
    
    Related Resources
    Parameters:
    
    getBucketAclRequest -
    
    Returns:
    A Java Future containing the result of the GetBucketAcl operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getBucketAcl
```
default CompletableFuture<GetBucketAclResponse> getBucketAcl(Consumer<GetBucketAclRequest.Builder> getBucketAclRequest)
```
    This implementation of the GET operation uses the acl subresource to return the access control list (ACL) of a bucket. To use GET to return the ACL of the bucket, you must have READ_ACP access to the bucket. If READ_ACP permission is granted to the anonymous user, you can return the ACL of the bucket without using an authorization header.
    
    Related Resources
    This is a convenience which creates an instance of the GetBucketAclRequest.Builder avoiding the need to create one manually via GetBucketAclRequest.builder()
    Parameters:
    
    getBucketAclRequest - A Consumer that will call methods on GetBucketAclRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the GetBucketAcl operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getBucketAnalyticsConfiguration
```
default CompletableFuture<GetBucketAnalyticsConfigurationResponse> getBucketAnalyticsConfiguration(GetBucketAnalyticsConfigurationRequest getBucketAnalyticsConfigurationRequest)
```
    This implementation of the GET operation returns an analytics configuration (identified by the analytics configuration ID) from the bucket.
    
    To use this operation, you must have permissions to perform the s3:GetAnalyticsConfiguration action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources in the Amazon Simple Storage Service Developer Guide.
    
    For information about Amazon S3 analytics feature, see Amazon S3 Analytics – Storage Class Analysis in the Amazon Simple Storage Service Developer Guide.
    
    Related Resources
    Parameters:
    
    getBucketAnalyticsConfigurationRequest -
    
    Returns:
    A Java Future containing the result of the GetBucketAnalyticsConfiguration operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getBucketAnalyticsConfiguration
```
default CompletableFuture<GetBucketAnalyticsConfigurationResponse> getBucketAnalyticsConfiguration(Consumer<GetBucketAnalyticsConfigurationRequest.Builder> getBucketAnalyticsConfigurationRequest)
```
    This implementation of the GET operation returns an analytics configuration (identified by the analytics configuration ID) from the bucket.
    
    To use this operation, you must have permissions to perform the s3:GetAnalyticsConfiguration action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources in the Amazon Simple Storage Service Developer Guide.
    
    For information about Amazon S3 analytics feature, see Amazon S3 Analytics – Storage Class Analysis in the Amazon Simple Storage Service Developer Guide.
    
    Related Resources
    This is a convenience which creates an instance of the GetBucketAnalyticsConfigurationRequest.Builder avoiding the need to create one manually via GetBucketAnalyticsConfigurationRequest.builder()
    Parameters:
    
    getBucketAnalyticsConfigurationRequest - A Consumer that will call methods on GetBucketAnalyticsConfigurationRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the GetBucketAnalyticsConfiguration operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getBucketCors
```
default CompletableFuture<GetBucketCorsResponse> getBucketCors(GetBucketCorsRequest getBucketCorsRequest)
```
    Returns the cors configuration information set for the bucket.
    
    To use this operation, you must have permission to perform the s3:GetBucketCORS action. By default, the bucket owner has this permission and can grant it to others.
    
    For more information about cors, see Enabling Cross-Origin Resource Sharing.
    
    The following operations are related to GetBucketCors:
    - PutBucketCors
    - DeleteBucketCors
    Parameters:
    
    getBucketCorsRequest -
    
    Returns:
    A Java Future containing the result of the GetBucketCors operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getBucketCors
```
default CompletableFuture<GetBucketCorsResponse> getBucketCors(Consumer<GetBucketCorsRequest.Builder> getBucketCorsRequest)
```
    Returns the cors configuration information set for the bucket.
    
    To use this operation, you must have permission to perform the s3:GetBucketCORS action. By default, the bucket owner has this permission and can grant it to others.
    
    For more information about cors, see Enabling Cross-Origin Resource Sharing.
    
    The following operations are related to GetBucketCors:
    - PutBucketCors
    - DeleteBucketCors
    This is a convenience which creates an instance of the GetBucketCorsRequest.Builder avoiding the need to create one manually via GetBucketCorsRequest.builder()
    Parameters:
    
    getBucketCorsRequest - A Consumer that will call methods on GetBucketCorsRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the GetBucketCors operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getBucketEncryption
```
default CompletableFuture<GetBucketEncryptionResponse> getBucketEncryption(GetBucketEncryptionRequest getBucketEncryptionRequest)
```
    Returns the default encryption configuration for an Amazon S3 bucket. For information about the Amazon S3 default encryption feature, see Amazon S3 Default Bucket Encryption.
    
    To use this operation, you must have permission to perform the s3:GetEncryptionConfiguration action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.
    
    The following operations are related to GetBucketEncryption:
    - PutBucketEncryption
    - DeleteBucketEncryption
    Parameters:
    
    getBucketEncryptionRequest -
    
    Returns:
    A Java Future containing the result of the GetBucketEncryption operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getBucketEncryption
```
default CompletableFuture<GetBucketEncryptionResponse> getBucketEncryption(Consumer<GetBucketEncryptionRequest.Builder> getBucketEncryptionRequest)
```
    Returns the default encryption configuration for an Amazon S3 bucket. For information about the Amazon S3 default encryption feature, see Amazon S3 Default Bucket Encryption.
    
    To use this operation, you must have permission to perform the s3:GetEncryptionConfiguration action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.
    
    The following operations are related to GetBucketEncryption:
    - PutBucketEncryption
    - DeleteBucketEncryption
    This is a convenience which creates an instance of the GetBucketEncryptionRequest.Builder avoiding the need to create one manually via GetBucketEncryptionRequest.builder()
    Parameters:
    
    getBucketEncryptionRequest - A Consumer that will call methods on GetBucketEncryptionRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the GetBucketEncryption operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getBucketInventoryConfiguration
```
default CompletableFuture<GetBucketInventoryConfigurationResponse> getBucketInventoryConfiguration(GetBucketInventoryConfigurationRequest getBucketInventoryConfigurationRequest)
```
    Returns an inventory configuration (identified by the inventory configuration ID) from the bucket.
    
    To use this operation, you must have permissions to perform the s3:GetInventoryConfiguration action. The bucket owner has this permission by default and can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.
    
    For information about the Amazon S3 inventory feature, see Amazon S3 Inventory.
    
    The following operations are related to GetBucketInventoryConfiguration:
    Parameters:
    
    getBucketInventoryConfigurationRequest -
    
    Returns:
    A Java Future containing the result of the GetBucketInventoryConfiguration operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getBucketInventoryConfiguration
```
default CompletableFuture<GetBucketInventoryConfigurationResponse> getBucketInventoryConfiguration(Consumer<GetBucketInventoryConfigurationRequest.Builder> getBucketInventoryConfigurationRequest)
```
    Returns an inventory configuration (identified by the inventory configuration ID) from the bucket.
    
    To use this operation, you must have permissions to perform the s3:GetInventoryConfiguration action. The bucket owner has this permission by default and can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.
    
    For information about the Amazon S3 inventory feature, see Amazon S3 Inventory.
    
    The following operations are related to GetBucketInventoryConfiguration:
    This is a convenience which creates an instance of the GetBucketInventoryConfigurationRequest.Builder avoiding the need to create one manually via GetBucketInventoryConfigurationRequest.builder()
    Parameters:
    
    getBucketInventoryConfigurationRequest - A Consumer that will call methods on GetBucketInventoryConfigurationRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the GetBucketInventoryConfiguration operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getBucketLifecycleConfiguration
```
default CompletableFuture<GetBucketLifecycleConfigurationResponse> getBucketLifecycleConfiguration(GetBucketLifecycleConfigurationRequest getBucketLifecycleConfigurationRequest)
```
    Bucket lifecycle configuration now supports specifying a lifecycle rule using an object key name prefix, one or more object tags, or a combination of both. Accordingly, this section describes the latest API. The response describes the new filter element that you can use to specify a filter to select a subset of objects to which the rule applies. If you are still using previous version of the lifecycle configuration, it works. For the earlier API description, see GetBucketLifecycle.
    
    Returns the lifecycle configuration information set on the bucket. For information about lifecycle configuration, see Object Lifecycle Management.
    
    To use this operation, you must have permission to perform the s3:GetLifecycleConfiguration action. The bucket owner has this permission, by default. The bucket owner can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.
    
    GetBucketLifecycleConfiguration has the following special error:
    - Error code: NoSuchLifecycleConfiguration
      
      Description: The lifecycle configuration does not exist.
      
      HTTP Status Code: 404 Not Found
      
      SOAP Fault Code Prefix: Client
    The following operations are related to DeleteBucketMetricsConfiguration:
    Parameters:
    
    getBucketLifecycleConfigurationRequest -
    
    Returns:
    A Java Future containing the result of the GetBucketLifecycleConfiguration operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getBucketLifecycleConfiguration
```
default CompletableFuture<GetBucketLifecycleConfigurationResponse> getBucketLifecycleConfiguration(Consumer<GetBucketLifecycleConfigurationRequest.Builder> getBucketLifecycleConfigurationRequest)
```
    Bucket lifecycle configuration now supports specifying a lifecycle rule using an object key name prefix, one or more object tags, or a combination of both. Accordingly, this section describes the latest API. The response describes the new filter element that you can use to specify a filter to select a subset of objects to which the rule applies. If you are still using previous version of the lifecycle configuration, it works. For the earlier API description, see GetBucketLifecycle.
    
    Returns the lifecycle configuration information set on the bucket. For information about lifecycle configuration, see Object Lifecycle Management.
    
    To use this operation, you must have permission to perform the s3:GetLifecycleConfiguration action. The bucket owner has this permission, by default. The bucket owner can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.
    
    GetBucketLifecycleConfiguration has the following special error:
    - Error code: NoSuchLifecycleConfiguration
      
      Description: The lifecycle configuration does not exist.
      
      HTTP Status Code: 404 Not Found
      
      SOAP Fault Code Prefix: Client
    The following operations are related to DeleteBucketMetricsConfiguration:
    This is a convenience which creates an instance of the GetBucketLifecycleConfigurationRequest.Builder avoiding the need to create one manually via GetBucketLifecycleConfigurationRequest.builder()
    Parameters:
    
    getBucketLifecycleConfigurationRequest - A Consumer that will call methods on GetBucketLifecycleConfigurationRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the GetBucketLifecycleConfiguration operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getBucketLocation
```
default CompletableFuture<GetBucketLocationResponse> getBucketLocation(GetBucketLocationRequest getBucketLocationRequest)
```
    Returns the Region the bucket resides in. You set the bucket's Region using the LocationConstraint request parameter in a CreateBucket request. For more information, see CreateBucket.
    
    To use this implementation of the operation, you must be the bucket owner.
    
    The following operations are related to GetBucketLocation:
    - GetObject
    - CreateBucket
    Parameters:
    
    getBucketLocationRequest -
    
    Returns:
    A Java Future containing the result of the GetBucketLocation operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getBucketLocation
```
default CompletableFuture<GetBucketLocationResponse> getBucketLocation(Consumer<GetBucketLocationRequest.Builder> getBucketLocationRequest)
```
    Returns the Region the bucket resides in. You set the bucket's Region using the LocationConstraint request parameter in a CreateBucket request. For more information, see CreateBucket.
    
    To use this implementation of the operation, you must be the bucket owner.
    
    The following operations are related to GetBucketLocation:
    - GetObject
    - CreateBucket
    This is a convenience which creates an instance of the GetBucketLocationRequest.Builder avoiding the need to create one manually via GetBucketLocationRequest.builder()
    Parameters:
    
    getBucketLocationRequest - A Consumer that will call methods on GetBucketLocationRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the GetBucketLocation operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getBucketLogging
```
default CompletableFuture<GetBucketLoggingResponse> getBucketLogging(GetBucketLoggingRequest getBucketLoggingRequest)
```
    Returns the logging status of a bucket and the permissions users have to view and modify that status. To use GET, you must be the bucket owner.
    
    The following operations are related to GetBucketLogging:
    - CreateBucket
    - PutBucketLogging
    Parameters:
    
    getBucketLoggingRequest -
    
    Returns:
    A Java Future containing the result of the GetBucketLogging operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getBucketLogging
```
default CompletableFuture<GetBucketLoggingResponse> getBucketLogging(Consumer<GetBucketLoggingRequest.Builder> getBucketLoggingRequest)
```
    Returns the logging status of a bucket and the permissions users have to view and modify that status. To use GET, you must be the bucket owner.
    
    The following operations are related to GetBucketLogging:
    - CreateBucket
    - PutBucketLogging
    This is a convenience which creates an instance of the GetBucketLoggingRequest.Builder avoiding the need to create one manually via GetBucketLoggingRequest.builder()
    Parameters:
    
    getBucketLoggingRequest - A Consumer that will call methods on GetBucketLoggingRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the GetBucketLogging operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getBucketMetricsConfiguration
```
default CompletableFuture<GetBucketMetricsConfigurationResponse> getBucketMetricsConfiguration(GetBucketMetricsConfigurationRequest getBucketMetricsConfigurationRequest)
```
    Gets a metrics configuration (specified by the metrics configuration ID) from the bucket. Note that this doesn't include the daily storage metrics.
    
    To use this operation, you must have permissions to perform the s3:GetMetricsConfiguration action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.
    
    For information about CloudWatch request metrics for Amazon S3, see Monitoring Metrics with Amazon CloudWatch.
    
    The following operations are related to GetBucketMetricsConfiguration:
    Parameters:
    
    getBucketMetricsConfigurationRequest -
    
    Returns:
    A Java Future containing the result of the GetBucketMetricsConfiguration operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getBucketMetricsConfiguration
```
default CompletableFuture<GetBucketMetricsConfigurationResponse> getBucketMetricsConfiguration(Consumer<GetBucketMetricsConfigurationRequest.Builder> getBucketMetricsConfigurationRequest)
```
    Gets a metrics configuration (specified by the metrics configuration ID) from the bucket. Note that this doesn't include the daily storage metrics.
    
    To use this operation, you must have permissions to perform the s3:GetMetricsConfiguration action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.
    
    For information about CloudWatch request metrics for Amazon S3, see Monitoring Metrics with Amazon CloudWatch.
    
    The following operations are related to GetBucketMetricsConfiguration:
    This is a convenience which creates an instance of the GetBucketMetricsConfigurationRequest.Builder avoiding the need to create one manually via GetBucketMetricsConfigurationRequest.builder()
    Parameters:
    
    getBucketMetricsConfigurationRequest - A Consumer that will call methods on GetBucketMetricsConfigurationRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the GetBucketMetricsConfiguration operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getBucketNotificationConfiguration
```
default CompletableFuture<GetBucketNotificationConfigurationResponse> getBucketNotificationConfiguration(GetBucketNotificationConfigurationRequest getBucketNotificationConfigurationRequest)
```
    Returns the notification configuration of a bucket.
    
    If notifications are not enabled on the bucket, the operation returns an empty NotificationConfiguration element.
    
    By default, you must be the bucket owner to read the notification configuration of a bucket. However, the bucket owner can use a bucket policy to grant permission to other users to read this configuration with the s3:GetBucketNotification permission.
    
    For more information about setting and reading the notification configuration on a bucket, see Setting Up Notification of Bucket Events. For more information about bucket policies, see Using Bucket Policies.
    
    The following operation is related to GetBucketNotification:
    - PutBucketNotification
    Parameters:
    
    getBucketNotificationConfigurationRequest -
    
    Returns:
    A Java Future containing the result of the GetBucketNotificationConfiguration operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getBucketNotificationConfiguration
```
default CompletableFuture<GetBucketNotificationConfigurationResponse> getBucketNotificationConfiguration(Consumer<GetBucketNotificationConfigurationRequest.Builder> getBucketNotificationConfigurationRequest)
```
    Returns the notification configuration of a bucket.
    
    If notifications are not enabled on the bucket, the operation returns an empty NotificationConfiguration element.
    
    By default, you must be the bucket owner to read the notification configuration of a bucket. However, the bucket owner can use a bucket policy to grant permission to other users to read this configuration with the s3:GetBucketNotification permission.
    
    For more information about setting and reading the notification configuration on a bucket, see Setting Up Notification of Bucket Events. For more information about bucket policies, see Using Bucket Policies.
    
    The following operation is related to GetBucketNotification:
    - PutBucketNotification
    This is a convenience which creates an instance of the GetBucketNotificationConfigurationRequest.Builder avoiding the need to create one manually via GetBucketNotificationConfigurationRequest.builder()
    Parameters:
    
    getBucketNotificationConfigurationRequest - A Consumer that will call methods on GetBucketNotificationConfigurationRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the GetBucketNotificationConfiguration operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getBucketPolicy
```
default CompletableFuture<GetBucketPolicyResponse> getBucketPolicy(GetBucketPolicyRequest getBucketPolicyRequest)
```
    Returns the policy of a specified bucket. If you are using an identity other than the root user of the AWS account that owns the bucket, the calling identity must have the GetBucketPolicy permissions on the specified bucket and belong to the bucket owner's account in order to use this operation.
    
    If you don't have GetBucketPolicy 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.
    
    As a security precaution, the root user of the AWS account that owns a bucket can always use this operation, even if the policy explicitly denies the root user the ability to perform this action.
    
    For more information about bucket policies, see Using Bucket Policies and User Policies.
    
    The following operation is related to GetBucketPolicy:
    - GetObject
    Parameters:
    
    getBucketPolicyRequest -
    
    Returns:
    A Java Future containing the result of the GetBucketPolicy operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getBucketPolicy
```
default CompletableFuture<GetBucketPolicyResponse> getBucketPolicy(Consumer<GetBucketPolicyRequest.Builder> getBucketPolicyRequest)
```
    Returns the policy of a specified bucket. If you are using an identity other than the root user of the AWS account that owns the bucket, the calling identity must have the GetBucketPolicy permissions on the specified bucket and belong to the bucket owner's account in order to use this operation.
    
    If you don't have GetBucketPolicy 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.
    
    As a security precaution, the root user of the AWS account that owns a bucket can always use this operation, even if the policy explicitly denies the root user the ability to perform this action.
    
    For more information about bucket policies, see Using Bucket Policies and User Policies.
    
    The following operation is related to GetBucketPolicy:
    - GetObject
    This is a convenience which creates an instance of the GetBucketPolicyRequest.Builder avoiding the need to create one manually via GetBucketPolicyRequest.builder()
    Parameters:
    
    getBucketPolicyRequest - A Consumer that will call methods on GetBucketPolicyRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the GetBucketPolicy operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getBucketPolicyStatus
```
default CompletableFuture<GetBucketPolicyStatusResponse> getBucketPolicyStatus(GetBucketPolicyStatusRequest getBucketPolicyStatusRequest)
```
    Retrieves the policy status for an Amazon S3 bucket, indicating whether the bucket is public. In order to use this operation, you must have the s3:GetBucketPolicyStatus permission. For more information about Amazon S3 permissions, see Specifying Permissions in a Policy.
    
    For more information about when Amazon S3 considers a bucket public, see The Meaning of "Public".
    
    The following operations are related to GetBucketPolicyStatus:
    Parameters:
    
    getBucketPolicyStatusRequest -
    
    Returns:
    A Java Future containing the result of the GetBucketPolicyStatus operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getBucketPolicyStatus
```
default CompletableFuture<GetBucketPolicyStatusResponse> getBucketPolicyStatus(Consumer<GetBucketPolicyStatusRequest.Builder> getBucketPolicyStatusRequest)
```
    Retrieves the policy status for an Amazon S3 bucket, indicating whether the bucket is public. In order to use this operation, you must have the s3:GetBucketPolicyStatus permission. For more information about Amazon S3 permissions, see Specifying Permissions in a Policy.
    
    For more information about when Amazon S3 considers a bucket public, see The Meaning of "Public".
    
    The following operations are related to GetBucketPolicyStatus:
    This is a convenience which creates an instance of the GetBucketPolicyStatusRequest.Builder avoiding the need to create one manually via GetBucketPolicyStatusRequest.builder()
    Parameters:
    
    getBucketPolicyStatusRequest - A Consumer that will call methods on GetBucketPolicyStatusRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the GetBucketPolicyStatus operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getBucketReplication
```
default CompletableFuture<GetBucketReplicationResponse> getBucketReplication(GetBucketReplicationRequest getBucketReplicationRequest)
```
    Returns the replication configuration of a bucket.
    
    It can take a while to propagate the put or delete a replication configuration to all Amazon S3 systems. Therefore, a get request soon after put or delete can return a wrong result.
    
    For information about replication configuration, see Replication in the Amazon Simple Storage Service Developer Guide.
    
    This operation requires permissions for the s3:GetReplicationConfiguration action. For more information about permissions, see Using Bucket Policies and User Policies.
    
    If you include the Filter element in a replication configuration, you must also include the DeleteMarkerReplication and Priority elements. The response also returns those elements.
    
    For information about GetBucketReplication errors, see ReplicationErrorCodeList
    
    The following operations are related to GetBucketReplication:
    - PutBucketReplication
    - DeleteBucketReplication
    Parameters:
    
    getBucketReplicationRequest -
    
    Returns:
    A Java Future containing the result of the GetBucketReplication operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getBucketReplication
```
default CompletableFuture<GetBucketReplicationResponse> getBucketReplication(Consumer<GetBucketReplicationRequest.Builder> getBucketReplicationRequest)
```
    Returns the replication configuration of a bucket.
    
    It can take a while to propagate the put or delete a replication configuration to all Amazon S3 systems. Therefore, a get request soon after put or delete can return a wrong result.
    
    For information about replication configuration, see Replication in the Amazon Simple Storage Service Developer Guide.
    
    This operation requires permissions for the s3:GetReplicationConfiguration action. For more information about permissions, see Using Bucket Policies and User Policies.
    
    If you include the Filter element in a replication configuration, you must also include the DeleteMarkerReplication and Priority elements. The response also returns those elements.
    
    For information about GetBucketReplication errors, see ReplicationErrorCodeList
    
    The following operations are related to GetBucketReplication:
    - PutBucketReplication
    - DeleteBucketReplication
    This is a convenience which creates an instance of the GetBucketReplicationRequest.Builder avoiding the need to create one manually via GetBucketReplicationRequest.builder()
    Parameters:
    
    getBucketReplicationRequest - A Consumer that will call methods on GetBucketReplicationRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the GetBucketReplication operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getBucketRequestPayment
```
default CompletableFuture<GetBucketRequestPaymentResponse> getBucketRequestPayment(GetBucketRequestPaymentRequest getBucketRequestPaymentRequest)
```
    Returns the request payment configuration of a bucket. To use this version of the operation, you must be the bucket owner. For more information, see Requester Pays Buckets.
    
    The following operations are related to GetBucketRequestPayment:
    - ListObjects
    Parameters:
    
    getBucketRequestPaymentRequest -
    
    Returns:
    A Java Future containing the result of the GetBucketRequestPayment operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getBucketRequestPayment
```
default CompletableFuture<GetBucketRequestPaymentResponse> getBucketRequestPayment(Consumer<GetBucketRequestPaymentRequest.Builder> getBucketRequestPaymentRequest)
```
    Returns the request payment configuration of a bucket. To use this version of the operation, you must be the bucket owner. For more information, see Requester Pays Buckets.
    
    The following operations are related to GetBucketRequestPayment:
    - ListObjects
    This is a convenience which creates an instance of the GetBucketRequestPaymentRequest.Builder avoiding the need to create one manually via GetBucketRequestPaymentRequest.builder()
    Parameters:
    
    getBucketRequestPaymentRequest - A Consumer that will call methods on GetBucketRequestPaymentRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the GetBucketRequestPayment operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getBucketTagging
```
default CompletableFuture<GetBucketTaggingResponse> getBucketTagging(GetBucketTaggingRequest getBucketTaggingRequest)
```
    Returns the tag set associated with the bucket.
    
    To use this operation, you must have permission to perform the s3:GetBucketTagging action. By default, the bucket owner has this permission and can grant this permission to others.
    
    GetBucketTagging has the following special error:
    - Error code: NoSuchTagSetError
      
      Description: There is no tag set associated with the bucket.
    The following operations are related to GetBucketTagging:
    - PutBucketTagging
    - DeleteBucketTagging
    Parameters:
    
    getBucketTaggingRequest -
    
    Returns:
    A Java Future containing the result of the GetBucketTagging operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getBucketTagging
```
default CompletableFuture<GetBucketTaggingResponse> getBucketTagging(Consumer<GetBucketTaggingRequest.Builder> getBucketTaggingRequest)
```
    Returns the tag set associated with the bucket.
    
    To use this operation, you must have permission to perform the s3:GetBucketTagging action. By default, the bucket owner has this permission and can grant this permission to others.
    
    GetBucketTagging has the following special error:
    - Error code: NoSuchTagSetError
      
      Description: There is no tag set associated with the bucket.
    The following operations are related to GetBucketTagging:
    - PutBucketTagging
    - DeleteBucketTagging
    This is a convenience which creates an instance of the GetBucketTaggingRequest.Builder avoiding the need to create one manually via GetBucketTaggingRequest.builder()
    Parameters:
    
    getBucketTaggingRequest - A Consumer that will call methods on GetBucketTaggingRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the GetBucketTagging operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getBucketVersioning
```
default CompletableFuture<GetBucketVersioningResponse> getBucketVersioning(GetBucketVersioningRequest getBucketVersioningRequest)
```
    Returns the versioning state of a bucket.
    
    To retrieve the versioning state of a bucket, you must be the bucket owner.
    
    This implementation also returns the MFA Delete status of the versioning state. If the MFA Delete status is enabled, the bucket owner must use an authentication device to change the versioning state of the bucket.
    
    The following operations are related to GetBucketVersioning:
    Parameters:
    
    getBucketVersioningRequest -
    
    Returns:
    A Java Future containing the result of the GetBucketVersioning operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getBucketVersioning
```
default CompletableFuture<GetBucketVersioningResponse> getBucketVersioning(Consumer<GetBucketVersioningRequest.Builder> getBucketVersioningRequest)
```
    Returns the versioning state of a bucket.
    
    To retrieve the versioning state of a bucket, you must be the bucket owner.
    
    This implementation also returns the MFA Delete status of the versioning state. If the MFA Delete status is enabled, the bucket owner must use an authentication device to change the versioning state of the bucket.
    
    The following operations are related to GetBucketVersioning:
    This is a convenience which creates an instance of the GetBucketVersioningRequest.Builder avoiding the need to create one manually via GetBucketVersioningRequest.builder()
    Parameters:
    
    getBucketVersioningRequest - A Consumer that will call methods on GetBucketVersioningRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the GetBucketVersioning operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getBucketWebsite
```
default CompletableFuture<GetBucketWebsiteResponse> getBucketWebsite(GetBucketWebsiteRequest getBucketWebsiteRequest)
```
    Returns the website configuration for a bucket. To host website on Amazon S3, you can configure a bucket as website by adding a website configuration. For more information about hosting websites, see Hosting Websites on Amazon S3.
    
    This GET operation requires the S3:GetBucketWebsite permission. By default, only the bucket owner can read the bucket website configuration. However, bucket owners can allow other users to read the website configuration by writing a bucket policy granting them the S3:GetBucketWebsite permission.
    
    The following operations are related to DeleteBucketWebsite:
    - DeleteBucketWebsite
    - PutBucketWebsite
    Parameters:
    
    getBucketWebsiteRequest -
    
    Returns:
    A Java Future containing the result of the GetBucketWebsite operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getBucketWebsite
```
default CompletableFuture<GetBucketWebsiteResponse> getBucketWebsite(Consumer<GetBucketWebsiteRequest.Builder> getBucketWebsiteRequest)
```
    Returns the website configuration for a bucket. To host website on Amazon S3, you can configure a bucket as website by adding a website configuration. For more information about hosting websites, see Hosting Websites on Amazon S3.
    
    This GET operation requires the S3:GetBucketWebsite permission. By default, only the bucket owner can read the bucket website configuration. However, bucket owners can allow other users to read the website configuration by writing a bucket policy granting them the S3:GetBucketWebsite permission.
    
    The following operations are related to DeleteBucketWebsite:
    - DeleteBucketWebsite
    - PutBucketWebsite
    This is a convenience which creates an instance of the GetBucketWebsiteRequest.Builder avoiding the need to create one manually via GetBucketWebsiteRequest.builder()
    Parameters:
    
    getBucketWebsiteRequest - A Consumer that will call methods on GetBucketWebsiteRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the GetBucketWebsite operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getObject
```
default <ReturnT> CompletableFuture<ReturnT> getObject(GetObjectRequest getObjectRequest,
                                                       AsyncResponseTransformer<GetObjectResponse,ReturnT> asyncResponseTransformer)
```
    Retrieves objects from Amazon S3. To use GET, you must have READ access to the object. If you grant READ access to the anonymous user, you can return the object without using an authorization header.
    
    An Amazon S3 bucket has no directory hierarchy such as you would find in a typical computer file system. You can, however, create a logical hierarchy by using object key names that imply a folder structure. For example, instead of naming an object sample.jpg, you can name it photos/2006/February/sample.jpg.
    
    To get an object from such a logical hierarchy, specify the full key name for the object in the GET operation. For a virtual hosted-style request example, if you have the object photos/2006/February/sample.jpg, specify the resource as /photos/2006/February/sample.jpg. For a path-style request example, if you have the object photos/2006/February/sample.jpg in the bucket named examplebucket, specify the resource as /examplebucket/photos/2006/February/sample.jpg. For more information about request types, see HTTP Host Header Bucket Specification.
    
    To distribute large files to many people, you can save bandwidth costs by using BitTorrent. For more information, see Amazon S3 Torrent. For more information about returning the ACL of an object, see GetObjectAcl.
    
    If the object you are retrieving is stored in the GLACIER or DEEP_ARCHIVE storage classes, before you can retrieve the object you must first restore a copy using . Otherwise, this operation returns an InvalidObjectStateError error. For information about restoring archived objects, see Restoring Archived Objects.
    
    Encryption request headers, like x-amz-server-side-encryption, should not be sent for GET requests if your object uses server-side encryption with CMKs stored in AWS KMS (SSE-KMS) or server-side encryption with Amazon S3–managed encryption keys (SSE-S3). If your object does use these types of keys, you’ll get an HTTP 400 BadRequest error.
    
    If you encrypt an object by using server-side encryption with customer-provided encryption keys (SSE-C) when you store the object in Amazon S3, then when you GET the object, you must use the following headers:
    - x-amz-server-side-encryption-customer-algorithm
    - x-amz-server-side-encryption-customer-key
    - x-amz-server-side-encryption-customer-key-MD5
    For more information about SSE-C, see Server-Side Encryption (Using Customer-Provided Encryption Keys).
    
    Assuming you have permission to read object tags (permission for the s3:GetObjectVersionTagging action), the response also returns the x-amz-tagging-count header that provides the count of number of tags associated with the object. You can use GetObjectTagging to retrieve the tag set associated with an object.
    
    Permissions
    
    You need the s3:GetObject permission for this operation. For more information, see Specifying Permissions in a Policy. If the object you request does not exist, the error Amazon S3 returns depends on whether you also have the s3:ListBucket permission.
    - If you have the s3:ListBucket permission on the bucket, Amazon S3 will return an HTTP status code 404 ("no such key") error.
    - If you don’t have the s3:ListBucket permission, Amazon S3 will return an HTTP status code 403 ("access denied") error.
    Versioning
    
    By default, the GET operation returns the current version of an object. To return a different version, use the versionId subresource.
    
    If the current version of the object is a delete marker, Amazon S3 behaves as if the object was deleted and includes x-amz-delete-marker: true in the response.
    
    For more information about versioning, see PutBucketVersioning.
    
    Overriding Response Header Values
    
    There are times when you want to override certain response header values in a GET response. For example, you might override the Content-Disposition response header value in your GET request.
    
    You can override values for a set of response headers using the following query parameters. These response header values are sent only on a successful request, that is, when status code 200 OK is returned. The set of headers you can override using these parameters is a subset of the headers that Amazon S3 accepts when you create an object. The response headers that you can override for the GET response are Content-Type, Content-Language, Expires, Cache-Control, Content-Disposition , and Content-Encoding. To override these header values in the GET response, you use the following request parameters.
    
    You must sign the request, either using an Authorization header or a presigned URL, when using these parameters. They cannot be used with an unsigned (anonymous) request.
    - response-content-type
    - response-content-language
    - response-expires
    - response-cache-control
    - response-content-disposition
    - response-content-encoding
    Additional Considerations about Request Headers
    
    If both of the If-Match and If-Unmodified-Since headers are present in the request as follows: If-Match condition evaluates to true, and; If-Unmodified-Since condition evaluates to false; then, S3 returns 200 OK and the data requested.
    
    If both of the If-None-Match and If-Modified-Since headers are present in the request as follows: If-None-Match condition evaluates to false, and; If-Modified-Since condition evaluates to true; then, S3 returns 304 Not Modified response code.
    
    For more information about conditional requests, see RFC 7232.
    
    The following operations are related to GetObject:
    - ListBuckets
    - GetObjectAcl
    Parameters:
    
    getObjectRequest -
    
    asyncResponseTransformer - The response transformer for processing the streaming response in a non-blocking manner. See AsyncResponseTransformer for details on how this callback should be implemented and for links to precanned implementations for common scenarios like downloading to a file. The service documentation for the response content is as follows '
    Object data.
    '.
    
    Returns:
    A future to the transformed result of the AsyncResponseTransformer.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    NoSuchKeyException The specified key does not exist.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getObject
```
default <ReturnT> CompletableFuture<ReturnT> getObject(Consumer<GetObjectRequest.Builder> getObjectRequest,
                                                       AsyncResponseTransformer<GetObjectResponse,ReturnT> asyncResponseTransformer)
```
    Retrieves objects from Amazon S3. To use GET, you must have READ access to the object. If you grant READ access to the anonymous user, you can return the object without using an authorization header.
    
    An Amazon S3 bucket has no directory hierarchy such as you would find in a typical computer file system. You can, however, create a logical hierarchy by using object key names that imply a folder structure. For example, instead of naming an object sample.jpg, you can name it photos/2006/February/sample.jpg.
    
    To get an object from such a logical hierarchy, specify the full key name for the object in the GET operation. For a virtual hosted-style request example, if you have the object photos/2006/February/sample.jpg, specify the resource as /photos/2006/February/sample.jpg. For a path-style request example, if you have the object photos/2006/February/sample.jpg in the bucket named examplebucket, specify the resource as /examplebucket/photos/2006/February/sample.jpg. For more information about request types, see HTTP Host Header Bucket Specification.
    
    To distribute large files to many people, you can save bandwidth costs by using BitTorrent. For more information, see Amazon S3 Torrent. For more information about returning the ACL of an object, see GetObjectAcl.
    
    If the object you are retrieving is stored in the GLACIER or DEEP_ARCHIVE storage classes, before you can retrieve the object you must first restore a copy using . Otherwise, this operation returns an InvalidObjectStateError error. For information about restoring archived objects, see Restoring Archived Objects.
    
    Encryption request headers, like x-amz-server-side-encryption, should not be sent for GET requests if your object uses server-side encryption with CMKs stored in AWS KMS (SSE-KMS) or server-side encryption with Amazon S3–managed encryption keys (SSE-S3). If your object does use these types of keys, you’ll get an HTTP 400 BadRequest error.
    
    If you encrypt an object by using server-side encryption with customer-provided encryption keys (SSE-C) when you store the object in Amazon S3, then when you GET the object, you must use the following headers:
    - x-amz-server-side-encryption-customer-algorithm
    - x-amz-server-side-encryption-customer-key
    - x-amz-server-side-encryption-customer-key-MD5
    For more information about SSE-C, see Server-Side Encryption (Using Customer-Provided Encryption Keys).
    
    Assuming you have permission to read object tags (permission for the s3:GetObjectVersionTagging action), the response also returns the x-amz-tagging-count header that provides the count of number of tags associated with the object. You can use GetObjectTagging to retrieve the tag set associated with an object.
    
    Permissions
    
    You need the s3:GetObject permission for this operation. For more information, see Specifying Permissions in a Policy. If the object you request does not exist, the error Amazon S3 returns depends on whether you also have the s3:ListBucket permission.
    - If you have the s3:ListBucket permission on the bucket, Amazon S3 will return an HTTP status code 404 ("no such key") error.
    - If you don’t have the s3:ListBucket permission, Amazon S3 will return an HTTP status code 403 ("access denied") error.
    Versioning
    
    By default, the GET operation returns the current version of an object. To return a different version, use the versionId subresource.
    
    If the current version of the object is a delete marker, Amazon S3 behaves as if the object was deleted and includes x-amz-delete-marker: true in the response.
    
    For more information about versioning, see PutBucketVersioning.
    
    Overriding Response Header Values
    
    There are times when you want to override certain response header values in a GET response. For example, you might override the Content-Disposition response header value in your GET request.
    
    You can override values for a set of response headers using the following query parameters. These response header values are sent only on a successful request, that is, when status code 200 OK is returned. The set of headers you can override using these parameters is a subset of the headers that Amazon S3 accepts when you create an object. The response headers that you can override for the GET response are Content-Type, Content-Language, Expires, Cache-Control, Content-Disposition , and Content-Encoding. To override these header values in the GET response, you use the following request parameters.
    
    You must sign the request, either using an Authorization header or a presigned URL, when using these parameters. They cannot be used with an unsigned (anonymous) request.
    - response-content-type
    - response-content-language
    - response-expires
    - response-cache-control
    - response-content-disposition
    - response-content-encoding
    Additional Considerations about Request Headers
    
    If both of the If-Match and If-Unmodified-Since headers are present in the request as follows: If-Match condition evaluates to true, and; If-Unmodified-Since condition evaluates to false; then, S3 returns 200 OK and the data requested.
    
    If both of the If-None-Match and If-Modified-Since headers are present in the request as follows: If-None-Match condition evaluates to false, and; If-Modified-Since condition evaluates to true; then, S3 returns 304 Not Modified response code.
    
    For more information about conditional requests, see RFC 7232.
    
    The following operations are related to GetObject:
    - ListBuckets
    - GetObjectAcl
    This is a convenience which creates an instance of the GetObjectRequest.Builder avoiding the need to create one manually via GetObjectRequest.builder()
    Parameters:
    
    getObjectRequest - A Consumer that will call methods on GetObjectRequest.Builder to create a request.
    
    asyncResponseTransformer - The response transformer for processing the streaming response in a non-blocking manner. See AsyncResponseTransformer for details on how this callback should be implemented and for links to precanned implementations for common scenarios like downloading to a file. The service documentation for the response content is as follows '
    Object data.
    '.
    
    Returns:
    A future to the transformed result of the AsyncResponseTransformer.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    NoSuchKeyException The specified key does not exist.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getObject
```
default CompletableFuture<GetObjectResponse> getObject(GetObjectRequest getObjectRequest,
                                                       Path destinationPath)
```
    Retrieves objects from Amazon S3. To use GET, you must have READ access to the object. If you grant READ access to the anonymous user, you can return the object without using an authorization header.
    
    An Amazon S3 bucket has no directory hierarchy such as you would find in a typical computer file system. You can, however, create a logical hierarchy by using object key names that imply a folder structure. For example, instead of naming an object sample.jpg, you can name it photos/2006/February/sample.jpg.
    
    To get an object from such a logical hierarchy, specify the full key name for the object in the GET operation. For a virtual hosted-style request example, if you have the object photos/2006/February/sample.jpg, specify the resource as /photos/2006/February/sample.jpg. For a path-style request example, if you have the object photos/2006/February/sample.jpg in the bucket named examplebucket, specify the resource as /examplebucket/photos/2006/February/sample.jpg. For more information about request types, see HTTP Host Header Bucket Specification.
    
    To distribute large files to many people, you can save bandwidth costs by using BitTorrent. For more information, see Amazon S3 Torrent. For more information about returning the ACL of an object, see GetObjectAcl.
    
    If the object you are retrieving is stored in the GLACIER or DEEP_ARCHIVE storage classes, before you can retrieve the object you must first restore a copy using . Otherwise, this operation returns an InvalidObjectStateError error. For information about restoring archived objects, see Restoring Archived Objects.
    
    Encryption request headers, like x-amz-server-side-encryption, should not be sent for GET requests if your object uses server-side encryption with CMKs stored in AWS KMS (SSE-KMS) or server-side encryption with Amazon S3–managed encryption keys (SSE-S3). If your object does use these types of keys, you’ll get an HTTP 400 BadRequest error.
    
    If you encrypt an object by using server-side encryption with customer-provided encryption keys (SSE-C) when you store the object in Amazon S3, then when you GET the object, you must use the following headers:
    - x-amz-server-side-encryption-customer-algorithm
    - x-amz-server-side-encryption-customer-key
    - x-amz-server-side-encryption-customer-key-MD5
    For more information about SSE-C, see Server-Side Encryption (Using Customer-Provided Encryption Keys).
    
    Assuming you have permission to read object tags (permission for the s3:GetObjectVersionTagging action), the response also returns the x-amz-tagging-count header that provides the count of number of tags associated with the object. You can use GetObjectTagging to retrieve the tag set associated with an object.
    
    Permissions
    
    You need the s3:GetObject permission for this operation. For more information, see Specifying Permissions in a Policy. If the object you request does not exist, the error Amazon S3 returns depends on whether you also have the s3:ListBucket permission.
    - If you have the s3:ListBucket permission on the bucket, Amazon S3 will return an HTTP status code 404 ("no such key") error.
    - If you don’t have the s3:ListBucket permission, Amazon S3 will return an HTTP status code 403 ("access denied") error.
    Versioning
    
    By default, the GET operation returns the current version of an object. To return a different version, use the versionId subresource.
    
    If the current version of the object is a delete marker, Amazon S3 behaves as if the object was deleted and includes x-amz-delete-marker: true in the response.
    
    For more information about versioning, see PutBucketVersioning.
    
    Overriding Response Header Values
    
    There are times when you want to override certain response header values in a GET response. For example, you might override the Content-Disposition response header value in your GET request.
    
    You can override values for a set of response headers using the following query parameters. These response header values are sent only on a successful request, that is, when status code 200 OK is returned. The set of headers you can override using these parameters is a subset of the headers that Amazon S3 accepts when you create an object. The response headers that you can override for the GET response are Content-Type, Content-Language, Expires, Cache-Control, Content-Disposition , and Content-Encoding. To override these header values in the GET response, you use the following request parameters.
    
    You must sign the request, either using an Authorization header or a presigned URL, when using these parameters. They cannot be used with an unsigned (anonymous) request.
    - response-content-type
    - response-content-language
    - response-expires
    - response-cache-control
    - response-content-disposition
    - response-content-encoding
    Additional Considerations about Request Headers
    
    If both of the If-Match and If-Unmodified-Since headers are present in the request as follows: If-Match condition evaluates to true, and; If-Unmodified-Since condition evaluates to false; then, S3 returns 200 OK and the data requested.
    
    If both of the If-None-Match and If-Modified-Since headers are present in the request as follows: If-None-Match condition evaluates to false, and; If-Modified-Since condition evaluates to true; then, S3 returns 304 Not Modified response code.
    
    For more information about conditional requests, see RFC 7232.
    
    The following operations are related to GetObject:
    - ListBuckets
    - GetObjectAcl
    Parameters:
    
    getObjectRequest -
    
    destinationPath - Path to file that response contents will be written to. The file must not exist or this method will throw an exception. If the file is not writable by the current user then an exception will be thrown. The service documentation for the response content is as follows '
    Object data.
    '.
    
    Returns:
    A future to the transformed result of the AsyncResponseTransformer.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    NoSuchKeyException The specified key does not exist.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getObject
```
default CompletableFuture<GetObjectResponse> getObject(Consumer<GetObjectRequest.Builder> getObjectRequest,
                                                       Path destinationPath)
```
    Retrieves objects from Amazon S3. To use GET, you must have READ access to the object. If you grant READ access to the anonymous user, you can return the object without using an authorization header.
    
    An Amazon S3 bucket has no directory hierarchy such as you would find in a typical computer file system. You can, however, create a logical hierarchy by using object key names that imply a folder structure. For example, instead of naming an object sample.jpg, you can name it photos/2006/February/sample.jpg.
    
    To get an object from such a logical hierarchy, specify the full key name for the object in the GET operation. For a virtual hosted-style request example, if you have the object photos/2006/February/sample.jpg, specify the resource as /photos/2006/February/sample.jpg. For a path-style request example, if you have the object photos/2006/February/sample.jpg in the bucket named examplebucket, specify the resource as /examplebucket/photos/2006/February/sample.jpg. For more information about request types, see HTTP Host Header Bucket Specification.
    
    To distribute large files to many people, you can save bandwidth costs by using BitTorrent. For more information, see Amazon S3 Torrent. For more information about returning the ACL of an object, see GetObjectAcl.
    
    If the object you are retrieving is stored in the GLACIER or DEEP_ARCHIVE storage classes, before you can retrieve the object you must first restore a copy using . Otherwise, this operation returns an InvalidObjectStateError error. For information about restoring archived objects, see Restoring Archived Objects.
    
    Encryption request headers, like x-amz-server-side-encryption, should not be sent for GET requests if your object uses server-side encryption with CMKs stored in AWS KMS (SSE-KMS) or server-side encryption with Amazon S3–managed encryption keys (SSE-S3). If your object does use these types of keys, you’ll get an HTTP 400 BadRequest error.
    
    If you encrypt an object by using server-side encryption with customer-provided encryption keys (SSE-C) when you store the object in Amazon S3, then when you GET the object, you must use the following headers:
    - x-amz-server-side-encryption-customer-algorithm
    - x-amz-server-side-encryption-customer-key
    - x-amz-server-side-encryption-customer-key-MD5
    For more information about SSE-C, see Server-Side Encryption (Using Customer-Provided Encryption Keys).
    
    Assuming you have permission to read object tags (permission for the s3:GetObjectVersionTagging action), the response also returns the x-amz-tagging-count header that provides the count of number of tags associated with the object. You can use GetObjectTagging to retrieve the tag set associated with an object.
    
    Permissions
    
    You need the s3:GetObject permission for this operation. For more information, see Specifying Permissions in a Policy. If the object you request does not exist, the error Amazon S3 returns depends on whether you also have the s3:ListBucket permission.
    - If you have the s3:ListBucket permission on the bucket, Amazon S3 will return an HTTP status code 404 ("no such key") error.
    - If you don’t have the s3:ListBucket permission, Amazon S3 will return an HTTP status code 403 ("access denied") error.
    Versioning
    
    By default, the GET operation returns the current version of an object. To return a different version, use the versionId subresource.
    
    If the current version of the object is a delete marker, Amazon S3 behaves as if the object was deleted and includes x-amz-delete-marker: true in the response.
    
    For more information about versioning, see PutBucketVersioning.
    
    Overriding Response Header Values
    
    There are times when you want to override certain response header values in a GET response. For example, you might override the Content-Disposition response header value in your GET request.
    
    You can override values for a set of response headers using the following query parameters. These response header values are sent only on a successful request, that is, when status code 200 OK is returned. The set of headers you can override using these parameters is a subset of the headers that Amazon S3 accepts when you create an object. The response headers that you can override for the GET response are Content-Type, Content-Language, Expires, Cache-Control, Content-Disposition , and Content-Encoding. To override these header values in the GET response, you use the following request parameters.
    
    You must sign the request, either using an Authorization header or a presigned URL, when using these parameters. They cannot be used with an unsigned (anonymous) request.
    - response-content-type
    - response-content-language
    - response-expires
    - response-cache-control
    - response-content-disposition
    - response-content-encoding
    Additional Considerations about Request Headers
    
    If both of the If-Match and If-Unmodified-Since headers are present in the request as follows: If-Match condition evaluates to true, and; If-Unmodified-Since condition evaluates to false; then, S3 returns 200 OK and the data requested.
    
    If both of the If-None-Match and If-Modified-Since headers are present in the request as follows: If-None-Match condition evaluates to false, and; If-Modified-Since condition evaluates to true; then, S3 returns 304 Not Modified response code.
    
    For more information about conditional requests, see RFC 7232.
    
    The following operations are related to GetObject:
    - ListBuckets
    - GetObjectAcl
    This is a convenience which creates an instance of the GetObjectRequest.Builder avoiding the need to create one manually via GetObjectRequest.builder()
    Parameters:
    
    getObjectRequest - A Consumer that will call methods on GetObjectRequest.Builder to create a request.
    
    destinationPath - Path to file that response contents will be written to. The file must not exist or this method will throw an exception. If the file is not writable by the current user then an exception will be thrown. The service documentation for the response content is as follows '
    Object data.
    '.
    
    Returns:
    A future to the transformed result of the AsyncResponseTransformer.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    NoSuchKeyException The specified key does not exist.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getObjectAcl
```
default CompletableFuture<GetObjectAclResponse> getObjectAcl(GetObjectAclRequest getObjectAclRequest)
```
    Returns the access control list (ACL) of an object. To use this operation, you must have READ_ACP access to the object.
    
    Versioning
    
    By default, GET returns ACL information about the current version of an object. To return ACL information about a different version, use the versionId subresource.
    
    The following operations are related to GetObjectAcl:
    Parameters:
    
    getObjectAclRequest -
    
    Returns:
    A Java Future containing the result of the GetObjectAcl operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    NoSuchKeyException The specified key does not exist.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getObjectAcl
```
default CompletableFuture<GetObjectAclResponse> getObjectAcl(Consumer<GetObjectAclRequest.Builder> getObjectAclRequest)
```
    Returns the access control list (ACL) of an object. To use this operation, you must have READ_ACP access to the object.
    
    Versioning
    
    By default, GET returns ACL information about the current version of an object. To return ACL information about a different version, use the versionId subresource.
    
    The following operations are related to GetObjectAcl:
    This is a convenience which creates an instance of the GetObjectAclRequest.Builder avoiding the need to create one manually via GetObjectAclRequest.builder()
    Parameters:
    
    getObjectAclRequest - A Consumer that will call methods on GetObjectAclRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the GetObjectAcl operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    NoSuchKeyException The specified key does not exist.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getObjectLegalHold
```
default CompletableFuture<GetObjectLegalHoldResponse> getObjectLegalHold(GetObjectLegalHoldRequest getObjectLegalHoldRequest)
```
    Gets an object's current Legal Hold status. For more information, see Locking Objects.
    Parameters:
    
    getObjectLegalHoldRequest -
    
    Returns:
    A Java Future containing the result of the GetObjectLegalHold operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getObjectLegalHold
```
default CompletableFuture<GetObjectLegalHoldResponse> getObjectLegalHold(Consumer<GetObjectLegalHoldRequest.Builder> getObjectLegalHoldRequest)
```
    Gets an object's current Legal Hold status. For more information, see Locking Objects.
    
    This is a convenience which creates an instance of the GetObjectLegalHoldRequest.Builder avoiding the need to create one manually via GetObjectLegalHoldRequest.builder()
    Parameters:
    
    getObjectLegalHoldRequest - A Consumer that will call methods on GetObjectLegalHoldRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the GetObjectLegalHold operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getObjectLockConfiguration
```
default CompletableFuture<GetObjectLockConfigurationResponse> getObjectLockConfiguration(GetObjectLockConfigurationRequest getObjectLockConfigurationRequest)
```
    Gets the Object Lock configuration for a bucket. The rule specified in the Object Lock configuration will be applied by default to every new object placed in the specified bucket. For more information, see Locking Objects.
    Parameters:
    
    getObjectLockConfigurationRequest -
    
    Returns:
    A Java Future containing the result of the GetObjectLockConfiguration operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getObjectLockConfiguration
```
default CompletableFuture<GetObjectLockConfigurationResponse> getObjectLockConfiguration(Consumer<GetObjectLockConfigurationRequest.Builder> getObjectLockConfigurationRequest)
```
    Gets the Object Lock configuration for a bucket. The rule specified in the Object Lock configuration will be applied by default to every new object placed in the specified bucket. For more information, see Locking Objects.
    
    This is a convenience which creates an instance of the GetObjectLockConfigurationRequest.Builder avoiding the need to create one manually via GetObjectLockConfigurationRequest.builder()
    Parameters:
    
    getObjectLockConfigurationRequest - A Consumer that will call methods on GetObjectLockConfigurationRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the GetObjectLockConfiguration operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getObjectRetention
```
default CompletableFuture<GetObjectRetentionResponse> getObjectRetention(GetObjectRetentionRequest getObjectRetentionRequest)
```
    Retrieves an object's retention settings. For more information, see Locking Objects.
    Parameters:
    
    getObjectRetentionRequest -
    
    Returns:
    A Java Future containing the result of the GetObjectRetention operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getObjectRetention
```
default CompletableFuture<GetObjectRetentionResponse> getObjectRetention(Consumer<GetObjectRetentionRequest.Builder> getObjectRetentionRequest)
```
    Retrieves an object's retention settings. For more information, see Locking Objects.
    
    This is a convenience which creates an instance of the GetObjectRetentionRequest.Builder avoiding the need to create one manually via GetObjectRetentionRequest.builder()
    Parameters:
    
    getObjectRetentionRequest - A Consumer that will call methods on GetObjectRetentionRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the GetObjectRetention operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getObjectTagging
```
default CompletableFuture<GetObjectTaggingResponse> getObjectTagging(GetObjectTaggingRequest getObjectTaggingRequest)
```
    Returns the tag-set of an object. You send the GET request against the tagging subresource associated with the object.
    
    To use this operation, you must have permission to perform the s3:GetObjectTagging action. By default, the GET operation returns information about current version of an object. For a versioned bucket, you can have multiple versions of an object in your bucket. To retrieve tags of any other version, use the versionId query parameter. You also need permission for the s3:GetObjectVersionTagging action.
    
    By default, the bucket owner has this permission and can grant this permission to others.
    
    For information about the Amazon S3 object tagging feature, see Object Tagging.
    
    The following operation is related to GetObjectTagging:
    - PutObjectTagging
    Parameters:
    
    getObjectTaggingRequest -
    
    Returns:
    A Java Future containing the result of the GetObjectTagging operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getObjectTagging
```
default CompletableFuture<GetObjectTaggingResponse> getObjectTagging(Consumer<GetObjectTaggingRequest.Builder> getObjectTaggingRequest)
```
    Returns the tag-set of an object. You send the GET request against the tagging subresource associated with the object.
    
    To use this operation, you must have permission to perform the s3:GetObjectTagging action. By default, the GET operation returns information about current version of an object. For a versioned bucket, you can have multiple versions of an object in your bucket. To retrieve tags of any other version, use the versionId query parameter. You also need permission for the s3:GetObjectVersionTagging action.
    
    By default, the bucket owner has this permission and can grant this permission to others.
    
    For information about the Amazon S3 object tagging feature, see Object Tagging.
    
    The following operation is related to GetObjectTagging:
    - PutObjectTagging
    This is a convenience which creates an instance of the GetObjectTaggingRequest.Builder avoiding the need to create one manually via GetObjectTaggingRequest.builder()
    Parameters:
    
    getObjectTaggingRequest - A Consumer that will call methods on GetObjectTaggingRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the GetObjectTagging operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getObjectTorrent
```
default <ReturnT> CompletableFuture<ReturnT> getObjectTorrent(GetObjectTorrentRequest getObjectTorrentRequest,
                                                              AsyncResponseTransformer<GetObjectTorrentResponse,ReturnT> asyncResponseTransformer)
```
    Return torrent files from a bucket. BitTorrent can save you bandwidth when you're distributing large files. For more information about BitTorrent, see Amazon S3 Torrent.
    
    You can get torrent only for objects that are less than 5 GB in size and that are not encrypted using server-side encryption with customer-provided encryption key.
    
    To use GET, you must have READ access to the object.
    
    The following operation is related to GetObjectTorrent:
    - GetObject
    Parameters:
    
    getObjectTorrentRequest -
    
    asyncResponseTransformer - The response transformer for processing the streaming response in a non-blocking manner. See AsyncResponseTransformer for details on how this callback should be implemented and for links to precanned implementations for common scenarios like downloading to a file. The service documentation for the response content is as follows '
    A Bencoded dictionary as defined by the BitTorrent specification
    '.
    
    Returns:
    A future to the transformed result of the AsyncResponseTransformer.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getObjectTorrent
```
default <ReturnT> CompletableFuture<ReturnT> getObjectTorrent(Consumer<GetObjectTorrentRequest.Builder> getObjectTorrentRequest,
                                                              AsyncResponseTransformer<GetObjectTorrentResponse,ReturnT> asyncResponseTransformer)
```
    Return torrent files from a bucket. BitTorrent can save you bandwidth when you're distributing large files. For more information about BitTorrent, see Amazon S3 Torrent.
    
    You can get torrent only for objects that are less than 5 GB in size and that are not encrypted using server-side encryption with customer-provided encryption key.
    
    To use GET, you must have READ access to the object.
    
    The following operation is related to GetObjectTorrent:
    - GetObject
    This is a convenience which creates an instance of the GetObjectTorrentRequest.Builder avoiding the need to create one manually via GetObjectTorrentRequest.builder()
    Parameters:
    
    getObjectTorrentRequest - A Consumer that will call methods on GetObjectTorrentRequest.Builder to create a request.
    
    asyncResponseTransformer - The response transformer for processing the streaming response in a non-blocking manner. See AsyncResponseTransformer for details on how this callback should be implemented and for links to precanned implementations for common scenarios like downloading to a file. The service documentation for the response content is as follows '
    A Bencoded dictionary as defined by the BitTorrent specification
    '.
    
    Returns:
    A future to the transformed result of the AsyncResponseTransformer.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getObjectTorrent
```
default CompletableFuture<GetObjectTorrentResponse> getObjectTorrent(GetObjectTorrentRequest getObjectTorrentRequest,
                                                                     Path destinationPath)
```
    Return torrent files from a bucket. BitTorrent can save you bandwidth when you're distributing large files. For more information about BitTorrent, see Amazon S3 Torrent.
    
    You can get torrent only for objects that are less than 5 GB in size and that are not encrypted using server-side encryption with customer-provided encryption key.
    
    To use GET, you must have READ access to the object.
    
    The following operation is related to GetObjectTorrent:
    - GetObject
    Parameters:
    
    getObjectTorrentRequest -
    
    destinationPath - Path to file that response contents will be written to. The file must not exist or this method will throw an exception. If the file is not writable by the current user then an exception will be thrown. The service documentation for the response content is as follows '
    A Bencoded dictionary as defined by the BitTorrent specification
    '.
    
    Returns:
    A future to the transformed result of the AsyncResponseTransformer.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getObjectTorrent
```
default CompletableFuture<GetObjectTorrentResponse> getObjectTorrent(Consumer<GetObjectTorrentRequest.Builder> getObjectTorrentRequest,
                                                                     Path destinationPath)
```
    Return torrent files from a bucket. BitTorrent can save you bandwidth when you're distributing large files. For more information about BitTorrent, see Amazon S3 Torrent.
    
    You can get torrent only for objects that are less than 5 GB in size and that are not encrypted using server-side encryption with customer-provided encryption key.
    
    To use GET, you must have READ access to the object.
    
    The following operation is related to GetObjectTorrent:
    - GetObject
    This is a convenience which creates an instance of the GetObjectTorrentRequest.Builder avoiding the need to create one manually via GetObjectTorrentRequest.builder()
    Parameters:
    
    getObjectTorrentRequest - A Consumer that will call methods on GetObjectTorrentRequest.Builder to create a request.
    
    destinationPath - Path to file that response contents will be written to. The file must not exist or this method will throw an exception. If the file is not writable by the current user then an exception will be thrown. The service documentation for the response content is as follows '
    A Bencoded dictionary as defined by the BitTorrent specification
    '.
    
    Returns:
    A future to the transformed result of the AsyncResponseTransformer.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getPublicAccessBlock
```
default CompletableFuture<GetPublicAccessBlockResponse> getPublicAccessBlock(GetPublicAccessBlockRequest getPublicAccessBlockRequest)
```
    Retrieves the PublicAccessBlock configuration for an Amazon S3 bucket. To use this operation, you must have the s3:GetBucketPublicAccessBlock permission. For more information about Amazon S3 permissions, see Specifying Permissions in a Policy.
    
    When Amazon S3 evaluates the PublicAccessBlock configuration for a bucket or an object, it checks the PublicAccessBlock configuration for both the bucket (or the bucket that contains the object) and the bucket owner's account. If the PublicAccessBlock settings are different between the bucket and the account, Amazon S3 uses the most restrictive combination of the bucket-level and account-level settings.
    
    For more information about when Amazon S3 considers a bucket or an object public, see The Meaning of "Public".
    
    The following operations are related to GetPublicAccessBlock:
    Parameters:
    
    getPublicAccessBlockRequest -
    
    Returns:
    A Java Future containing the result of the GetPublicAccessBlock operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - getPublicAccessBlock
```
default CompletableFuture<GetPublicAccessBlockResponse> getPublicAccessBlock(Consumer<GetPublicAccessBlockRequest.Builder> getPublicAccessBlockRequest)
```
    Retrieves the PublicAccessBlock configuration for an Amazon S3 bucket. To use this operation, you must have the s3:GetBucketPublicAccessBlock permission. For more information about Amazon S3 permissions, see Specifying Permissions in a Policy.
    
    When Amazon S3 evaluates the PublicAccessBlock configuration for a bucket or an object, it checks the PublicAccessBlock configuration for both the bucket (or the bucket that contains the object) and the bucket owner's account. If the PublicAccessBlock settings are different between the bucket and the account, Amazon S3 uses the most restrictive combination of the bucket-level and account-level settings.
    
    For more information about when Amazon S3 considers a bucket or an object public, see The Meaning of "Public".
    
    The following operations are related to GetPublicAccessBlock:
    This is a convenience which creates an instance of the GetPublicAccessBlockRequest.Builder avoiding the need to create one manually via GetPublicAccessBlockRequest.builder()
    Parameters:
    
    getPublicAccessBlockRequest - A Consumer that will call methods on GetPublicAccessBlockRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the GetPublicAccessBlock operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - headBucket
```
default CompletableFuture<HeadBucketResponse> headBucket(HeadBucketRequest headBucketRequest)
```
    This operation is useful to determine if a bucket exists and you have permission to access it. The operation returns a 200 OK if the bucket exists and you have permission to access it. Otherwise, the operation might return responses such as 404 Not Found and 403 Forbidden.
    
    To use this operation, you must have permissions to perform the s3:ListBucket action. The bucket owner has this permission by default and can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.
    Parameters:
    
    headBucketRequest -
    
    Returns:
    A Java Future containing the result of the HeadBucket operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    NoSuchBucketException The specified bucket does not exist.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - headBucket
```
default CompletableFuture<HeadBucketResponse> headBucket(Consumer<HeadBucketRequest.Builder> headBucketRequest)
```
    This operation is useful to determine if a bucket exists and you have permission to access it. The operation returns a 200 OK if the bucket exists and you have permission to access it. Otherwise, the operation might return responses such as 404 Not Found and 403 Forbidden.
    
    To use this operation, you must have permissions to perform the s3:ListBucket action. The bucket owner has this permission by default and can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.
    
    This is a convenience which creates an instance of the HeadBucketRequest.Builder avoiding the need to create one manually via HeadBucketRequest.builder()
    Parameters:
    
    headBucketRequest - A Consumer that will call methods on HeadBucketRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the HeadBucket operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    NoSuchBucketException The specified bucket does not exist.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - headObject
```
default CompletableFuture<HeadObjectResponse> headObject(HeadObjectRequest headObjectRequest)
```
    The HEAD operation retrieves metadata from an object without returning the object itself. This operation is useful if you're only interested in an object's metadata. To use HEAD, you must have READ access to the object.
    
    A HEAD request has the same options as a GET operation on an object. The response is identical to the GET response except that there is no response body.
    
    If you encrypt an object by using server-side encryption with customer-provided encryption keys (SSE-C) when you store the object in Amazon S3, then when you retrieve the metadata from the object, you must use the following headers:
    - x-amz-server-side-encryption-customer-algorithm
    - x-amz-server-side-encryption-customer-key
    - x-amz-server-side-encryption-customer-key-MD5
    For more information about SSE-C, see Server-Side Encryption (Using Customer-Provided Encryption Keys).
    
    Encryption request headers, like x-amz-server-side-encryption, should not be sent for GET requests if your object uses server-side encryption with CMKs stored in AWS KMS (SSE-KMS) or server-side encryption with Amazon S3–managed encryption keys (SSE-S3). If your object does use these types of keys, you’ll get an HTTP 400 BadRequest error.
    
    Request headers are limited to 8 KB in size. For more information, see Common Request Headers.
    
    Consider the following when using request headers:
    - Consideration 1 – If both of the If-Match and If-Unmodified-Since headers are present in the request as follows:
      
      If-Match condition evaluates to true, and;
      
      If-Unmodified-Since condition evaluates to false;
      
      Then Amazon S3 returns 200 OK and the data requested.
    - Consideration 2 – If both of the If-None-Match and If-Modified-Since headers are present in the request as follows:
      
      If-None-Match condition evaluates to false, and;
      
      If-Modified-Since condition evaluates to true;
      
      Then Amazon S3 returns the 304 Not Modified response code.
    For more information about conditional requests, see RFC 7232.
    
    Permissions
    
    You need the s3:GetObject permission for this operation. For more information, see Specifying Permissions in a Policy. If the object you request does not exist, the error Amazon S3 returns depends on whether you also have the s3:ListBucket permission.
    - If you have the s3:ListBucket permission on the bucket, Amazon S3 returns an HTTP status code 404 ("no such key") error.
    - If you don’t have the s3:ListBucket permission, Amazon S3 returns an HTTP status code 403 ("access denied") error.
    The following operation is related to HeadObject:
    - GetObject
    Parameters:
    
    headObjectRequest -
    
    Returns:
    A Java Future containing the result of the HeadObject operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    NoSuchKeyException The specified key does not exist.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - headObject
```
default CompletableFuture<HeadObjectResponse> headObject(Consumer<HeadObjectRequest.Builder> headObjectRequest)
```
    The HEAD operation retrieves metadata from an object without returning the object itself. This operation is useful if you're only interested in an object's metadata. To use HEAD, you must have READ access to the object.
    
    A HEAD request has the same options as a GET operation on an object. The response is identical to the GET response except that there is no response body.
    
    If you encrypt an object by using server-side encryption with customer-provided encryption keys (SSE-C) when you store the object in Amazon S3, then when you retrieve the metadata from the object, you must use the following headers:
    - x-amz-server-side-encryption-customer-algorithm
    - x-amz-server-side-encryption-customer-key
    - x-amz-server-side-encryption-customer-key-MD5
    For more information about SSE-C, see Server-Side Encryption (Using Customer-Provided Encryption Keys).
    
    Encryption request headers, like x-amz-server-side-encryption, should not be sent for GET requests if your object uses server-side encryption with CMKs stored in AWS KMS (SSE-KMS) or server-side encryption with Amazon S3–managed encryption keys (SSE-S3). If your object does use these types of keys, you’ll get an HTTP 400 BadRequest error.
    
    Request headers are limited to 8 KB in size. For more information, see Common Request Headers.
    
    Consider the following when using request headers:
    - Consideration 1 – If both of the If-Match and If-Unmodified-Since headers are present in the request as follows:
      
      If-Match condition evaluates to true, and;
      
      If-Unmodified-Since condition evaluates to false;
      
      Then Amazon S3 returns 200 OK and the data requested.
    - Consideration 2 – If both of the If-None-Match and If-Modified-Since headers are present in the request as follows:
      
      If-None-Match condition evaluates to false, and;
      
      If-Modified-Since condition evaluates to true;
      
      Then Amazon S3 returns the 304 Not Modified response code.
    For more information about conditional requests, see RFC 7232.
    
    Permissions
    
    You need the s3:GetObject permission for this operation. For more information, see Specifying Permissions in a Policy. If the object you request does not exist, the error Amazon S3 returns depends on whether you also have the s3:ListBucket permission.
    - If you have the s3:ListBucket permission on the bucket, Amazon S3 returns an HTTP status code 404 ("no such key") error.
    - If you don’t have the s3:ListBucket permission, Amazon S3 returns an HTTP status code 403 ("access denied") error.
    The following operation is related to HeadObject:
    - GetObject
    This is a convenience which creates an instance of the HeadObjectRequest.Builder avoiding the need to create one manually via HeadObjectRequest.builder()
    Parameters:
    
    headObjectRequest - A Consumer that will call methods on HeadObjectRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the HeadObject operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    NoSuchKeyException The specified key does not exist.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - listBucketAnalyticsConfigurations
```
default CompletableFuture<ListBucketAnalyticsConfigurationsResponse> listBucketAnalyticsConfigurations(ListBucketAnalyticsConfigurationsRequest listBucketAnalyticsConfigurationsRequest)
```
    Lists the analytics configurations for the bucket. You can have up to 1,000 analytics configurations per bucket.
    
    This operation supports list pagination and does not return more than 100 configurations at a time. You should always check the IsTruncated element in the response. If there are no more configurations to list, IsTruncated is set to false. If there are more configurations to list, IsTruncated is set to true, and there will be a value in NextContinuationToken. You use the NextContinuationToken value to continue the pagination of the list by passing the value in continuation-token in the request to GET the next page.
    
    To use this operation, you must have permissions to perform the s3:GetAnalyticsConfiguration action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.
    
    For information about Amazon S3 analytics feature, see Amazon S3 Analytics – Storage Class Analysis.
    
    The following operations are related to ListBucketAnalyticsConfigurations:
    Parameters:
    
    listBucketAnalyticsConfigurationsRequest -
    
    Returns:
    A Java Future containing the result of the ListBucketAnalyticsConfigurations operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - listBucketAnalyticsConfigurations
```
default CompletableFuture<ListBucketAnalyticsConfigurationsResponse> listBucketAnalyticsConfigurations(Consumer<ListBucketAnalyticsConfigurationsRequest.Builder> listBucketAnalyticsConfigurationsRequest)
```
    Lists the analytics configurations for the bucket. You can have up to 1,000 analytics configurations per bucket.
    
    This operation supports list pagination and does not return more than 100 configurations at a time. You should always check the IsTruncated element in the response. If there are no more configurations to list, IsTruncated is set to false. If there are more configurations to list, IsTruncated is set to true, and there will be a value in NextContinuationToken. You use the NextContinuationToken value to continue the pagination of the list by passing the value in continuation-token in the request to GET the next page.
    
    To use this operation, you must have permissions to perform the s3:GetAnalyticsConfiguration action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.
    
    For information about Amazon S3 analytics feature, see Amazon S3 Analytics – Storage Class Analysis.
    
    The following operations are related to ListBucketAnalyticsConfigurations:
    This is a convenience which creates an instance of the ListBucketAnalyticsConfigurationsRequest.Builder avoiding the need to create one manually via ListBucketAnalyticsConfigurationsRequest.builder()
    Parameters:
    
    listBucketAnalyticsConfigurationsRequest - A Consumer that will call methods on ListBucketAnalyticsConfigurationsRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the ListBucketAnalyticsConfigurations operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - listBucketInventoryConfigurations
```
default CompletableFuture<ListBucketInventoryConfigurationsResponse> listBucketInventoryConfigurations(ListBucketInventoryConfigurationsRequest listBucketInventoryConfigurationsRequest)
```
    Returns a list of inventory configurations for the bucket. You can have up to 1,000 analytics configurations per bucket.
    
    This operation supports list pagination and does not return more than 100 configurations at a time. Always check the IsTruncated element in the response. If there are no more configurations to list, IsTruncated is set to false. If there are more configurations to list, IsTruncated is set to true, and there is a value in NextContinuationToken. You use the NextContinuationToken value to continue the pagination of the list by passing the value in continuation-token in the request to GET the next page.
    
    To use this operation, you must have permissions to perform the s3:GetInventoryConfiguration action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.
    
    For information about the Amazon S3 inventory feature, see Amazon S3 Inventory
    
    The following operations are related to ListBucketInventoryConfigurations:
    Parameters:
    
    listBucketInventoryConfigurationsRequest -
    
    Returns:
    A Java Future containing the result of the ListBucketInventoryConfigurations operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - listBucketInventoryConfigurations
```
default CompletableFuture<ListBucketInventoryConfigurationsResponse> listBucketInventoryConfigurations(Consumer<ListBucketInventoryConfigurationsRequest.Builder> listBucketInventoryConfigurationsRequest)
```
    Returns a list of inventory configurations for the bucket. You can have up to 1,000 analytics configurations per bucket.
    
    This operation supports list pagination and does not return more than 100 configurations at a time. Always check the IsTruncated element in the response. If there are no more configurations to list, IsTruncated is set to false. If there are more configurations to list, IsTruncated is set to true, and there is a value in NextContinuationToken. You use the NextContinuationToken value to continue the pagination of the list by passing the value in continuation-token in the request to GET the next page.
    
    To use this operation, you must have permissions to perform the s3:GetInventoryConfiguration action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.
    
    For information about the Amazon S3 inventory feature, see Amazon S3 Inventory
    
    The following operations are related to ListBucketInventoryConfigurations:
    This is a convenience which creates an instance of the ListBucketInventoryConfigurationsRequest.Builder avoiding the need to create one manually via ListBucketInventoryConfigurationsRequest.builder()
    Parameters:
    
    listBucketInventoryConfigurationsRequest - A Consumer that will call methods on ListBucketInventoryConfigurationsRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the ListBucketInventoryConfigurations operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - listBucketMetricsConfigurations
```
default CompletableFuture<ListBucketMetricsConfigurationsResponse> listBucketMetricsConfigurations(ListBucketMetricsConfigurationsRequest listBucketMetricsConfigurationsRequest)
```
    Lists the metrics configurations for the bucket. The metrics configurations are only for the request metrics of the bucket and do not provide information on daily storage metrics. You can have up to 1,000 configurations per bucket.
    
    This operation supports list pagination and does not return more than 100 configurations at a time. Always check the IsTruncated element in the response. If there are no more configurations to list, IsTruncated is set to false. If there are more configurations to list, IsTruncated is set to true, and there is a value in NextContinuationToken. You use the NextContinuationToken value to continue the pagination of the list by passing the value in continuation-token in the request to GET the next page.
    
    To use this operation, you must have permissions to perform the s3:GetMetricsConfiguration action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.
    
    For more information about metrics configurations and CloudWatch request metrics, see Monitoring Metrics with Amazon CloudWatch.
    
    The following operations are related to ListBucketMetricsConfigurations:
    Parameters:
    
    listBucketMetricsConfigurationsRequest -
    
    Returns:
    A Java Future containing the result of the ListBucketMetricsConfigurations operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - listBucketMetricsConfigurations
```
default CompletableFuture<ListBucketMetricsConfigurationsResponse> listBucketMetricsConfigurations(Consumer<ListBucketMetricsConfigurationsRequest.Builder> listBucketMetricsConfigurationsRequest)
```
    Lists the metrics configurations for the bucket. The metrics configurations are only for the request metrics of the bucket and do not provide information on daily storage metrics. You can have up to 1,000 configurations per bucket.
    
    This operation supports list pagination and does not return more than 100 configurations at a time. Always check the IsTruncated element in the response. If there are no more configurations to list, IsTruncated is set to false. If there are more configurations to list, IsTruncated is set to true, and there is a value in NextContinuationToken. You use the NextContinuationToken value to continue the pagination of the list by passing the value in continuation-token in the request to GET the next page.
    
    To use this operation, you must have permissions to perform the s3:GetMetricsConfiguration action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.
    
    For more information about metrics configurations and CloudWatch request metrics, see Monitoring Metrics with Amazon CloudWatch.
    
    The following operations are related to ListBucketMetricsConfigurations:
    This is a convenience which creates an instance of the ListBucketMetricsConfigurationsRequest.Builder avoiding the need to create one manually via ListBucketMetricsConfigurationsRequest.builder()
    Parameters:
    
    listBucketMetricsConfigurationsRequest - A Consumer that will call methods on ListBucketMetricsConfigurationsRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the ListBucketMetricsConfigurations operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - listBuckets
```
default CompletableFuture<ListBucketsResponse> listBuckets(ListBucketsRequest listBucketsRequest)
```
    Returns a list of all buckets owned by the authenticated sender of the request.
    Parameters:
    
    listBucketsRequest -
    
    Returns:
    A Java Future containing the result of the ListBuckets operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - listBuckets
```
default CompletableFuture<ListBucketsResponse> listBuckets(Consumer<ListBucketsRequest.Builder> listBucketsRequest)
```
    Returns a list of all buckets owned by the authenticated sender of the request.
    
    This is a convenience which creates an instance of the ListBucketsRequest.Builder avoiding the need to create one manually via ListBucketsRequest.builder()
    Parameters:
    
    listBucketsRequest - A Consumer that will call methods on ListBucketsRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the ListBuckets operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - listBuckets
```
default CompletableFuture<ListBucketsResponse> listBuckets()
```
    Returns a list of all buckets owned by the authenticated sender of the request.
    Returns:
    A Java Future containing the result of the ListBuckets operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - listMultipartUploads
```
default CompletableFuture<ListMultipartUploadsResponse> listMultipartUploads(ListMultipartUploadsRequest listMultipartUploadsRequest)
```
    This operation lists in-progress multipart uploads. An in-progress multipart upload is a multipart upload that has been initiated using the Initiate Multipart Upload request, but has not yet been completed or aborted.
    
    This operation returns at most 1,000 multipart uploads in the response. 1,000 multipart uploads is the maximum number of uploads a response can include, which is also the default value. You can further limit the number of uploads in a response by specifying the max-uploads parameter in the response. If additional multipart uploads satisfy the list criteria, the response will contain an IsTruncated element with the value true. To list the additional multipart uploads, use the key-marker and upload-id-marker request parameters.
    
    In the response, the uploads are sorted by key. If your application has initiated more than one multipart upload using the same object key, then uploads in the response are first sorted by key. Additionally, uploads are sorted in ascending order within each key by the upload initiation time.
    
    For more information on multipart uploads, see Uploading Objects Using Multipart Upload.
    
    For information on permissions required to use the multipart upload API, see Multipart Upload API and Permissions.
    
    The following operations are related to ListMultipartUploads:
    Parameters:
    
    listMultipartUploadsRequest -
    
    Returns:
    A Java Future containing the result of the ListMultipartUploads operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - listMultipartUploads
```
default CompletableFuture<ListMultipartUploadsResponse> listMultipartUploads(Consumer<ListMultipartUploadsRequest.Builder> listMultipartUploadsRequest)
```
    This operation lists in-progress multipart uploads. An in-progress multipart upload is a multipart upload that has been initiated using the Initiate Multipart Upload request, but has not yet been completed or aborted.
    
    This operation returns at most 1,000 multipart uploads in the response. 1,000 multipart uploads is the maximum number of uploads a response can include, which is also the default value. You can further limit the number of uploads in a response by specifying the max-uploads parameter in the response. If additional multipart uploads satisfy the list criteria, the response will contain an IsTruncated element with the value true. To list the additional multipart uploads, use the key-marker and upload-id-marker request parameters.
    
    In the response, the uploads are sorted by key. If your application has initiated more than one multipart upload using the same object key, then uploads in the response are first sorted by key. Additionally, uploads are sorted in ascending order within each key by the upload initiation time.
    
    For more information on multipart uploads, see Uploading Objects Using Multipart Upload.
    
    For information on permissions required to use the multipart upload API, see Multipart Upload API and Permissions.
    
    The following operations are related to ListMultipartUploads:
    This is a convenience which creates an instance of the ListMultipartUploadsRequest.Builder avoiding the need to create one manually via ListMultipartUploadsRequest.builder()
    Parameters:
    
    listMultipartUploadsRequest - A Consumer that will call methods on ListMultipartUploadsRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the ListMultipartUploads operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - listMultipartUploadsPaginator
```
default ListMultipartUploadsPublisher listMultipartUploadsPaginator(ListMultipartUploadsRequest listMultipartUploadsRequest)
```
    This operation lists in-progress multipart uploads. An in-progress multipart upload is a multipart upload that has been initiated using the Initiate Multipart Upload request, but has not yet been completed or aborted.
    
    This operation returns at most 1,000 multipart uploads in the response. 1,000 multipart uploads is the maximum number of uploads a response can include, which is also the default value. You can further limit the number of uploads in a response by specifying the max-uploads parameter in the response. If additional multipart uploads satisfy the list criteria, the response will contain an IsTruncated element with the value true. To list the additional multipart uploads, use the key-marker and upload-id-marker request parameters.
    
    In the response, the uploads are sorted by key. If your application has initiated more than one multipart upload using the same object key, then uploads in the response are first sorted by key. Additionally, uploads are sorted in ascending order within each key by the upload initiation time.
    
    For more information on multipart uploads, see Uploading Objects Using Multipart Upload.
    
    For information on permissions required to use the multipart upload API, see Multipart Upload API and Permissions.
    
    The following operations are related to ListMultipartUploads:
    This is a variant of listMultipartUploads(software.amazon.awssdk.services.s3.model.ListMultipartUploadsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.
    
    When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.
    
    The following are few ways to use the response class:
    1) Using the subscribe helper method
```
 
 software.amazon.awssdk.services.s3.paginators.ListMultipartUploadsPublisher publisher = client.listMultipartUploadsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
 
 
```
    2) Using a custom subscriber
```
 
 software.amazon.awssdk.services.s3.paginators.ListMultipartUploadsPublisher publisher = client.listMultipartUploadsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.s3.model.ListMultipartUploadsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.s3.model.ListMultipartUploadsResponse response) { //... };
 });
 
```
    As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.
    Note: If you prefer to have control on service calls, use the listMultipartUploads(software.amazon.awssdk.services.s3.model.ListMultipartUploadsRequest) operation.
    Parameters:
    
    listMultipartUploadsRequest -
    
    Returns:
    A custom publisher that can be subscribed to request a stream of response pages.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - listMultipartUploadsPaginator
```
default ListMultipartUploadsPublisher listMultipartUploadsPaginator(Consumer<ListMultipartUploadsRequest.Builder> listMultipartUploadsRequest)
```
    This operation lists in-progress multipart uploads. An in-progress multipart upload is a multipart upload that has been initiated using the Initiate Multipart Upload request, but has not yet been completed or aborted.
    
    This operation returns at most 1,000 multipart uploads in the response. 1,000 multipart uploads is the maximum number of uploads a response can include, which is also the default value. You can further limit the number of uploads in a response by specifying the max-uploads parameter in the response. If additional multipart uploads satisfy the list criteria, the response will contain an IsTruncated element with the value true. To list the additional multipart uploads, use the key-marker and upload-id-marker request parameters.
    
    In the response, the uploads are sorted by key. If your application has initiated more than one multipart upload using the same object key, then uploads in the response are first sorted by key. Additionally, uploads are sorted in ascending order within each key by the upload initiation time.
    
    For more information on multipart uploads, see Uploading Objects Using Multipart Upload.
    
    For information on permissions required to use the multipart upload API, see Multipart Upload API and Permissions.
    
    The following operations are related to ListMultipartUploads:
    This is a variant of listMultipartUploads(software.amazon.awssdk.services.s3.model.ListMultipartUploadsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.
    
    When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.
    
    The following are few ways to use the response class:
    1) Using the subscribe helper method
```
 
 software.amazon.awssdk.services.s3.paginators.ListMultipartUploadsPublisher publisher = client.listMultipartUploadsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
 
 
```
    2) Using a custom subscriber
```
 
 software.amazon.awssdk.services.s3.paginators.ListMultipartUploadsPublisher publisher = client.listMultipartUploadsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.s3.model.ListMultipartUploadsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.s3.model.ListMultipartUploadsResponse response) { //... };
 });
 
```
    As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.
    Note: If you prefer to have control on service calls, use the listMultipartUploads(software.amazon.awssdk.services.s3.model.ListMultipartUploadsRequest) operation.
    
    This is a convenience which creates an instance of the ListMultipartUploadsRequest.Builder avoiding the need to create one manually via ListMultipartUploadsRequest.builder()
    Parameters:
    
    listMultipartUploadsRequest - A Consumer that will call methods on ListMultipartUploadsRequest.Builder to create a request.
    
    Returns:
    A custom publisher that can be subscribed to request a stream of response pages.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - listObjectVersions
```
default CompletableFuture<ListObjectVersionsResponse> listObjectVersions(ListObjectVersionsRequest listObjectVersionsRequest)
```
    Returns metadata about all of the versions of objects in a bucket. You can also use request parameters as selection criteria to return metadata about a subset of all the object versions.
    
    A 200 OK response can contain valid or invalid XML. Make sure to design your application to parse the contents of the response and handle it appropriately.
    
    To use this operation, you must have READ access to the bucket.
    
    The following operations are related to ListObjectVersions:
    Parameters:
    
    listObjectVersionsRequest -
    
    Returns:
    A Java Future containing the result of the ListObjectVersions operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - listObjectVersions
```
default CompletableFuture<ListObjectVersionsResponse> listObjectVersions(Consumer<ListObjectVersionsRequest.Builder> listObjectVersionsRequest)
```
    Returns metadata about all of the versions of objects in a bucket. You can also use request parameters as selection criteria to return metadata about a subset of all the object versions.
    
    A 200 OK response can contain valid or invalid XML. Make sure to design your application to parse the contents of the response and handle it appropriately.
    
    To use this operation, you must have READ access to the bucket.
    
    The following operations are related to ListObjectVersions:
    This is a convenience which creates an instance of the ListObjectVersionsRequest.Builder avoiding the need to create one manually via ListObjectVersionsRequest.builder()
    Parameters:
    
    listObjectVersionsRequest - A Consumer that will call methods on ListObjectVersionsRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the ListObjectVersions operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - listObjectVersionsPaginator
```
default ListObjectVersionsPublisher listObjectVersionsPaginator(ListObjectVersionsRequest listObjectVersionsRequest)
```
    Returns metadata about all of the versions of objects in a bucket. You can also use request parameters as selection criteria to return metadata about a subset of all the object versions.
    
    A 200 OK response can contain valid or invalid XML. Make sure to design your application to parse the contents of the response and handle it appropriately.
    
    To use this operation, you must have READ access to the bucket.
    
    The following operations are related to ListObjectVersions:
    This is a variant of listObjectVersions(software.amazon.awssdk.services.s3.model.ListObjectVersionsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.
    
    When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.
    
    The following are few ways to use the response class:
    1) Using the subscribe helper method
```
 
 software.amazon.awssdk.services.s3.paginators.ListObjectVersionsPublisher publisher = client.listObjectVersionsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
 
 
```
    2) Using a custom subscriber
```
 
 software.amazon.awssdk.services.s3.paginators.ListObjectVersionsPublisher publisher = client.listObjectVersionsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.s3.model.ListObjectVersionsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.s3.model.ListObjectVersionsResponse response) { //... };
 });
 
```
    As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.
    Note: If you prefer to have control on service calls, use the listObjectVersions(software.amazon.awssdk.services.s3.model.ListObjectVersionsRequest) operation.
    Parameters:
    
    listObjectVersionsRequest -
    
    Returns:
    A custom publisher that can be subscribed to request a stream of response pages.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - listObjectVersionsPaginator
```
default ListObjectVersionsPublisher listObjectVersionsPaginator(Consumer<ListObjectVersionsRequest.Builder> listObjectVersionsRequest)
```
    Returns metadata about all of the versions of objects in a bucket. You can also use request parameters as selection criteria to return metadata about a subset of all the object versions.
    
    A 200 OK response can contain valid or invalid XML. Make sure to design your application to parse the contents of the response and handle it appropriately.
    
    To use this operation, you must have READ access to the bucket.
    
    The following operations are related to ListObjectVersions:
    This is a variant of listObjectVersions(software.amazon.awssdk.services.s3.model.ListObjectVersionsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.
    
    When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.
    
    The following are few ways to use the response class:
    1) Using the subscribe helper method
```
 
 software.amazon.awssdk.services.s3.paginators.ListObjectVersionsPublisher publisher = client.listObjectVersionsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
 
 
```
    2) Using a custom subscriber
```
 
 software.amazon.awssdk.services.s3.paginators.ListObjectVersionsPublisher publisher = client.listObjectVersionsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.s3.model.ListObjectVersionsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.s3.model.ListObjectVersionsResponse response) { //... };
 });
 
```
    As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.
    Note: If you prefer to have control on service calls, use the listObjectVersions(software.amazon.awssdk.services.s3.model.ListObjectVersionsRequest) operation.
    
    This is a convenience which creates an instance of the ListObjectVersionsRequest.Builder avoiding the need to create one manually via ListObjectVersionsRequest.builder()
    Parameters:
    
    listObjectVersionsRequest - A Consumer that will call methods on ListObjectVersionsRequest.Builder to create a request.
    
    Returns:
    A custom publisher that can be subscribed to request a stream of response pages.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - listObjects
```
default CompletableFuture<ListObjectsResponse> listObjects(ListObjectsRequest listObjectsRequest)
```
    Returns some or all (up to 1,000) of the objects in a bucket. You can use the request parameters as selection criteria to return a subset of the objects in a bucket. A 200 OK response can contain valid or invalid XML. Be sure to design your application to parse the contents of the response and handle it appropriately.
    
    This API has been revised. We recommend that you use the newer version, ListObjectsV2, when developing applications. For backward compatibility, Amazon S3 continues to support ListObjects.
    
    The following operations are related to ListObjects:
    Parameters:
    
    listObjectsRequest -
    
    Returns:
    A Java Future containing the result of the ListObjects operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    NoSuchBucketException The specified bucket does not exist.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - listObjects
```
default CompletableFuture<ListObjectsResponse> listObjects(Consumer<ListObjectsRequest.Builder> listObjectsRequest)
```
    Returns some or all (up to 1,000) of the objects in a bucket. You can use the request parameters as selection criteria to return a subset of the objects in a bucket. A 200 OK response can contain valid or invalid XML. Be sure to design your application to parse the contents of the response and handle it appropriately.
    
    This API has been revised. We recommend that you use the newer version, ListObjectsV2, when developing applications. For backward compatibility, Amazon S3 continues to support ListObjects.
    
    The following operations are related to ListObjects:
    This is a convenience which creates an instance of the ListObjectsRequest.Builder avoiding the need to create one manually via ListObjectsRequest.builder()
    Parameters:
    
    listObjectsRequest - A Consumer that will call methods on ListObjectsRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the ListObjects operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    NoSuchBucketException The specified bucket does not exist.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - listObjectsV2
```
default CompletableFuture<ListObjectsV2Response> listObjectsV2(ListObjectsV2Request listObjectsV2Request)
```
    Returns some or all (up to 1,000) of the objects in a bucket. You can use the request parameters as selection criteria to return a subset of the objects in a bucket. A 200 OK response can contain valid or invalid XML. Make sure to design your application to parse the contents of the response and handle it appropriately.
    
    To use this operation, you must have READ access to the bucket.
    
    To use this operation in an AWS Identity and Access Management (IAM) policy, you must have permissions to perform the s3:ListBucket action. The bucket owner has this permission by default and can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.
    
    This section describes the latest revision of the API. We recommend that you use this revised API for application development. For backward compatibility, Amazon S3 continues to support the prior version of this API, ListObjects.
    
    To get a list of your buckets, see ListBuckets.
    
    The following operations are related to ListObjectsV2:
    Parameters:
    
    listObjectsV2Request -
    
    Returns:
    A Java Future containing the result of the ListObjectsV2 operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    NoSuchBucketException The specified bucket does not exist.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - listObjectsV2
```
default CompletableFuture<ListObjectsV2Response> listObjectsV2(Consumer<ListObjectsV2Request.Builder> listObjectsV2Request)
```
    Returns some or all (up to 1,000) of the objects in a bucket. You can use the request parameters as selection criteria to return a subset of the objects in a bucket. A 200 OK response can contain valid or invalid XML. Make sure to design your application to parse the contents of the response and handle it appropriately.
    
    To use this operation, you must have READ access to the bucket.
    
    To use this operation in an AWS Identity and Access Management (IAM) policy, you must have permissions to perform the s3:ListBucket action. The bucket owner has this permission by default and can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.
    
    This section describes the latest revision of the API. We recommend that you use this revised API for application development. For backward compatibility, Amazon S3 continues to support the prior version of this API, ListObjects.
    
    To get a list of your buckets, see ListBuckets.
    
    The following operations are related to ListObjectsV2:
    This is a convenience which creates an instance of the ListObjectsV2Request.Builder avoiding the need to create one manually via ListObjectsV2Request.builder()
    Parameters:
    
    listObjectsV2Request - A Consumer that will call methods on ListObjectsV2Request.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the ListObjectsV2 operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    NoSuchBucketException The specified bucket does not exist.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - listObjectsV2Paginator
```
default ListObjectsV2Publisher listObjectsV2Paginator(ListObjectsV2Request listObjectsV2Request)
```
    Returns some or all (up to 1,000) of the objects in a bucket. You can use the request parameters as selection criteria to return a subset of the objects in a bucket. A 200 OK response can contain valid or invalid XML. Make sure to design your application to parse the contents of the response and handle it appropriately.
    
    To use this operation, you must have READ access to the bucket.
    
    To use this operation in an AWS Identity and Access Management (IAM) policy, you must have permissions to perform the s3:ListBucket action. The bucket owner has this permission by default and can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.
    
    This section describes the latest revision of the API. We recommend that you use this revised API for application development. For backward compatibility, Amazon S3 continues to support the prior version of this API, ListObjects.
    
    To get a list of your buckets, see ListBuckets.
    
    The following operations are related to ListObjectsV2:
    This is a variant of listObjectsV2(software.amazon.awssdk.services.s3.model.ListObjectsV2Request) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.
    
    When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.
    
    The following are few ways to use the response class:
    1) Using the subscribe helper method
```
 
 software.amazon.awssdk.services.s3.paginators.ListObjectsV2Publisher publisher = client.listObjectsV2Paginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
 
 
```
    2) Using a custom subscriber
```
 
 software.amazon.awssdk.services.s3.paginators.ListObjectsV2Publisher publisher = client.listObjectsV2Paginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.s3.model.ListObjectsV2Response>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.s3.model.ListObjectsV2Response response) { //... };
 });
 
```
    As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.
    Note: If you prefer to have control on service calls, use the listObjectsV2(software.amazon.awssdk.services.s3.model.ListObjectsV2Request) operation.
    Parameters:
    
    listObjectsV2Request -
    
    Returns:
    A custom publisher that can be subscribed to request a stream of response pages.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    NoSuchBucketException The specified bucket does not exist.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - listObjectsV2Paginator
```
default ListObjectsV2Publisher listObjectsV2Paginator(Consumer<ListObjectsV2Request.Builder> listObjectsV2Request)
```
    Returns some or all (up to 1,000) of the objects in a bucket. You can use the request parameters as selection criteria to return a subset of the objects in a bucket. A 200 OK response can contain valid or invalid XML. Make sure to design your application to parse the contents of the response and handle it appropriately.
    
    To use this operation, you must have READ access to the bucket.
    
    To use this operation in an AWS Identity and Access Management (IAM) policy, you must have permissions to perform the s3:ListBucket action. The bucket owner has this permission by default and can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.
    
    This section describes the latest revision of the API. We recommend that you use this revised API for application development. For backward compatibility, Amazon S3 continues to support the prior version of this API, ListObjects.
    
    To get a list of your buckets, see ListBuckets.
    
    The following operations are related to ListObjectsV2:
    This is a variant of listObjectsV2(software.amazon.awssdk.services.s3.model.ListObjectsV2Request) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.
    
    When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.
    
    The following are few ways to use the response class:
    1) Using the subscribe helper method
```
 
 software.amazon.awssdk.services.s3.paginators.ListObjectsV2Publisher publisher = client.listObjectsV2Paginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
 
 
```
    2) Using a custom subscriber
```
 
 software.amazon.awssdk.services.s3.paginators.ListObjectsV2Publisher publisher = client.listObjectsV2Paginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.s3.model.ListObjectsV2Response>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.s3.model.ListObjectsV2Response response) { //... };
 });
 
```
    As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.
    Note: If you prefer to have control on service calls, use the listObjectsV2(software.amazon.awssdk.services.s3.model.ListObjectsV2Request) operation.
    
    This is a convenience which creates an instance of the ListObjectsV2Request.Builder avoiding the need to create one manually via ListObjectsV2Request.builder()
    Parameters:
    
    listObjectsV2Request - A Consumer that will call methods on ListObjectsV2Request.Builder to create a request.
    
    Returns:
    A custom publisher that can be subscribed to request a stream of response pages.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    NoSuchBucketException The specified bucket does not exist.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - listParts
```
default CompletableFuture<ListPartsResponse> listParts(ListPartsRequest listPartsRequest)
```
    Lists the parts that have been uploaded for a specific multipart upload. This operation must include the upload ID, which you obtain by sending the initiate multipart upload request (see CreateMultipartUpload). This request returns a maximum of 1,000 uploaded parts. The default number of parts returned is 1,000 parts. You can restrict the number of parts returned by specifying the max-parts request parameter. If your multipart upload consists of more than 1,000 parts, the response returns an IsTruncated field with the value of true, and a NextPartNumberMarker element. In subsequent ListParts requests you can include the part-number-marker query string parameter and set its value to the NextPartNumberMarker field value from the previous response.
    
    For more information on multipart uploads, see Uploading Objects Using Multipart Upload.
    
    For information on permissions required to use the multipart upload API, see Multipart Upload API and Permissions.
    
    The following operations are related to ListParts:
    Parameters:
    
    listPartsRequest -
    
    Returns:
    A Java Future containing the result of the ListParts operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - listParts
```
default CompletableFuture<ListPartsResponse> listParts(Consumer<ListPartsRequest.Builder> listPartsRequest)
```
    Lists the parts that have been uploaded for a specific multipart upload. This operation must include the upload ID, which you obtain by sending the initiate multipart upload request (see CreateMultipartUpload). This request returns a maximum of 1,000 uploaded parts. The default number of parts returned is 1,000 parts. You can restrict the number of parts returned by specifying the max-parts request parameter. If your multipart upload consists of more than 1,000 parts, the response returns an IsTruncated field with the value of true, and a NextPartNumberMarker element. In subsequent ListParts requests you can include the part-number-marker query string parameter and set its value to the NextPartNumberMarker field value from the previous response.
    
    For more information on multipart uploads, see Uploading Objects Using Multipart Upload.
    
    For information on permissions required to use the multipart upload API, see Multipart Upload API and Permissions.
    
    The following operations are related to ListParts:
    This is a convenience which creates an instance of the ListPartsRequest.Builder avoiding the need to create one manually via ListPartsRequest.builder()
    Parameters:
    
    listPartsRequest - A Consumer that will call methods on ListPartsRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the ListParts operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - listPartsPaginator
```
default ListPartsPublisher listPartsPaginator(ListPartsRequest listPartsRequest)
```
    Lists the parts that have been uploaded for a specific multipart upload. This operation must include the upload ID, which you obtain by sending the initiate multipart upload request (see CreateMultipartUpload). This request returns a maximum of 1,000 uploaded parts. The default number of parts returned is 1,000 parts. You can restrict the number of parts returned by specifying the max-parts request parameter. If your multipart upload consists of more than 1,000 parts, the response returns an IsTruncated field with the value of true, and a NextPartNumberMarker element. In subsequent ListParts requests you can include the part-number-marker query string parameter and set its value to the NextPartNumberMarker field value from the previous response.
    
    For more information on multipart uploads, see Uploading Objects Using Multipart Upload.
    
    For information on permissions required to use the multipart upload API, see Multipart Upload API and Permissions.
    
    The following operations are related to ListParts:
    This is a variant of listParts(software.amazon.awssdk.services.s3.model.ListPartsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.
    
    When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.
    
    The following are few ways to use the response class:
    1) Using the subscribe helper method
```
 
 software.amazon.awssdk.services.s3.paginators.ListPartsPublisher publisher = client.listPartsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
 
 
```
    2) Using a custom subscriber
```
 
 software.amazon.awssdk.services.s3.paginators.ListPartsPublisher publisher = client.listPartsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.s3.model.ListPartsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.s3.model.ListPartsResponse response) { //... };
 });
 
```
    As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.
    Note: If you prefer to have control on service calls, use the listParts(software.amazon.awssdk.services.s3.model.ListPartsRequest) operation.
    Parameters:
    
    listPartsRequest -
    
    Returns:
    A custom publisher that can be subscribed to request a stream of response pages.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - listPartsPaginator
```
default ListPartsPublisher listPartsPaginator(Consumer<ListPartsRequest.Builder> listPartsRequest)
```
    Lists the parts that have been uploaded for a specific multipart upload. This operation must include the upload ID, which you obtain by sending the initiate multipart upload request (see CreateMultipartUpload). This request returns a maximum of 1,000 uploaded parts. The default number of parts returned is 1,000 parts. You can restrict the number of parts returned by specifying the max-parts request parameter. If your multipart upload consists of more than 1,000 parts, the response returns an IsTruncated field with the value of true, and a NextPartNumberMarker element. In subsequent ListParts requests you can include the part-number-marker query string parameter and set its value to the NextPartNumberMarker field value from the previous response.
    
    For more information on multipart uploads, see Uploading Objects Using Multipart Upload.
    
    For information on permissions required to use the multipart upload API, see Multipart Upload API and Permissions.
    
    The following operations are related to ListParts:
    This is a variant of listParts(software.amazon.awssdk.services.s3.model.ListPartsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.
    
    When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.
    
    The following are few ways to use the response class:
    1) Using the subscribe helper method
```
 
 software.amazon.awssdk.services.s3.paginators.ListPartsPublisher publisher = client.listPartsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
 
 
```
    2) Using a custom subscriber
```
 
 software.amazon.awssdk.services.s3.paginators.ListPartsPublisher publisher = client.listPartsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.s3.model.ListPartsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.s3.model.ListPartsResponse response) { //... };
 });
 
```
    As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.
    Note: If you prefer to have control on service calls, use the listParts(software.amazon.awssdk.services.s3.model.ListPartsRequest) operation.
    
    This is a convenience which creates an instance of the ListPartsRequest.Builder avoiding the need to create one manually via ListPartsRequest.builder()
    Parameters:
    
    listPartsRequest - A Consumer that will call methods on ListPartsRequest.Builder to create a request.
    
    Returns:
    A custom publisher that can be subscribed to request a stream of response pages.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putBucketAccelerateConfiguration
```
default CompletableFuture<PutBucketAccelerateConfigurationResponse> putBucketAccelerateConfiguration(PutBucketAccelerateConfigurationRequest putBucketAccelerateConfigurationRequest)
```
    Sets the accelerate configuration of an existing bucket. Amazon S3 Transfer Acceleration is a bucket-level feature that enables you to perform faster data transfers to Amazon S3.
    
    To use this operation, you must have permission to perform the s3:PutAccelerateConfiguration action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.
    
    The Transfer Acceleration state of a bucket can be set to one of the following two values:
    - Enabled – Enables accelerated data transfers to the bucket.
    - Suspended – Disables accelerated data transfers to the bucket.
    The GetBucketAccelerateConfiguration operation returns the transfer acceleration state of a bucket.
    
    After setting the Transfer Acceleration state of a bucket to Enabled, it might take up to thirty minutes before the data transfer rates to the bucket increase.
    
    The name of the bucket used for Transfer Acceleration must be DNS-compliant and must not contain periods (".").
    
    For more information about transfer acceleration, see Transfer Acceleration.
    
    The following operations are related to PutBucketAccelerateConfiguration:
    - GetBucketAccelerateConfiguration
    - CreateBucket
    Parameters:
    
    putBucketAccelerateConfigurationRequest -
    
    Returns:
    A Java Future containing the result of the PutBucketAccelerateConfiguration operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putBucketAccelerateConfiguration
```
default CompletableFuture<PutBucketAccelerateConfigurationResponse> putBucketAccelerateConfiguration(Consumer<PutBucketAccelerateConfigurationRequest.Builder> putBucketAccelerateConfigurationRequest)
```
    Sets the accelerate configuration of an existing bucket. Amazon S3 Transfer Acceleration is a bucket-level feature that enables you to perform faster data transfers to Amazon S3.
    
    To use this operation, you must have permission to perform the s3:PutAccelerateConfiguration action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.
    
    The Transfer Acceleration state of a bucket can be set to one of the following two values:
    - Enabled – Enables accelerated data transfers to the bucket.
    - Suspended – Disables accelerated data transfers to the bucket.
    The GetBucketAccelerateConfiguration operation returns the transfer acceleration state of a bucket.
    
    After setting the Transfer Acceleration state of a bucket to Enabled, it might take up to thirty minutes before the data transfer rates to the bucket increase.
    
    The name of the bucket used for Transfer Acceleration must be DNS-compliant and must not contain periods (".").
    
    For more information about transfer acceleration, see Transfer Acceleration.
    
    The following operations are related to PutBucketAccelerateConfiguration:
    - GetBucketAccelerateConfiguration
    - CreateBucket
    This is a convenience which creates an instance of the PutBucketAccelerateConfigurationRequest.Builder avoiding the need to create one manually via PutBucketAccelerateConfigurationRequest.builder()
    Parameters:
    
    putBucketAccelerateConfigurationRequest - A Consumer that will call methods on PutBucketAccelerateConfigurationRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the PutBucketAccelerateConfiguration operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putBucketAcl
```
default CompletableFuture<PutBucketAclResponse> putBucketAcl(PutBucketAclRequest putBucketAclRequest)
```
    Sets the permissions on an existing bucket using access control lists (ACL). For more information, see Using ACLs. To set the ACL of a bucket, you must have WRITE_ACP permission.
    
    You can use one of the following two ways to set a bucket's permissions:
    - Specify the ACL in the request body
    - Specify permissions using request headers
    You cannot specify access permission using both the body and the request headers.
    
    Depending on your application needs, you may choose to set the ACL on a bucket using either the request body or the headers. For example, if you have an existing application that updates a bucket ACL using the request body, then you can continue to use that approach.
    
    Access Permissions
    
    You can set access permissions using one of the following methods:
    - Specify a canned ACL with the x-amz-acl request header. Amazon S3 supports a set of predefined ACLs, known as canned ACLs. Each canned ACL has a predefined set of grantees and permissions. Specify the canned ACL name as the value of x-amz-acl. If you use this header, you cannot use other access control-specific headers in your request. For more information, see Canned ACL.
    - Specify access permissions explicitly with the x-amz-grant-read, x-amz-grant-read-acp, x-amz-grant-write-acp, and x-amz-grant-full-control headers. When using these headers, you specify explicit access permissions and grantees (AWS accounts or Amazon S3 groups) who will receive the permission. If you use these ACL-specific headers, you cannot use the x-amz-acl header to set a canned ACL. These parameters map to the set of permissions that Amazon S3 supports in an ACL. For more information, see Access Control List (ACL) Overview.
      
      You specify each grantee as a type=value pair, where the type is one of the following:
      
      emailAddress – if the value specified is the email address of an AWS account
      
      id – if the value specified is the canonical user ID of an AWS account
      
      uri – if you are granting permissions to a predefined group
      
      For example, the following x-amz-grant-write header grants create, overwrite, and delete objects permission to LogDelivery group predefined by Amazon S3 and two AWS accounts identified by their email addresses.
      
      x-amz-grant-write: uri="http://acs.amazonaws.com/groups/s3/LogDelivery", emailAddress="[email protected]", emailAddress="[email protected]"
    You can use either a canned ACL or specify access permissions explicitly. You cannot do both.
    
    Grantee Values
    
    You can specify the person (grantee) to whom you're assigning access rights (using request elements) in the following ways:
    - By Email address:
      
      <Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="AmazonCustomerByEmail"><EmailAddress><>[email protected]<></EmailAddress>lt;/Grantee>
      
      The grantee is resolved to the CanonicalUser and, in a response to a GET Object acl request, appears as the CanonicalUser.
    - By the person's ID:
      
      <Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="CanonicalUser"><ID><>ID<></ID><DisplayName><>GranteesEmail<></DisplayName> </Grantee>
      
      DisplayName is optional and ignored in the request
    - By URI:
      
      <Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="Group"><URI><>http://acs.amazonaws.com/groups/global/AuthenticatedUsers<></URI></Grantee>
    Related Resources
    Parameters:
    
    putBucketAclRequest -
    
    Returns:
    A Java Future containing the result of the PutBucketAcl operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putBucketAcl
```
default CompletableFuture<PutBucketAclResponse> putBucketAcl(Consumer<PutBucketAclRequest.Builder> putBucketAclRequest)
```
    Sets the permissions on an existing bucket using access control lists (ACL). For more information, see Using ACLs. To set the ACL of a bucket, you must have WRITE_ACP permission.
    
    You can use one of the following two ways to set a bucket's permissions:
    - Specify the ACL in the request body
    - Specify permissions using request headers
    You cannot specify access permission using both the body and the request headers.
    
    Depending on your application needs, you may choose to set the ACL on a bucket using either the request body or the headers. For example, if you have an existing application that updates a bucket ACL using the request body, then you can continue to use that approach.
    
    Access Permissions
    
    You can set access permissions using one of the following methods:
    - Specify a canned ACL with the x-amz-acl request header. Amazon S3 supports a set of predefined ACLs, known as canned ACLs. Each canned ACL has a predefined set of grantees and permissions. Specify the canned ACL name as the value of x-amz-acl. If you use this header, you cannot use other access control-specific headers in your request. For more information, see Canned ACL.
    - Specify access permissions explicitly with the x-amz-grant-read, x-amz-grant-read-acp, x-amz-grant-write-acp, and x-amz-grant-full-control headers. When using these headers, you specify explicit access permissions and grantees (AWS accounts or Amazon S3 groups) who will receive the permission. If you use these ACL-specific headers, you cannot use the x-amz-acl header to set a canned ACL. These parameters map to the set of permissions that Amazon S3 supports in an ACL. For more information, see Access Control List (ACL) Overview.
      
      You specify each grantee as a type=value pair, where the type is one of the following:
      
      emailAddress – if the value specified is the email address of an AWS account
      
      id – if the value specified is the canonical user ID of an AWS account
      
      uri – if you are granting permissions to a predefined group
      
      For example, the following x-amz-grant-write header grants create, overwrite, and delete objects permission to LogDelivery group predefined by Amazon S3 and two AWS accounts identified by their email addresses.
      
      x-amz-grant-write: uri="http://acs.amazonaws.com/groups/s3/LogDelivery", emailAddress="[email protected]", emailAddress="[email protected]"
    You can use either a canned ACL or specify access permissions explicitly. You cannot do both.
    
    Grantee Values
    
    You can specify the person (grantee) to whom you're assigning access rights (using request elements) in the following ways:
    - By Email address:
      
      <Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="AmazonCustomerByEmail"><EmailAddress><>[email protected]<></EmailAddress>lt;/Grantee>
      
      The grantee is resolved to the CanonicalUser and, in a response to a GET Object acl request, appears as the CanonicalUser.
    - By the person's ID:
      
      <Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="CanonicalUser"><ID><>ID<></ID><DisplayName><>GranteesEmail<></DisplayName> </Grantee>
      
      DisplayName is optional and ignored in the request
    - By URI:
      
      <Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="Group"><URI><>http://acs.amazonaws.com/groups/global/AuthenticatedUsers<></URI></Grantee>
    Related Resources
    This is a convenience which creates an instance of the PutBucketAclRequest.Builder avoiding the need to create one manually via PutBucketAclRequest.builder()
    Parameters:
    
    putBucketAclRequest - A Consumer that will call methods on PutBucketAclRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the PutBucketAcl operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putBucketAnalyticsConfiguration
```
default CompletableFuture<PutBucketAnalyticsConfigurationResponse> putBucketAnalyticsConfiguration(PutBucketAnalyticsConfigurationRequest putBucketAnalyticsConfigurationRequest)
```
    Sets an analytics configuration for the bucket (specified by the analytics configuration ID). You can have up to 1,000 analytics configurations per bucket.
    
    You can choose to have storage class analysis export analysis reports sent to a comma-separated values (CSV) flat file. See the DataExport request element. Reports are updated daily and are based on the object filters that you configure. When selecting data export, you specify a destination bucket and an optional destination prefix where the file is written. You can export the data to a destination bucket in a different account. However, the destination bucket must be in the same Region as the bucket that you are making the PUT analytics configuration to. For more information, see Amazon S3 Analytics – Storage Class Analysis.
    
    You must create a bucket policy on the destination bucket where the exported file is written to grant permissions to Amazon S3 to write objects to the bucket. For an example policy, see Granting Permissions for Amazon S3 Inventory and Storage Class Analysis.
    
    To use this operation, you must have permissions to perform the s3:PutAnalyticsConfiguration action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.
    
    Special Errors
    - HTTP Error: HTTP 400 Bad Request
      
      Code: InvalidArgument
      
      Cause: Invalid argument.
    - HTTP Error: HTTP 400 Bad Request
      
      Code: TooManyConfigurations
      
      Cause: You are attempting to create a new configuration but have already reached the 1,000-configuration limit.
    - HTTP Error: HTTP 403 Forbidden
      
      Code: AccessDenied
      
      Cause: You are not the owner of the specified bucket, or you do not have the s3:PutAnalyticsConfiguration bucket permission to set the configuration on the bucket.
    Related Resources
    Parameters:
    
    putBucketAnalyticsConfigurationRequest -
    
    Returns:
    A Java Future containing the result of the PutBucketAnalyticsConfiguration operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putBucketAnalyticsConfiguration
```
default CompletableFuture<PutBucketAnalyticsConfigurationResponse> putBucketAnalyticsConfiguration(Consumer<PutBucketAnalyticsConfigurationRequest.Builder> putBucketAnalyticsConfigurationRequest)
```
    Sets an analytics configuration for the bucket (specified by the analytics configuration ID). You can have up to 1,000 analytics configurations per bucket.
    
    You can choose to have storage class analysis export analysis reports sent to a comma-separated values (CSV) flat file. See the DataExport request element. Reports are updated daily and are based on the object filters that you configure. When selecting data export, you specify a destination bucket and an optional destination prefix where the file is written. You can export the data to a destination bucket in a different account. However, the destination bucket must be in the same Region as the bucket that you are making the PUT analytics configuration to. For more information, see Amazon S3 Analytics – Storage Class Analysis.
    
    You must create a bucket policy on the destination bucket where the exported file is written to grant permissions to Amazon S3 to write objects to the bucket. For an example policy, see Granting Permissions for Amazon S3 Inventory and Storage Class Analysis.
    
    To use this operation, you must have permissions to perform the s3:PutAnalyticsConfiguration action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.
    
    Special Errors
    - HTTP Error: HTTP 400 Bad Request
      
      Code: InvalidArgument
      
      Cause: Invalid argument.
    - HTTP Error: HTTP 400 Bad Request
      
      Code: TooManyConfigurations
      
      Cause: You are attempting to create a new configuration but have already reached the 1,000-configuration limit.
    - HTTP Error: HTTP 403 Forbidden
      
      Code: AccessDenied
      
      Cause: You are not the owner of the specified bucket, or you do not have the s3:PutAnalyticsConfiguration bucket permission to set the configuration on the bucket.
    Related Resources
    This is a convenience which creates an instance of the PutBucketAnalyticsConfigurationRequest.Builder avoiding the need to create one manually via PutBucketAnalyticsConfigurationRequest.builder()
    Parameters:
    
    putBucketAnalyticsConfigurationRequest - A Consumer that will call methods on PutBucketAnalyticsConfigurationRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the PutBucketAnalyticsConfiguration operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putBucketCors
```
default CompletableFuture<PutBucketCorsResponse> putBucketCors(PutBucketCorsRequest putBucketCorsRequest)
```
    Sets the cors configuration for your bucket. If the configuration exists, Amazon S3 replaces it.
    
    To use this operation, you must be allowed to perform the s3:PutBucketCORS action. By default, the bucket owner has this permission and can grant it to others.
    
    You set this configuration on a bucket so that the bucket can service cross-origin requests. For example, you might want to enable a request whose origin is http://www.example.com to access your Amazon S3 bucket at my.example.bucket.com by using the browser's XMLHttpRequest capability.
    
    To enable cross-origin resource sharing (CORS) on a bucket, you add the cors subresource to the bucket. The cors subresource is an XML document in which you configure rules that identify origins and the HTTP methods that can be executed on your bucket. The document is limited to 64 KB in size.
    
    When Amazon S3 receives a cross-origin request (or a pre-flight OPTIONS request) against a bucket, it evaluates the cors configuration on the bucket and uses the first CORSRule rule that matches the incoming browser request to enable a cross-origin request. For a rule to match, the following conditions must be met:
    - The request's Origin header must match AllowedOrigin elements.
    - The request method (for example, GET, PUT, HEAD, and so on) or the Access-Control-Request-Method header in case of a pre-flight OPTIONS request must be one of the AllowedMethod elements.
    - Every header specified in the Access-Control-Request-Headers request header of a pre-flight request must match an AllowedHeader element.
    For more information about CORS, go to Enabling Cross-Origin Resource Sharing in the Amazon Simple Storage Service Developer Guide.
    
    Related Resources
    Parameters:
    
    putBucketCorsRequest -
    
    Returns:
    A Java Future containing the result of the PutBucketCors operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putBucketCors
```
default CompletableFuture<PutBucketCorsResponse> putBucketCors(Consumer<PutBucketCorsRequest.Builder> putBucketCorsRequest)
```
    Sets the cors configuration for your bucket. If the configuration exists, Amazon S3 replaces it.
    
    To use this operation, you must be allowed to perform the s3:PutBucketCORS action. By default, the bucket owner has this permission and can grant it to others.
    
    You set this configuration on a bucket so that the bucket can service cross-origin requests. For example, you might want to enable a request whose origin is http://www.example.com to access your Amazon S3 bucket at my.example.bucket.com by using the browser's XMLHttpRequest capability.
    
    To enable cross-origin resource sharing (CORS) on a bucket, you add the cors subresource to the bucket. The cors subresource is an XML document in which you configure rules that identify origins and the HTTP methods that can be executed on your bucket. The document is limited to 64 KB in size.
    
    When Amazon S3 receives a cross-origin request (or a pre-flight OPTIONS request) against a bucket, it evaluates the cors configuration on the bucket and uses the first CORSRule rule that matches the incoming browser request to enable a cross-origin request. For a rule to match, the following conditions must be met:
    - The request's Origin header must match AllowedOrigin elements.
    - The request method (for example, GET, PUT, HEAD, and so on) or the Access-Control-Request-Method header in case of a pre-flight OPTIONS request must be one of the AllowedMethod elements.
    - Every header specified in the Access-Control-Request-Headers request header of a pre-flight request must match an AllowedHeader element.
    For more information about CORS, go to Enabling Cross-Origin Resource Sharing in the Amazon Simple Storage Service Developer Guide.
    
    Related Resources
    This is a convenience which creates an instance of the PutBucketCorsRequest.Builder avoiding the need to create one manually via PutBucketCorsRequest.builder()
    Parameters:
    
    putBucketCorsRequest - A Consumer that will call methods on PutBucketCorsRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the PutBucketCors operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putBucketEncryption
```
default CompletableFuture<PutBucketEncryptionResponse> putBucketEncryption(PutBucketEncryptionRequest putBucketEncryptionRequest)
```
    This implementation of the PUT operation uses the encryption subresource to set the default encryption state of an existing bucket.
    
    This implementation of the PUT operation sets default encryption for a bucket using server-side encryption with Amazon S3-managed keys SSE-S3 or AWS KMS customer master keys (CMKs) (SSE-KMS).
    
    This operation requires AWS Signature Version 4. For more information, see Authenticating Requests (AWS Signature Version 4).
    
    To use this operation, you must have permissions to perform the s3:PutEncryptionConfiguration action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources in the Amazon Simple Storage Service Developer Guide.
    
    Related Resources
    - GetBucketEncryption
    - DeleteBucketEncryption
    Parameters:
    
    putBucketEncryptionRequest -
    
    Returns:
    A Java Future containing the result of the PutBucketEncryption operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putBucketEncryption
```
default CompletableFuture<PutBucketEncryptionResponse> putBucketEncryption(Consumer<PutBucketEncryptionRequest.Builder> putBucketEncryptionRequest)
```
    This implementation of the PUT operation uses the encryption subresource to set the default encryption state of an existing bucket.
    
    This implementation of the PUT operation sets default encryption for a bucket using server-side encryption with Amazon S3-managed keys SSE-S3 or AWS KMS customer master keys (CMKs) (SSE-KMS).
    
    This operation requires AWS Signature Version 4. For more information, see Authenticating Requests (AWS Signature Version 4).
    
    To use this operation, you must have permissions to perform the s3:PutEncryptionConfiguration action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources in the Amazon Simple Storage Service Developer Guide.
    
    Related Resources
    - GetBucketEncryption
    - DeleteBucketEncryption
    This is a convenience which creates an instance of the PutBucketEncryptionRequest.Builder avoiding the need to create one manually via PutBucketEncryptionRequest.builder()
    Parameters:
    
    putBucketEncryptionRequest - A Consumer that will call methods on PutBucketEncryptionRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the PutBucketEncryption operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putBucketInventoryConfiguration
```
default CompletableFuture<PutBucketInventoryConfigurationResponse> putBucketInventoryConfiguration(PutBucketInventoryConfigurationRequest putBucketInventoryConfigurationRequest)
```
    This implementation of the PUT operation adds an inventory configuration (identified by the inventory ID) to the bucket. You can have up to 1,000 inventory configurations per bucket.
    
    Amazon S3 inventory generates inventories of the objects in the bucket on a daily or weekly basis, and the results are published to a flat file. The bucket that is inventoried is called the source bucket, and the bucket where the inventory flat file is stored is called the destination bucket. The destination bucket must be in the same AWS Region as the source bucket.
    
    When you configure an inventory for a source bucket, you specify the destination bucket where you want the inventory to be stored, and whether to generate the inventory daily or weekly. You can also configure what object metadata to include and whether to inventory all object versions or only current versions. For more information, see Amazon S3 Inventory in the Amazon Simple Storage Service Developer Guide.
    
    You must create a bucket policy on the destination bucket to grant permissions to Amazon S3 to write objects to the bucket in the defined location. For an example policy, see Granting Permissions for Amazon S3 Inventory and Storage Class Analysis.
    
    To use this operation, you must have permissions to perform the s3:PutInventoryConfiguration action. The bucket owner has this permission by default and can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources in the Amazon Simple Storage Service Developer Guide.
    
    Special Errors
    - HTTP 400 Bad Request Error
      
      Code: InvalidArgument
      
      Cause: Invalid Argument
    - HTTP 400 Bad Request Error
      
      Code: TooManyConfigurations
      
      Cause: You are attempting to create a new configuration but have already reached the 1,000-configuration limit.
    - HTTP 403 Forbidden Error
      
      Code: AccessDenied
      
      Cause: You are not the owner of the specified bucket, or you do not have the s3:PutInventoryConfiguration bucket permission to set the configuration on the bucket
    Related Resources
    Parameters:
    
    putBucketInventoryConfigurationRequest -
    
    Returns:
    A Java Future containing the result of the PutBucketInventoryConfiguration operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putBucketInventoryConfiguration
```
default CompletableFuture<PutBucketInventoryConfigurationResponse> putBucketInventoryConfiguration(Consumer<PutBucketInventoryConfigurationRequest.Builder> putBucketInventoryConfigurationRequest)
```
    This implementation of the PUT operation adds an inventory configuration (identified by the inventory ID) to the bucket. You can have up to 1,000 inventory configurations per bucket.
    
    Amazon S3 inventory generates inventories of the objects in the bucket on a daily or weekly basis, and the results are published to a flat file. The bucket that is inventoried is called the source bucket, and the bucket where the inventory flat file is stored is called the destination bucket. The destination bucket must be in the same AWS Region as the source bucket.
    
    When you configure an inventory for a source bucket, you specify the destination bucket where you want the inventory to be stored, and whether to generate the inventory daily or weekly. You can also configure what object metadata to include and whether to inventory all object versions or only current versions. For more information, see Amazon S3 Inventory in the Amazon Simple Storage Service Developer Guide.
    
    You must create a bucket policy on the destination bucket to grant permissions to Amazon S3 to write objects to the bucket in the defined location. For an example policy, see Granting Permissions for Amazon S3 Inventory and Storage Class Analysis.
    
    To use this operation, you must have permissions to perform the s3:PutInventoryConfiguration action. The bucket owner has this permission by default and can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources in the Amazon Simple Storage Service Developer Guide.
    
    Special Errors
    - HTTP 400 Bad Request Error
      
      Code: InvalidArgument
      
      Cause: Invalid Argument
    - HTTP 400 Bad Request Error
      
      Code: TooManyConfigurations
      
      Cause: You are attempting to create a new configuration but have already reached the 1,000-configuration limit.
    - HTTP 403 Forbidden Error
      
      Code: AccessDenied
      
      Cause: You are not the owner of the specified bucket, or you do not have the s3:PutInventoryConfiguration bucket permission to set the configuration on the bucket
    Related Resources
    This is a convenience which creates an instance of the PutBucketInventoryConfigurationRequest.Builder avoiding the need to create one manually via PutBucketInventoryConfigurationRequest.builder()
    Parameters:
    
    putBucketInventoryConfigurationRequest - A Consumer that will call methods on PutBucketInventoryConfigurationRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the PutBucketInventoryConfiguration operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putBucketLifecycleConfiguration
```
default CompletableFuture<PutBucketLifecycleConfigurationResponse> putBucketLifecycleConfiguration(PutBucketLifecycleConfigurationRequest putBucketLifecycleConfigurationRequest)
```
    Creates a new lifecycle configuration for the bucket or replaces an existing lifecycle configuration. For information about lifecycle configuration, see Managing Access Permissions to Your Amazon S3 Resources.
    
    Bucket lifecycle configuration now supports specifying a lifecycle rule using an object key name prefix, one or more object tags, or a combination of both. Accordingly, this section describes the latest API. The previous version of the API supported filtering based only on an object key name prefix, which is supported for backward compatibility. For the related API description, see PutBucketLifecycle.
    
    Rules
    
    You specify the lifecycle configuration in your request body. The lifecycle configuration is specified as XML consisting of one or more rules. Each rule consists of the following:
    - Filter identifying a subset of objects to which the rule applies. The filter can be based on a key name prefix, object tags, or a combination of both.
    - Status whether the rule is in effect.
    - One or more lifecycle transition and expiration actions that you want Amazon S3 to perform on the objects identified by the filter. If the state of your bucket is versioning-enabled or versioning-suspended, you can have many versions of the same object (one current version and zero or more noncurrent versions). Amazon S3 provides predefined actions that you can specify for current and noncurrent object versions.
    For more information, see Object Lifecycle Management and Lifecycle Configuration Elements.
    
    Permissions
    
    By default, all Amazon S3 resources are private, including buckets, objects, and related subresources (for example, lifecycle configuration and website configuration). Only the resource owner (that is, the AWS account that created it) can access the resource. The resource owner can optionally grant access permissions to others by writing an access policy. For this operation, a user must get the s3:PutLifecycleConfiguration permission.
    
    You can also explicitly deny permissions. Explicit deny also supersedes any other permissions. If you want to block users or accounts from removing or deleting objects from your bucket, you must deny them permissions for the following actions:
    - s3:DeleteObject
    - s3:DeleteObjectVersion
    - s3:PutLifecycleConfiguration
    For more information about permissions, see Managing Access Permissions to Your Amazon S3 Resources.
    
    The following are related to PutBucketLifecycleConfiguration:
    Parameters:
    
    putBucketLifecycleConfigurationRequest -
    
    Returns:
    A Java Future containing the result of the PutBucketLifecycleConfiguration operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putBucketLifecycleConfiguration
```
default CompletableFuture<PutBucketLifecycleConfigurationResponse> putBucketLifecycleConfiguration(Consumer<PutBucketLifecycleConfigurationRequest.Builder> putBucketLifecycleConfigurationRequest)
```
    Creates a new lifecycle configuration for the bucket or replaces an existing lifecycle configuration. For information about lifecycle configuration, see Managing Access Permissions to Your Amazon S3 Resources.
    
    Bucket lifecycle configuration now supports specifying a lifecycle rule using an object key name prefix, one or more object tags, or a combination of both. Accordingly, this section describes the latest API. The previous version of the API supported filtering based only on an object key name prefix, which is supported for backward compatibility. For the related API description, see PutBucketLifecycle.
    
    Rules
    
    You specify the lifecycle configuration in your request body. The lifecycle configuration is specified as XML consisting of one or more rules. Each rule consists of the following:
    - Filter identifying a subset of objects to which the rule applies. The filter can be based on a key name prefix, object tags, or a combination of both.
    - Status whether the rule is in effect.
    - One or more lifecycle transition and expiration actions that you want Amazon S3 to perform on the objects identified by the filter. If the state of your bucket is versioning-enabled or versioning-suspended, you can have many versions of the same object (one current version and zero or more noncurrent versions). Amazon S3 provides predefined actions that you can specify for current and noncurrent object versions.
    For more information, see Object Lifecycle Management and Lifecycle Configuration Elements.
    
    Permissions
    
    By default, all Amazon S3 resources are private, including buckets, objects, and related subresources (for example, lifecycle configuration and website configuration). Only the resource owner (that is, the AWS account that created it) can access the resource. The resource owner can optionally grant access permissions to others by writing an access policy. For this operation, a user must get the s3:PutLifecycleConfiguration permission.
    
    You can also explicitly deny permissions. Explicit deny also supersedes any other permissions. If you want to block users or accounts from removing or deleting objects from your bucket, you must deny them permissions for the following actions:
    - s3:DeleteObject
    - s3:DeleteObjectVersion
    - s3:PutLifecycleConfiguration
    For more information about permissions, see Managing Access Permissions to Your Amazon S3 Resources.
    
    The following are related to PutBucketLifecycleConfiguration:
    This is a convenience which creates an instance of the PutBucketLifecycleConfigurationRequest.Builder avoiding the need to create one manually via PutBucketLifecycleConfigurationRequest.builder()
    Parameters:
    
    putBucketLifecycleConfigurationRequest - A Consumer that will call methods on PutBucketLifecycleConfigurationRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the PutBucketLifecycleConfiguration operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putBucketLogging
```
default CompletableFuture<PutBucketLoggingResponse> putBucketLogging(PutBucketLoggingRequest putBucketLoggingRequest)
```
    Set the logging parameters for a bucket and to specify permissions for who can view and modify the logging parameters. All logs are saved to buckets in the same AWS Region as the source bucket. To set the logging status of a bucket, you must be the bucket owner.
    
    The bucket owner is automatically granted FULL_CONTROL to all logs. You use the Grantee request element to grant access to other people. The Permissions request element specifies the kind of access the grantee has to the logs.
    
    Grantee Values
    
    You can specify the person (grantee) to whom you're assigning access rights (using request elements) in the following ways:
    - By the person's ID:
      
      <Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="CanonicalUser"><ID><>ID<></ID><DisplayName><>GranteesEmail<></DisplayName> </Grantee>
      
      DisplayName is optional and ignored in the request.
    - By Email address:
      
      <Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="AmazonCustomerByEmail"><EmailAddress><>[email protected]<></EmailAddress></Grantee>
      
      The grantee is resolved to the CanonicalUser and, in a response to a GET Object acl request, appears as the CanonicalUser.
    - By URI:
      
      <Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="Group"><URI><>http://acs.amazonaws.com/groups/global/AuthenticatedUsers<></URI></Grantee>
    To enable logging, you use LoggingEnabled and its children request elements. To disable logging, you use an empty BucketLoggingStatus request element:
    
    <BucketLoggingStatus xmlns="http://doc.s3.amazonaws.com/2006-03-01" />
    
    For more information about server access logging, see Server Access Logging.
    
    For more information about creating a bucket, see CreateBucket. For more information about returning the logging status of a bucket, see GetBucketLogging.
    
    The following operations are related to PutBucketLogging:
    Parameters:
    
    putBucketLoggingRequest -
    
    Returns:
    A Java Future containing the result of the PutBucketLogging operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putBucketLogging
```
default CompletableFuture<PutBucketLoggingResponse> putBucketLogging(Consumer<PutBucketLoggingRequest.Builder> putBucketLoggingRequest)
```
    Set the logging parameters for a bucket and to specify permissions for who can view and modify the logging parameters. All logs are saved to buckets in the same AWS Region as the source bucket. To set the logging status of a bucket, you must be the bucket owner.
    
    The bucket owner is automatically granted FULL_CONTROL to all logs. You use the Grantee request element to grant access to other people. The Permissions request element specifies the kind of access the grantee has to the logs.
    
    Grantee Values
    
    You can specify the person (grantee) to whom you're assigning access rights (using request elements) in the following ways:
    - By the person's ID:
      
      <Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="CanonicalUser"><ID><>ID<></ID><DisplayName><>GranteesEmail<></DisplayName> </Grantee>
      
      DisplayName is optional and ignored in the request.
    - By Email address:
      
      <Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="AmazonCustomerByEmail"><EmailAddress><>[email protected]<></EmailAddress></Grantee>
      
      The grantee is resolved to the CanonicalUser and, in a response to a GET Object acl request, appears as the CanonicalUser.
    - By URI:
      
      <Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="Group"><URI><>http://acs.amazonaws.com/groups/global/AuthenticatedUsers<></URI></Grantee>
    To enable logging, you use LoggingEnabled and its children request elements. To disable logging, you use an empty BucketLoggingStatus request element:
    
    <BucketLoggingStatus xmlns="http://doc.s3.amazonaws.com/2006-03-01" />
    
    For more information about server access logging, see Server Access Logging.
    
    For more information about creating a bucket, see CreateBucket. For more information about returning the logging status of a bucket, see GetBucketLogging.
    
    The following operations are related to PutBucketLogging:
    This is a convenience which creates an instance of the PutBucketLoggingRequest.Builder avoiding the need to create one manually via PutBucketLoggingRequest.builder()
    Parameters:
    
    putBucketLoggingRequest - A Consumer that will call methods on PutBucketLoggingRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the PutBucketLogging operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putBucketMetricsConfiguration
```
default CompletableFuture<PutBucketMetricsConfigurationResponse> putBucketMetricsConfiguration(PutBucketMetricsConfigurationRequest putBucketMetricsConfigurationRequest)
```
    Sets a metrics configuration (specified by the metrics configuration ID) for the bucket. You can have up to 1,000 metrics configurations per bucket. If you're updating an existing metrics configuration, note that this is a full replacement of the existing metrics configuration. If you don't include the elements you want to keep, they are erased.
    
    To use this operation, you must have permissions to perform the s3:PutMetricsConfiguration action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.
    
    For information about CloudWatch request metrics for Amazon S3, see Monitoring Metrics with Amazon CloudWatch.
    
    The following operations are related to PutBucketMetricsConfiguration:
    GetBucketLifecycle has the following special error:
    - Error code: TooManyConfigurations
      
      Description: You are attempting to create a new configuration but have already reached the 1,000-configuration limit.
      
      HTTP Status Code: HTTP 400 Bad Request
    Parameters:
    
    putBucketMetricsConfigurationRequest -
    
    Returns:
    A Java Future containing the result of the PutBucketMetricsConfiguration operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putBucketMetricsConfiguration
```
default CompletableFuture<PutBucketMetricsConfigurationResponse> putBucketMetricsConfiguration(Consumer<PutBucketMetricsConfigurationRequest.Builder> putBucketMetricsConfigurationRequest)
```
    Sets a metrics configuration (specified by the metrics configuration ID) for the bucket. You can have up to 1,000 metrics configurations per bucket. If you're updating an existing metrics configuration, note that this is a full replacement of the existing metrics configuration. If you don't include the elements you want to keep, they are erased.
    
    To use this operation, you must have permissions to perform the s3:PutMetricsConfiguration action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.
    
    For information about CloudWatch request metrics for Amazon S3, see Monitoring Metrics with Amazon CloudWatch.
    
    The following operations are related to PutBucketMetricsConfiguration:
    GetBucketLifecycle has the following special error:
    - Error code: TooManyConfigurations
      
      Description: You are attempting to create a new configuration but have already reached the 1,000-configuration limit.
      
      HTTP Status Code: HTTP 400 Bad Request
    This is a convenience which creates an instance of the PutBucketMetricsConfigurationRequest.Builder avoiding the need to create one manually via PutBucketMetricsConfigurationRequest.builder()
    Parameters:
    
    putBucketMetricsConfigurationRequest - A Consumer that will call methods on PutBucketMetricsConfigurationRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the PutBucketMetricsConfiguration operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putBucketNotificationConfiguration
```
default CompletableFuture<PutBucketNotificationConfigurationResponse> putBucketNotificationConfiguration(PutBucketNotificationConfigurationRequest putBucketNotificationConfigurationRequest)
```
    Enables notifications of specified events for a bucket. For more information about event notifications, see Configuring Event Notifications.
    
    Using this API, you can replace an existing notification configuration. The configuration is an XML file that defines the event types that you want Amazon S3 to publish and the destination where you want Amazon S3 to publish an event notification when it detects an event of the specified type.
    
    By default, your bucket has no event notifications configured. That is, the notification configuration will be an empty NotificationConfiguration.
    
    <NotificationConfiguration>
    
    </NotificationConfiguration>
    
    This operation replaces the existing notification configuration with the configuration you include in the request body.
    
    After Amazon S3 receives this request, it first verifies that any Amazon Simple Notification Service (Amazon SNS) or Amazon Simple Queue Service (Amazon SQS) destination exists, and that the bucket owner has permission to publish to it by sending a test notification. In the case of AWS Lambda destinations, Amazon S3 verifies that the Lambda function permissions grant Amazon S3 permission to invoke the function from the Amazon S3 bucket. For more information, see Configuring Notifications for Amazon S3 Events.
    
    You can disable notifications by adding the empty NotificationConfiguration element.
    
    By default, only the bucket owner can configure notifications on a bucket. However, bucket owners can use a bucket policy to grant permission to other users to set this configuration with s3:PutBucketNotification permission.
    
    The PUT notification is an atomic operation. For example, suppose your notification configuration includes SNS topic, SQS queue, and Lambda function configurations. When you send a PUT request with this configuration, Amazon S3 sends test messages to your SNS topic. If the message fails, the entire PUT operation will fail, and Amazon S3 will not add the configuration to your bucket.
    
    Responses
    
    If the configuration in the request body includes only one TopicConfiguration specifying only the s3:ReducedRedundancyLostObject event type, the response will also include the x-amz-sns-test-message-id header containing the message ID of the test notification sent to the topic.
    
    The following operation is related to PutBucketNotificationConfiguration:
    - GetBucketNotificationConfiguration
    Parameters:
    
    putBucketNotificationConfigurationRequest -
    
    Returns:
    A Java Future containing the result of the PutBucketNotificationConfiguration operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putBucketNotificationConfiguration
```
default CompletableFuture<PutBucketNotificationConfigurationResponse> putBucketNotificationConfiguration(Consumer<PutBucketNotificationConfigurationRequest.Builder> putBucketNotificationConfigurationRequest)
```
    Enables notifications of specified events for a bucket. For more information about event notifications, see Configuring Event Notifications.
    
    Using this API, you can replace an existing notification configuration. The configuration is an XML file that defines the event types that you want Amazon S3 to publish and the destination where you want Amazon S3 to publish an event notification when it detects an event of the specified type.
    
    By default, your bucket has no event notifications configured. That is, the notification configuration will be an empty NotificationConfiguration.
    
    <NotificationConfiguration>
    
    </NotificationConfiguration>
    
    This operation replaces the existing notification configuration with the configuration you include in the request body.
    
    After Amazon S3 receives this request, it first verifies that any Amazon Simple Notification Service (Amazon SNS) or Amazon Simple Queue Service (Amazon SQS) destination exists, and that the bucket owner has permission to publish to it by sending a test notification. In the case of AWS Lambda destinations, Amazon S3 verifies that the Lambda function permissions grant Amazon S3 permission to invoke the function from the Amazon S3 bucket. For more information, see Configuring Notifications for Amazon S3 Events.
    
    You can disable notifications by adding the empty NotificationConfiguration element.
    
    By default, only the bucket owner can configure notifications on a bucket. However, bucket owners can use a bucket policy to grant permission to other users to set this configuration with s3:PutBucketNotification permission.
    
    The PUT notification is an atomic operation. For example, suppose your notification configuration includes SNS topic, SQS queue, and Lambda function configurations. When you send a PUT request with this configuration, Amazon S3 sends test messages to your SNS topic. If the message fails, the entire PUT operation will fail, and Amazon S3 will not add the configuration to your bucket.
    
    Responses
    
    If the configuration in the request body includes only one TopicConfiguration specifying only the s3:ReducedRedundancyLostObject event type, the response will also include the x-amz-sns-test-message-id header containing the message ID of the test notification sent to the topic.
    
    The following operation is related to PutBucketNotificationConfiguration:
    - GetBucketNotificationConfiguration
    This is a convenience which creates an instance of the PutBucketNotificationConfigurationRequest.Builder avoiding the need to create one manually via PutBucketNotificationConfigurationRequest.builder()
    Parameters:
    
    putBucketNotificationConfigurationRequest - A Consumer that will call methods on PutBucketNotificationConfigurationRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the PutBucketNotificationConfiguration operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putBucketPolicy
```
default CompletableFuture<PutBucketPolicyResponse> putBucketPolicy(PutBucketPolicyRequest putBucketPolicyRequest)
```
    Applies an Amazon S3 bucket policy to an Amazon S3 bucket. If you are using an identity other than the root user of the AWS account that owns the bucket, the calling identity must have the PutBucketPolicy permissions on the specified bucket and belong to the bucket owner's account in order to use this operation.
    
    If you don't have PutBucketPolicy 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.
    
    As a security precaution, the root user of the AWS account that owns a bucket can always use this operation, even if the policy explicitly denies the root user the ability to perform this action.
    
    For more information about bucket policies, see Using Bucket Policies and User Policies.
    
    The following operations are related to PutBucketPolicy:
    - CreateBucket
    - DeleteBucket
    Parameters:
    
    putBucketPolicyRequest -
    
    Returns:
    A Java Future containing the result of the PutBucketPolicy operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putBucketPolicy
```
default CompletableFuture<PutBucketPolicyResponse> putBucketPolicy(Consumer<PutBucketPolicyRequest.Builder> putBucketPolicyRequest)
```
    Applies an Amazon S3 bucket policy to an Amazon S3 bucket. If you are using an identity other than the root user of the AWS account that owns the bucket, the calling identity must have the PutBucketPolicy permissions on the specified bucket and belong to the bucket owner's account in order to use this operation.
    
    If you don't have PutBucketPolicy 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.
    
    As a security precaution, the root user of the AWS account that owns a bucket can always use this operation, even if the policy explicitly denies the root user the ability to perform this action.
    
    For more information about bucket policies, see Using Bucket Policies and User Policies.
    
    The following operations are related to PutBucketPolicy:
    - CreateBucket
    - DeleteBucket
    This is a convenience which creates an instance of the PutBucketPolicyRequest.Builder avoiding the need to create one manually via PutBucketPolicyRequest.builder()
    Parameters:
    
    putBucketPolicyRequest - A Consumer that will call methods on PutBucketPolicyRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the PutBucketPolicy operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putBucketReplication
```
default CompletableFuture<PutBucketReplicationResponse> putBucketReplication(PutBucketReplicationRequest putBucketReplicationRequest)
```
    Creates a replication configuration or replaces an existing one. For more information, see Replication in the Amazon S3 Developer Guide.
    
    To perform this operation, the user or role performing the operation must have the iam:PassRole permission.
    
    Specify the replication configuration in the request body. In the replication configuration, you provide the name of the destination bucket where you want Amazon S3 to replicate objects, the IAM role that Amazon S3 can assume to replicate objects on your behalf, and other relevant information.
    
    A replication configuration must include at least one rule, and can contain a maximum of 1,000. Each rule identifies a subset of objects to replicate by filtering the objects in the source bucket. To choose additional subsets of objects to replicate, add a rule for each subset. All rules must specify the same destination bucket.
    
    To specify a subset of the objects in the source bucket to apply a replication rule to, add the Filter element as a child of the Rule element. You can filter objects based on an object key prefix, one or more object tags, or both. When you add the Filter element in the configuration, you must also add the following elements: DeleteMarkerReplication, Status, and Priority.
    
    For information about enabling versioning on a bucket, see Using Versioning.
    
    By default, a resource owner, in this case the AWS account that created the bucket, can perform this operation. The resource owner can also grant others permissions to perform the operation. For more information about permissions, see Specifying Permissions in a Policy and Managing Access Permissions to Your Amazon S3 Resources.
    
    Handling Replication of Encrypted Objects
    
    By default, Amazon S3 doesn't replicate objects that are stored at rest using server-side encryption with CMKs stored in AWS KMS. To replicate AWS KMS-encrypted objects, add the following: SourceSelectionCriteria, SseKmsEncryptedObjects, Status, EncryptionConfiguration, and ReplicaKmsKeyID. For information about replication configuration, see Replicating Objects Created with SSE Using CMKs stored in AWS KMS.
    
    For information on PutBucketReplication errors, see ReplicationErrorCodeList
    
    The following operations are related to PutBucketReplication:
    - GetBucketReplication
    - DeleteBucketReplication
    Parameters:
    
    putBucketReplicationRequest -
    
    Returns:
    A Java Future containing the result of the PutBucketReplication operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putBucketReplication
```
default CompletableFuture<PutBucketReplicationResponse> putBucketReplication(Consumer<PutBucketReplicationRequest.Builder> putBucketReplicationRequest)
```
    Creates a replication configuration or replaces an existing one. For more information, see Replication in the Amazon S3 Developer Guide.
    
    To perform this operation, the user or role performing the operation must have the iam:PassRole permission.
    
    Specify the replication configuration in the request body. In the replication configuration, you provide the name of the destination bucket where you want Amazon S3 to replicate objects, the IAM role that Amazon S3 can assume to replicate objects on your behalf, and other relevant information.
    
    A replication configuration must include at least one rule, and can contain a maximum of 1,000. Each rule identifies a subset of objects to replicate by filtering the objects in the source bucket. To choose additional subsets of objects to replicate, add a rule for each subset. All rules must specify the same destination bucket.
    
    To specify a subset of the objects in the source bucket to apply a replication rule to, add the Filter element as a child of the Rule element. You can filter objects based on an object key prefix, one or more object tags, or both. When you add the Filter element in the configuration, you must also add the following elements: DeleteMarkerReplication, Status, and Priority.
    
    For information about enabling versioning on a bucket, see Using Versioning.
    
    By default, a resource owner, in this case the AWS account that created the bucket, can perform this operation. The resource owner can also grant others permissions to perform the operation. For more information about permissions, see Specifying Permissions in a Policy and Managing Access Permissions to Your Amazon S3 Resources.
    
    Handling Replication of Encrypted Objects
    
    By default, Amazon S3 doesn't replicate objects that are stored at rest using server-side encryption with CMKs stored in AWS KMS. To replicate AWS KMS-encrypted objects, add the following: SourceSelectionCriteria, SseKmsEncryptedObjects, Status, EncryptionConfiguration, and ReplicaKmsKeyID. For information about replication configuration, see Replicating Objects Created with SSE Using CMKs stored in AWS KMS.
    
    For information on PutBucketReplication errors, see ReplicationErrorCodeList
    
    The following operations are related to PutBucketReplication:
    - GetBucketReplication
    - DeleteBucketReplication
    This is a convenience which creates an instance of the PutBucketReplicationRequest.Builder avoiding the need to create one manually via PutBucketReplicationRequest.builder()
    Parameters:
    
    putBucketReplicationRequest - A Consumer that will call methods on PutBucketReplicationRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the PutBucketReplication operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putBucketRequestPayment
```
default CompletableFuture<PutBucketRequestPaymentResponse> putBucketRequestPayment(PutBucketRequestPaymentRequest putBucketRequestPaymentRequest)
```
    Sets the request payment configuration for a bucket. By default, the bucket owner pays for downloads from the bucket. This configuration parameter enables the bucket owner (only) to specify that the person requesting the download will be charged for the download. For more information, see Requester Pays Buckets.
    
    The following operations are related to PutBucketRequestPayment:
    - CreateBucket
    - GetBucketRequestPayment
    Parameters:
    
    putBucketRequestPaymentRequest -
    
    Returns:
    A Java Future containing the result of the PutBucketRequestPayment operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putBucketRequestPayment
```
default CompletableFuture<PutBucketRequestPaymentResponse> putBucketRequestPayment(Consumer<PutBucketRequestPaymentRequest.Builder> putBucketRequestPaymentRequest)
```
    Sets the request payment configuration for a bucket. By default, the bucket owner pays for downloads from the bucket. This configuration parameter enables the bucket owner (only) to specify that the person requesting the download will be charged for the download. For more information, see Requester Pays Buckets.
    
    The following operations are related to PutBucketRequestPayment:
    - CreateBucket
    - GetBucketRequestPayment
    This is a convenience which creates an instance of the PutBucketRequestPaymentRequest.Builder avoiding the need to create one manually via PutBucketRequestPaymentRequest.builder()
    Parameters:
    
    putBucketRequestPaymentRequest - A Consumer that will call methods on PutBucketRequestPaymentRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the PutBucketRequestPayment operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putBucketTagging
```
default CompletableFuture<PutBucketTaggingResponse> putBucketTagging(PutBucketTaggingRequest putBucketTaggingRequest)
```
    Sets the tags for a bucket.
    
    Use tags to organize your AWS bill to reflect your own cost structure. To do this, sign up to get your AWS account bill with tag key values included. Then, to see the cost of combined resources, organize your billing information according to resources with the same tag key values. For example, you can tag several resources with a specific application name, and then organize your billing information to see the total cost of that application across several services. For more information, see Cost Allocation and Tagging.
    
    Within a bucket, if you add a tag that has the same key as an existing tag, the new value overwrites the old value. For more information, see Using Cost Allocation in Amazon S3 Bucket Tags.
    
    To use this operation, you must have permissions to perform the s3:PutBucketTagging action. The bucket owner has this permission by default and can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.
    
    PutBucketTagging has the following special errors:
    - Error code: InvalidTagError
      
      Description: The tag provided was not a valid tag. This error can occur if the tag did not pass input validation. For information about tag restrictions, see User-Defined Tag Restrictions and AWS-Generated Cost Allocation Tag Restrictions.
    - Error code: MalformedXMLError
      
      Description: The XML provided does not match the schema.
    - Error code: OperationAbortedError
      
      Description: A conflicting conditional operation is currently in progress against this resource. Please try again.
    - Error code: InternalError
      
      Description: The service was unable to apply the provided tag to the bucket.
    The following operations are related to PutBucketTagging:
    - GetBucketTagging
    - DeleteBucketTagging
    Parameters:
    
    putBucketTaggingRequest -
    
    Returns:
    A Java Future containing the result of the PutBucketTagging operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putBucketTagging
```
default CompletableFuture<PutBucketTaggingResponse> putBucketTagging(Consumer<PutBucketTaggingRequest.Builder> putBucketTaggingRequest)
```
    Sets the tags for a bucket.
    
    Use tags to organize your AWS bill to reflect your own cost structure. To do this, sign up to get your AWS account bill with tag key values included. Then, to see the cost of combined resources, organize your billing information according to resources with the same tag key values. For example, you can tag several resources with a specific application name, and then organize your billing information to see the total cost of that application across several services. For more information, see Cost Allocation and Tagging.
    
    Within a bucket, if you add a tag that has the same key as an existing tag, the new value overwrites the old value. For more information, see Using Cost Allocation in Amazon S3 Bucket Tags.
    
    To use this operation, you must have permissions to perform the s3:PutBucketTagging action. The bucket owner has this permission by default and can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.
    
    PutBucketTagging has the following special errors:
    - Error code: InvalidTagError
      
      Description: The tag provided was not a valid tag. This error can occur if the tag did not pass input validation. For information about tag restrictions, see User-Defined Tag Restrictions and AWS-Generated Cost Allocation Tag Restrictions.
    - Error code: MalformedXMLError
      
      Description: The XML provided does not match the schema.
    - Error code: OperationAbortedError
      
      Description: A conflicting conditional operation is currently in progress against this resource. Please try again.
    - Error code: InternalError
      
      Description: The service was unable to apply the provided tag to the bucket.
    The following operations are related to PutBucketTagging:
    - GetBucketTagging
    - DeleteBucketTagging
    This is a convenience which creates an instance of the PutBucketTaggingRequest.Builder avoiding the need to create one manually via PutBucketTaggingRequest.builder()
    Parameters:
    
    putBucketTaggingRequest - A Consumer that will call methods on PutBucketTaggingRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the PutBucketTagging operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putBucketVersioning
```
default CompletableFuture<PutBucketVersioningResponse> putBucketVersioning(PutBucketVersioningRequest putBucketVersioningRequest)
```
    Sets the versioning state of an existing bucket. To set the versioning state, you must be the bucket owner.
    
    You can set the versioning state with one of the following values:
    
    Enabled—Enables versioning for the objects in the bucket. All objects added to the bucket receive a unique version ID.
    
    Suspended—Disables versioning for the objects in the bucket. All objects added to the bucket receive the version ID null.
    
    If the versioning state has never been set on a bucket, it has no versioning state; a GetBucketVersioning request does not return a versioning state value.
    
    If the bucket owner enables MFA Delete in the bucket versioning configuration, the bucket owner must include the x-amz-mfa request header and the Status and the MfaDelete request elements in a request to set the versioning state of the bucket.
    
    If you have an object expiration lifecycle policy in your non-versioned bucket and you want to maintain the same permanent delete behavior when you enable versioning, you must add a noncurrent expiration policy. The noncurrent expiration lifecycle policy will manage the deletes of the noncurrent object versions in the version-enabled bucket. (A version-enabled bucket maintains one current and zero or more noncurrent object versions.) For more information, see Lifecycle and Versioning.
    
    Related Resources
    Parameters:
    
    putBucketVersioningRequest -
    
    Returns:
    A Java Future containing the result of the PutBucketVersioning operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putBucketVersioning
```
default CompletableFuture<PutBucketVersioningResponse> putBucketVersioning(Consumer<PutBucketVersioningRequest.Builder> putBucketVersioningRequest)
```
    Sets the versioning state of an existing bucket. To set the versioning state, you must be the bucket owner.
    
    You can set the versioning state with one of the following values:
    
    Enabled—Enables versioning for the objects in the bucket. All objects added to the bucket receive a unique version ID.
    
    Suspended—Disables versioning for the objects in the bucket. All objects added to the bucket receive the version ID null.
    
    If the versioning state has never been set on a bucket, it has no versioning state; a GetBucketVersioning request does not return a versioning state value.
    
    If the bucket owner enables MFA Delete in the bucket versioning configuration, the bucket owner must include the x-amz-mfa request header and the Status and the MfaDelete request elements in a request to set the versioning state of the bucket.
    
    If you have an object expiration lifecycle policy in your non-versioned bucket and you want to maintain the same permanent delete behavior when you enable versioning, you must add a noncurrent expiration policy. The noncurrent expiration lifecycle policy will manage the deletes of the noncurrent object versions in the version-enabled bucket. (A version-enabled bucket maintains one current and zero or more noncurrent object versions.) For more information, see Lifecycle and Versioning.
    
    Related Resources
    This is a convenience which creates an instance of the PutBucketVersioningRequest.Builder avoiding the need to create one manually via PutBucketVersioningRequest.builder()
    Parameters:
    
    putBucketVersioningRequest - A Consumer that will call methods on PutBucketVersioningRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the PutBucketVersioning operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putBucketWebsite
```
default CompletableFuture<PutBucketWebsiteResponse> putBucketWebsite(PutBucketWebsiteRequest putBucketWebsiteRequest)
```
    Sets the configuration of the website that is specified in the website subresource. To configure a bucket as a website, you can add this subresource on the bucket with website configuration information such as the file name of the index document and any redirect rules. For more information, see Hosting Websites on Amazon S3.
    
    This PUT operation requires the S3:PutBucketWebsite permission. By default, only the bucket owner can configure the website attached to a bucket; however, bucket owners can allow other users to set the website configuration by writing a bucket policy that grants them the S3:PutBucketWebsite permission.
    
    To redirect all website requests sent to the bucket's website endpoint, you add a website configuration with the following elements. Because all requests are sent to another website, you don't need to provide index document name for the bucket.
    - WebsiteConfiguration
    - RedirectAllRequestsTo
    - HostName
    - Protocol
    If you want granular control over redirects, you can use the following elements to add routing rules that describe conditions for redirecting requests and information about the redirect destination. In this case, the website configuration must provide an index document for the bucket, because some requests might not be redirected.
    - WebsiteConfiguration
    - IndexDocument
    - Suffix
    - ErrorDocument
    - Key
    - RoutingRules
    - RoutingRule
    - Condition
    - HttpErrorCodeReturnedEquals
    - KeyPrefixEquals
    - Redirect
    - Protocol
    - HostName
    - ReplaceKeyPrefixWith
    - ReplaceKeyWith
    - HttpRedirectCode
    Parameters:
    
    putBucketWebsiteRequest -
    
    Returns:
    A Java Future containing the result of the PutBucketWebsite operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putBucketWebsite
```
default CompletableFuture<PutBucketWebsiteResponse> putBucketWebsite(Consumer<PutBucketWebsiteRequest.Builder> putBucketWebsiteRequest)
```
    Sets the configuration of the website that is specified in the website subresource. To configure a bucket as a website, you can add this subresource on the bucket with website configuration information such as the file name of the index document and any redirect rules. For more information, see Hosting Websites on Amazon S3.
    
    This PUT operation requires the S3:PutBucketWebsite permission. By default, only the bucket owner can configure the website attached to a bucket; however, bucket owners can allow other users to set the website configuration by writing a bucket policy that grants them the S3:PutBucketWebsite permission.
    
    To redirect all website requests sent to the bucket's website endpoint, you add a website configuration with the following elements. Because all requests are sent to another website, you don't need to provide index document name for the bucket.
    - WebsiteConfiguration
    - RedirectAllRequestsTo
    - HostName
    - Protocol
    If you want granular control over redirects, you can use the following elements to add routing rules that describe conditions for redirecting requests and information about the redirect destination. In this case, the website configuration must provide an index document for the bucket, because some requests might not be redirected.
    - WebsiteConfiguration
    - IndexDocument
    - Suffix
    - ErrorDocument
    - Key
    - RoutingRules
    - RoutingRule
    - Condition
    - HttpErrorCodeReturnedEquals
    - KeyPrefixEquals
    - Redirect
    - Protocol
    - HostName
    - ReplaceKeyPrefixWith
    - ReplaceKeyWith
    - HttpRedirectCode
    This is a convenience which creates an instance of the PutBucketWebsiteRequest.Builder avoiding the need to create one manually via PutBucketWebsiteRequest.builder()
    Parameters:
    
    putBucketWebsiteRequest - A Consumer that will call methods on PutBucketWebsiteRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the PutBucketWebsite operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putObject
```
default CompletableFuture<PutObjectResponse> putObject(PutObjectRequest putObjectRequest,
                                                       AsyncRequestBody requestBody)
```
    Adds an object to a bucket. You must have WRITE permissions on a bucket to add an object to it.
    
    Amazon S3 never adds partial objects; if you receive a success response, Amazon S3 added the entire object to the bucket.
    
    Amazon S3 is a distributed system. If it receives multiple write requests for the same object simultaneously, it overwrites all but the last object written. Amazon S3 does not provide object locking; if you need this, make sure to build it into your application layer or use versioning instead.
    
    To ensure that data is not corrupted traversing the network, use the Content-MD5 header. When you use this header, Amazon S3 checks the object against the provided MD5 value and, if they do not match, returns an error. Additionally, you can calculate the MD5 while putting an object to Amazon S3 and compare the returned ETag to the calculated MD5 value.
    
    To configure your application to send the request headers before sending the request body, use the 100-continue HTTP status code. For PUT operations, this helps you avoid sending the message body if the message is rejected based on the headers (for example, because authentication fails or a redirect occurs). For more information on the 100-continue HTTP status code, see Section 8.2.3 of http://www.ietf.org/rfc/rfc2616.txt.
    
    You can optionally request server-side encryption. With server-side encryption, Amazon S3 encrypts your data as it writes it to disks in its data centers and decrypts the data when you access it. You have the option to provide your own encryption key or use AWS managed encryption keys. For more information, see Using Server-Side Encryption.
    Access Permissions
    
    You can optionally specify the accounts or groups that should be granted specific permissions on the new object. There are two ways to grant the permissions using the request headers:
    
    Specify a canned ACL with the x-amz-acl request header. For more information, see Canned ACL.
    
    Specify access permissions explicitly with the x-amz-grant-read, x-amz-grant-read-acp, x-amz-grant-write-acp, and x-amz-grant-full-control headers. These parameters map to the set of permissions that Amazon S3 supports in an ACL. For more information, see Access Control List (ACL) Overview.
    
    You can use either a canned ACL or specify access permissions explicitly. You cannot do both.
    
    Server-Side- Encryption-Specific Request Headers
    
    You can optionally tell Amazon S3 to encrypt data at rest using server-side encryption. Server-side encryption is for data encryption at rest. Amazon S3 encrypts your data as it writes it to disks in its data centers and decrypts it when you access it. The option you use depends on whether you want to use AWS managed encryption keys or provide your own encryption key.
    
    Use encryption keys managed by Amazon S3 or customer master keys (CMKs) stored in AWS Key Management Service (AWS KMS) – If you want AWS to manage the keys used to encrypt data, specify the following headers in the request.
    
    x-amz-server-side-encryption
    
    x-amz-server-side-encryption-aws-kms-key-id
    
    x-amz-server-side-encryption-context
    
    If you specify x-amz-server-side-encryption:aws:kms, but don't provide x-amz-server-side-encryption-aws-kms-key-id, Amazon S3 uses the AWS managed CMK in AWS KMS to protect the data. If you want to use a customer managed AWS KMS CMK, you must provide the x-amz-server-side-encryption-aws-kms-key-id of the symmetric customer managed CMK. Amazon S3 only supports symmetric CMKs and not asymmetric CMKs. For more information, see Using Symmetric and Asymmetric Keys in the AWS Key Management Service Developer Guide.
    
    All GET and PUT requests for an object protected by AWS KMS fail if you don't make them with SSL or by using SigV4.
    
    For more information about server-side encryption with CMKs stored in AWS KMS (SSE-KMS), see Protecting Data Using Server-Side Encryption with CMKs stored in AWS.
    
    Use customer-provided encryption keys – If you want to manage your own encryption keys, provide all the following headers in the request.
    
    x-amz-server-side-encryption-customer-algorithm
    
    x-amz-server-side-encryption-customer-key
    
    x-amz-server-side-encryption-customer-key-MD5
    
    For more information about server-side encryption with CMKs stored in KMS (SSE-KMS), see Protecting Data Using Server-Side Encryption with CMKs stored in AWS.
    
    Access-Control-List (ACL)-Specific Request Headers
    
    You also can use the following access control–related headers with this operation. By default, all objects are private. Only the owner has full access control. When adding a new object, you can grant permissions to individual AWS accounts or to predefined groups defined by Amazon S3. These permissions are then added to the Access Control List (ACL) on the object. For more information, see Using ACLs. With this operation, you can grant access permissions using one of the following two methods:
    
    Specify a canned ACL (x-amz-acl) — Amazon S3 supports a set of predefined ACLs, known as canned ACLs. Each canned ACL has a predefined set of grantees and permissions. For more information, see Canned ACL.
    
    Specify access permissions explicitly — To explicitly grant access permissions to specific AWS accounts or groups, use the following headers. Each header maps to specific permissions that Amazon S3 supports in an ACL. For more information, see Access Control List (ACL) Overview. In the header, you specify a list of grantees who get the specific permission. To grant permissions explicitly use:
    
    x-amz-grant-read
    
    x-amz-grant-write
    
    x-amz-grant-read-acp
    
    x-amz-grant-write-acp
    
    x-amz-grant-full-control
    
    You specify each grantee as a type=value pair, where the type is one of the following:
    
    emailAddress – if the value specified is the email address of an AWS account
    
    Using email addresses to specify a grantee is only supported in the following AWS Regions:
    
    US East (N. Virginia)
    
    US West (N. California)
    
    US West (Oregon)
    
    Asia Pacific (Singapore)
    
    Asia Pacific (Sydney)
    
    Asia Pacific (Tokyo)
    
    EU (Ireland)
    
    South America (São Paulo)
    
    For a list of all the Amazon S3 supported Regions and endpoints, see Regions and Endpoints in the AWS General Reference
    
    id – if the value specified is the canonical user ID of an AWS account
    
    uri – if you are granting permissions to a predefined group
    
    For example, the following x-amz-grant-read header grants the AWS accounts identified by email addresses permissions to read object data and its metadata:
    
    x-amz-grant-read: emailAddress="[email protected]", emailAddress="[email protected]"
    
    Server-Side- Encryption-Specific Request Headers
    
    You can optionally tell Amazon S3 to encrypt data at rest using server-side encryption. Server-side encryption is for data encryption at rest. Amazon S3 encrypts your data as it writes it to disks in its data centers and decrypts it when you access it. The option you use depends on whether you want to use AWS-managed encryption keys or provide your own encryption key.
    
    Use encryption keys managed by Amazon S3 or customer master keys (CMKs) stored in AWS Key Management Service (AWS KMS) – If you want AWS to manage the keys used to encrypt data, specify the following headers in the request.
    
    x-amz-server-side-encryption
    
    x-amz-server-side-encryption-aws-kms-key-id
    
    x-amz-server-side-encryption-context
    
    If you specify x-amz-server-side-encryption:aws:kms, but don't provide x-amz-server-side-encryption-aws-kms-key-id, Amazon S3 uses the AWS managed CMK in AWS KMS to protect the data. If you want to use a customer managed AWS KMS CMK, you must provide the x-amz-server-side-encryption-aws-kms-key-id of the symmetric customer managed CMK. Amazon S3 only supports symmetric CMKs and not asymmetric CMKs. For more information, see Using Symmetric and Asymmetric Keys in the AWS Key Management Service Developer Guide.
    
    All GET and PUT requests for an object protected by AWS KMS fail if you don't make them with SSL or by using SigV4.
    
    For more information about server-side encryption with CMKs stored in AWS KMS (SSE-KMS), see Protecting Data Using Server-Side Encryption with CMKs stored in AWS KMS.
    
    Use customer-provided encryption keys – If you want to manage your own encryption keys, provide all the following headers in the request.
    
    If you use this feature, the ETag value that Amazon S3 returns in the response is not the MD5 of the object.
    
    x-amz-server-side-encryption-customer-algorithm
    
    x-amz-server-side-encryption-customer-key
    
    x-amz-server-side-encryption-customer-key-MD5
    
    For more information about server-side encryption with CMKs stored in AWS KMS (SSE-KMS), see Protecting Data Using Server-Side Encryption with CMKs stored in AWS KMS.
    Storage Class Options
    
    By default, Amazon S3 uses the Standard storage class to store newly created objects. The Standard storage class provides high durability and high availability. You can specify other storage classes depending on the performance needs. For more information, see Storage Classes in the Amazon Simple Storage Service Developer Guide.
    
    Versioning
    
    If you enable versioning for a bucket, Amazon S3 automatically generates a unique version ID for the object being stored. Amazon S3 returns this ID in the response using the x-amz-version-id response header. If versioning is suspended, Amazon S3 always uses null as the version ID for the object stored. For more information about returning the versioning state of a bucket, see GetBucketVersioning. If you enable versioning for a bucket, when Amazon S3 receives multiple write requests for the same object simultaneously, it stores all of the objects.
    
    Related Resources
    - CopyObject
    - DeleteObject
    Parameters:
    
    putObjectRequest -
    
    requestBody - Functional interface that can be implemented to produce the request content in a non-blocking manner. The size of the content is expected to be known up front. See AsyncRequestBody for specific details on implementing this interface as well as links to precanned implementations for common scenarios like uploading from a file. The service documentation for the request content is as follows '
    Object data.
    '
    
    Returns:
    A Java Future containing the result of the PutObject operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putObject
```
default CompletableFuture<PutObjectResponse> putObject(Consumer<PutObjectRequest.Builder> putObjectRequest,
                                                       AsyncRequestBody requestBody)
```
    Adds an object to a bucket. You must have WRITE permissions on a bucket to add an object to it.
    
    Amazon S3 never adds partial objects; if you receive a success response, Amazon S3 added the entire object to the bucket.
    
    Amazon S3 is a distributed system. If it receives multiple write requests for the same object simultaneously, it overwrites all but the last object written. Amazon S3 does not provide object locking; if you need this, make sure to build it into your application layer or use versioning instead.
    
    To ensure that data is not corrupted traversing the network, use the Content-MD5 header. When you use this header, Amazon S3 checks the object against the provided MD5 value and, if they do not match, returns an error. Additionally, you can calculate the MD5 while putting an object to Amazon S3 and compare the returned ETag to the calculated MD5 value.
    
    To configure your application to send the request headers before sending the request body, use the 100-continue HTTP status code. For PUT operations, this helps you avoid sending the message body if the message is rejected based on the headers (for example, because authentication fails or a redirect occurs). For more information on the 100-continue HTTP status code, see Section 8.2.3 of http://www.ietf.org/rfc/rfc2616.txt.
    
    You can optionally request server-side encryption. With server-side encryption, Amazon S3 encrypts your data as it writes it to disks in its data centers and decrypts the data when you access it. You have the option to provide your own encryption key or use AWS managed encryption keys. For more information, see Using Server-Side Encryption.
    Access Permissions
    
    You can optionally specify the accounts or groups that should be granted specific permissions on the new object. There are two ways to grant the permissions using the request headers:
    
    Specify a canned ACL with the x-amz-acl request header. For more information, see Canned ACL.
    
    Specify access permissions explicitly with the x-amz-grant-read, x-amz-grant-read-acp, x-amz-grant-write-acp, and x-amz-grant-full-control headers. These parameters map to the set of permissions that Amazon S3 supports in an ACL. For more information, see Access Control List (ACL) Overview.
    
    You can use either a canned ACL or specify access permissions explicitly. You cannot do both.
    
    Server-Side- Encryption-Specific Request Headers
    
    You can optionally tell Amazon S3 to encrypt data at rest using server-side encryption. Server-side encryption is for data encryption at rest. Amazon S3 encrypts your data as it writes it to disks in its data centers and decrypts it when you access it. The option you use depends on whether you want to use AWS managed encryption keys or provide your own encryption key.
    
    Use encryption keys managed by Amazon S3 or customer master keys (CMKs) stored in AWS Key Management Service (AWS KMS) – If you want AWS to manage the keys used to encrypt data, specify the following headers in the request.
    
    x-amz-server-side-encryption
    
    x-amz-server-side-encryption-aws-kms-key-id
    
    x-amz-server-side-encryption-context
    
    If you specify x-amz-server-side-encryption:aws:kms, but don't provide x-amz-server-side-encryption-aws-kms-key-id, Amazon S3 uses the AWS managed CMK in AWS KMS to protect the data. If you want to use a customer managed AWS KMS CMK, you must provide the x-amz-server-side-encryption-aws-kms-key-id of the symmetric customer managed CMK. Amazon S3 only supports symmetric CMKs and not asymmetric CMKs. For more information, see Using Symmetric and Asymmetric Keys in the AWS Key Management Service Developer Guide.
    
    All GET and PUT requests for an object protected by AWS KMS fail if you don't make them with SSL or by using SigV4.
    
    For more information about server-side encryption with CMKs stored in AWS KMS (SSE-KMS), see Protecting Data Using Server-Side Encryption with CMKs stored in AWS.
    
    Use customer-provided encryption keys – If you want to manage your own encryption keys, provide all the following headers in the request.
    
    x-amz-server-side-encryption-customer-algorithm
    
    x-amz-server-side-encryption-customer-key
    
    x-amz-server-side-encryption-customer-key-MD5
    
    For more information about server-side encryption with CMKs stored in KMS (SSE-KMS), see Protecting Data Using Server-Side Encryption with CMKs stored in AWS.
    
    Access-Control-List (ACL)-Specific Request Headers
    
    You also can use the following access control–related headers with this operation. By default, all objects are private. Only the owner has full access control. When adding a new object, you can grant permissions to individual AWS accounts or to predefined groups defined by Amazon S3. These permissions are then added to the Access Control List (ACL) on the object. For more information, see Using ACLs. With this operation, you can grant access permissions using one of the following two methods:
    
    Specify a canned ACL (x-amz-acl) — Amazon S3 supports a set of predefined ACLs, known as canned ACLs. Each canned ACL has a predefined set of grantees and permissions. For more information, see Canned ACL.
    
    Specify access permissions explicitly — To explicitly grant access permissions to specific AWS accounts or groups, use the following headers. Each header maps to specific permissions that Amazon S3 supports in an ACL. For more information, see Access Control List (ACL) Overview. In the header, you specify a list of grantees who get the specific permission. To grant permissions explicitly use:
    
    x-amz-grant-read
    
    x-amz-grant-write
    
    x-amz-grant-read-acp
    
    x-amz-grant-write-acp
    
    x-amz-grant-full-control
    
    You specify each grantee as a type=value pair, where the type is one of the following:
    
    emailAddress – if the value specified is the email address of an AWS account
    
    Using email addresses to specify a grantee is only supported in the following AWS Regions:
    
    US East (N. Virginia)
    
    US West (N. California)
    
    US West (Oregon)
    
    Asia Pacific (Singapore)
    
    Asia Pacific (Sydney)
    
    Asia Pacific (Tokyo)
    
    EU (Ireland)
    
    South America (São Paulo)
    
    For a list of all the Amazon S3 supported Regions and endpoints, see Regions and Endpoints in the AWS General Reference
    
    id – if the value specified is the canonical user ID of an AWS account
    
    uri – if you are granting permissions to a predefined group
    
    For example, the following x-amz-grant-read header grants the AWS accounts identified by email addresses permissions to read object data and its metadata:
    
    x-amz-grant-read: emailAddress="[email protected]", emailAddress="[email protected]"
    
    Server-Side- Encryption-Specific Request Headers
    
    You can optionally tell Amazon S3 to encrypt data at rest using server-side encryption. Server-side encryption is for data encryption at rest. Amazon S3 encrypts your data as it writes it to disks in its data centers and decrypts it when you access it. The option you use depends on whether you want to use AWS-managed encryption keys or provide your own encryption key.
    
    Use encryption keys managed by Amazon S3 or customer master keys (CMKs) stored in AWS Key Management Service (AWS KMS) – If you want AWS to manage the keys used to encrypt data, specify the following headers in the request.
    
    x-amz-server-side-encryption
    
    x-amz-server-side-encryption-aws-kms-key-id
    
    x-amz-server-side-encryption-context
    
    If you specify x-amz-server-side-encryption:aws:kms, but don't provide x-amz-server-side-encryption-aws-kms-key-id, Amazon S3 uses the AWS managed CMK in AWS KMS to protect the data. If you want to use a customer managed AWS KMS CMK, you must provide the x-amz-server-side-encryption-aws-kms-key-id of the symmetric customer managed CMK. Amazon S3 only supports symmetric CMKs and not asymmetric CMKs. For more information, see Using Symmetric and Asymmetric Keys in the AWS Key Management Service Developer Guide.
    
    All GET and PUT requests for an object protected by AWS KMS fail if you don't make them with SSL or by using SigV4.
    
    For more information about server-side encryption with CMKs stored in AWS KMS (SSE-KMS), see Protecting Data Using Server-Side Encryption with CMKs stored in AWS KMS.
    
    Use customer-provided encryption keys – If you want to manage your own encryption keys, provide all the following headers in the request.
    
    If you use this feature, the ETag value that Amazon S3 returns in the response is not the MD5 of the object.
    
    x-amz-server-side-encryption-customer-algorithm
    
    x-amz-server-side-encryption-customer-key
    
    x-amz-server-side-encryption-customer-key-MD5
    
    For more information about server-side encryption with CMKs stored in AWS KMS (SSE-KMS), see Protecting Data Using Server-Side Encryption with CMKs stored in AWS KMS.
    Storage Class Options
    
    By default, Amazon S3 uses the Standard storage class to store newly created objects. The Standard storage class provides high durability and high availability. You can specify other storage classes depending on the performance needs. For more information, see Storage Classes in the Amazon Simple Storage Service Developer Guide.
    
    Versioning
    
    If you enable versioning for a bucket, Amazon S3 automatically generates a unique version ID for the object being stored. Amazon S3 returns this ID in the response using the x-amz-version-id response header. If versioning is suspended, Amazon S3 always uses null as the version ID for the object stored. For more information about returning the versioning state of a bucket, see GetBucketVersioning. If you enable versioning for a bucket, when Amazon S3 receives multiple write requests for the same object simultaneously, it stores all of the objects.
    
    Related Resources
    - CopyObject
    - DeleteObject
    This is a convenience which creates an instance of the PutObjectRequest.Builder avoiding the need to create one manually via PutObjectRequest.builder()
    Parameters:
    
    putObjectRequest - A Consumer that will call methods on PutObjectRequest.Builder to create a request.
    
    requestBody - Functional interface that can be implemented to produce the request content in a non-blocking manner. The size of the content is expected to be known up front. See AsyncRequestBody for specific details on implementing this interface as well as links to precanned implementations for common scenarios like uploading from a file. The service documentation for the request content is as follows '
    Object data.
    '
    
    Returns:
    A Java Future containing the result of the PutObject operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putObject
```
default CompletableFuture<PutObjectResponse> putObject(PutObjectRequest putObjectRequest,
                                                       Path sourcePath)
```
    Adds an object to a bucket. You must have WRITE permissions on a bucket to add an object to it.
    
    Amazon S3 never adds partial objects; if you receive a success response, Amazon S3 added the entire object to the bucket.
    
    Amazon S3 is a distributed system. If it receives multiple write requests for the same object simultaneously, it overwrites all but the last object written. Amazon S3 does not provide object locking; if you need this, make sure to build it into your application layer or use versioning instead.
    
    To ensure that data is not corrupted traversing the network, use the Content-MD5 header. When you use this header, Amazon S3 checks the object against the provided MD5 value and, if they do not match, returns an error. Additionally, you can calculate the MD5 while putting an object to Amazon S3 and compare the returned ETag to the calculated MD5 value.
    
    To configure your application to send the request headers before sending the request body, use the 100-continue HTTP status code. For PUT operations, this helps you avoid sending the message body if the message is rejected based on the headers (for example, because authentication fails or a redirect occurs). For more information on the 100-continue HTTP status code, see Section 8.2.3 of http://www.ietf.org/rfc/rfc2616.txt.
    
    You can optionally request server-side encryption. With server-side encryption, Amazon S3 encrypts your data as it writes it to disks in its data centers and decrypts the data when you access it. You have the option to provide your own encryption key or use AWS managed encryption keys. For more information, see Using Server-Side Encryption.
    Access Permissions
    
    You can optionally specify the accounts or groups that should be granted specific permissions on the new object. There are two ways to grant the permissions using the request headers:
    
    Specify a canned ACL with the x-amz-acl request header. For more information, see Canned ACL.
    
    Specify access permissions explicitly with the x-amz-grant-read, x-amz-grant-read-acp, x-amz-grant-write-acp, and x-amz-grant-full-control headers. These parameters map to the set of permissions that Amazon S3 supports in an ACL. For more information, see Access Control List (ACL) Overview.
    
    You can use either a canned ACL or specify access permissions explicitly. You cannot do both.
    
    Server-Side- Encryption-Specific Request Headers
    
    You can optionally tell Amazon S3 to encrypt data at rest using server-side encryption. Server-side encryption is for data encryption at rest. Amazon S3 encrypts your data as it writes it to disks in its data centers and decrypts it when you access it. The option you use depends on whether you want to use AWS managed encryption keys or provide your own encryption key.
    
    Use encryption keys managed by Amazon S3 or customer master keys (CMKs) stored in AWS Key Management Service (AWS KMS) – If you want AWS to manage the keys used to encrypt data, specify the following headers in the request.
    
    x-amz-server-side-encryption
    
    x-amz-server-side-encryption-aws-kms-key-id
    
    x-amz-server-side-encryption-context
    
    If you specify x-amz-server-side-encryption:aws:kms, but don't provide x-amz-server-side-encryption-aws-kms-key-id, Amazon S3 uses the AWS managed CMK in AWS KMS to protect the data. If you want to use a customer managed AWS KMS CMK, you must provide the x-amz-server-side-encryption-aws-kms-key-id of the symmetric customer managed CMK. Amazon S3 only supports symmetric CMKs and not asymmetric CMKs. For more information, see Using Symmetric and Asymmetric Keys in the AWS Key Management Service Developer Guide.
    
    All GET and PUT requests for an object protected by AWS KMS fail if you don't make them with SSL or by using SigV4.
    
    For more information about server-side encryption with CMKs stored in AWS KMS (SSE-KMS), see Protecting Data Using Server-Side Encryption with CMKs stored in AWS.
    
    Use customer-provided encryption keys – If you want to manage your own encryption keys, provide all the following headers in the request.
    
    x-amz-server-side-encryption-customer-algorithm
    
    x-amz-server-side-encryption-customer-key
    
    x-amz-server-side-encryption-customer-key-MD5
    
    For more information about server-side encryption with CMKs stored in KMS (SSE-KMS), see Protecting Data Using Server-Side Encryption with CMKs stored in AWS.
    
    Access-Control-List (ACL)-Specific Request Headers
    
    You also can use the following access control–related headers with this operation. By default, all objects are private. Only the owner has full access control. When adding a new object, you can grant permissions to individual AWS accounts or to predefined groups defined by Amazon S3. These permissions are then added to the Access Control List (ACL) on the object. For more information, see Using ACLs. With this operation, you can grant access permissions using one of the following two methods:
    
    Specify a canned ACL (x-amz-acl) — Amazon S3 supports a set of predefined ACLs, known as canned ACLs. Each canned ACL has a predefined set of grantees and permissions. For more information, see Canned ACL.
    
    Specify access permissions explicitly — To explicitly grant access permissions to specific AWS accounts or groups, use the following headers. Each header maps to specific permissions that Amazon S3 supports in an ACL. For more information, see Access Control List (ACL) Overview. In the header, you specify a list of grantees who get the specific permission. To grant permissions explicitly use:
    
    x-amz-grant-read
    
    x-amz-grant-write
    
    x-amz-grant-read-acp
    
    x-amz-grant-write-acp
    
    x-amz-grant-full-control
    
    You specify each grantee as a type=value pair, where the type is one of the following:
    
    emailAddress – if the value specified is the email address of an AWS account
    
    Using email addresses to specify a grantee is only supported in the following AWS Regions:
    
    US East (N. Virginia)
    
    US West (N. California)
    
    US West (Oregon)
    
    Asia Pacific (Singapore)
    
    Asia Pacific (Sydney)
    
    Asia Pacific (Tokyo)
    
    EU (Ireland)
    
    South America (São Paulo)
    
    For a list of all the Amazon S3 supported Regions and endpoints, see Regions and Endpoints in the AWS General Reference
    
    id – if the value specified is the canonical user ID of an AWS account
    
    uri – if you are granting permissions to a predefined group
    
    For example, the following x-amz-grant-read header grants the AWS accounts identified by email addresses permissions to read object data and its metadata:
    
    x-amz-grant-read: emailAddress="[email protected]", emailAddress="[email protected]"
    
    Server-Side- Encryption-Specific Request Headers
    
    You can optionally tell Amazon S3 to encrypt data at rest using server-side encryption. Server-side encryption is for data encryption at rest. Amazon S3 encrypts your data as it writes it to disks in its data centers and decrypts it when you access it. The option you use depends on whether you want to use AWS-managed encryption keys or provide your own encryption key.
    
    Use encryption keys managed by Amazon S3 or customer master keys (CMKs) stored in AWS Key Management Service (AWS KMS) – If you want AWS to manage the keys used to encrypt data, specify the following headers in the request.
    
    x-amz-server-side-encryption
    
    x-amz-server-side-encryption-aws-kms-key-id
    
    x-amz-server-side-encryption-context
    
    If you specify x-amz-server-side-encryption:aws:kms, but don't provide x-amz-server-side-encryption-aws-kms-key-id, Amazon S3 uses the AWS managed CMK in AWS KMS to protect the data. If you want to use a customer managed AWS KMS CMK, you must provide the x-amz-server-side-encryption-aws-kms-key-id of the symmetric customer managed CMK. Amazon S3 only supports symmetric CMKs and not asymmetric CMKs. For more information, see Using Symmetric and Asymmetric Keys in the AWS Key Management Service Developer Guide.
    
    All GET and PUT requests for an object protected by AWS KMS fail if you don't make them with SSL or by using SigV4.
    
    For more information about server-side encryption with CMKs stored in AWS KMS (SSE-KMS), see Protecting Data Using Server-Side Encryption with CMKs stored in AWS KMS.
    
    Use customer-provided encryption keys – If you want to manage your own encryption keys, provide all the following headers in the request.
    
    If you use this feature, the ETag value that Amazon S3 returns in the response is not the MD5 of the object.
    
    x-amz-server-side-encryption-customer-algorithm
    
    x-amz-server-side-encryption-customer-key
    
    x-amz-server-side-encryption-customer-key-MD5
    
    For more information about server-side encryption with CMKs stored in AWS KMS (SSE-KMS), see Protecting Data Using Server-Side Encryption with CMKs stored in AWS KMS.
    Storage Class Options
    
    By default, Amazon S3 uses the Standard storage class to store newly created objects. The Standard storage class provides high durability and high availability. You can specify other storage classes depending on the performance needs. For more information, see Storage Classes in the Amazon Simple Storage Service Developer Guide.
    
    Versioning
    
    If you enable versioning for a bucket, Amazon S3 automatically generates a unique version ID for the object being stored. Amazon S3 returns this ID in the response using the x-amz-version-id response header. If versioning is suspended, Amazon S3 always uses null as the version ID for the object stored. For more information about returning the versioning state of a bucket, see GetBucketVersioning. If you enable versioning for a bucket, when Amazon S3 receives multiple write requests for the same object simultaneously, it stores all of the objects.
    
    Related Resources
    - CopyObject
    - DeleteObject
    Parameters:
    
    putObjectRequest -
    
    sourcePath - Path to file containing data to send to the service. File will be read entirely and may be read multiple times in the event of a retry. If the file does not exist or the current user does not have access to read it then an exception will be thrown. The service documentation for the request content is as follows '
    Object data.
    '
    
    Returns:
    A Java Future containing the result of the PutObject operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putObject
```
default CompletableFuture<PutObjectResponse> putObject(Consumer<PutObjectRequest.Builder> putObjectRequest,
                                                       Path sourcePath)
```
    Adds an object to a bucket. You must have WRITE permissions on a bucket to add an object to it.
    
    Amazon S3 never adds partial objects; if you receive a success response, Amazon S3 added the entire object to the bucket.
    
    Amazon S3 is a distributed system. If it receives multiple write requests for the same object simultaneously, it overwrites all but the last object written. Amazon S3 does not provide object locking; if you need this, make sure to build it into your application layer or use versioning instead.
    
    To ensure that data is not corrupted traversing the network, use the Content-MD5 header. When you use this header, Amazon S3 checks the object against the provided MD5 value and, if they do not match, returns an error. Additionally, you can calculate the MD5 while putting an object to Amazon S3 and compare the returned ETag to the calculated MD5 value.
    
    To configure your application to send the request headers before sending the request body, use the 100-continue HTTP status code. For PUT operations, this helps you avoid sending the message body if the message is rejected based on the headers (for example, because authentication fails or a redirect occurs). For more information on the 100-continue HTTP status code, see Section 8.2.3 of http://www.ietf.org/rfc/rfc2616.txt.
    
    You can optionally request server-side encryption. With server-side encryption, Amazon S3 encrypts your data as it writes it to disks in its data centers and decrypts the data when you access it. You have the option to provide your own encryption key or use AWS managed encryption keys. For more information, see Using Server-Side Encryption.
    Access Permissions
    
    You can optionally specify the accounts or groups that should be granted specific permissions on the new object. There are two ways to grant the permissions using the request headers:
    
    Specify a canned ACL with the x-amz-acl request header. For more information, see Canned ACL.
    
    Specify access permissions explicitly with the x-amz-grant-read, x-amz-grant-read-acp, x-amz-grant-write-acp, and x-amz-grant-full-control headers. These parameters map to the set of permissions that Amazon S3 supports in an ACL. For more information, see Access Control List (ACL) Overview.
    
    You can use either a canned ACL or specify access permissions explicitly. You cannot do both.
    
    Server-Side- Encryption-Specific Request Headers
    
    You can optionally tell Amazon S3 to encrypt data at rest using server-side encryption. Server-side encryption is for data encryption at rest. Amazon S3 encrypts your data as it writes it to disks in its data centers and decrypts it when you access it. The option you use depends on whether you want to use AWS managed encryption keys or provide your own encryption key.
    
    Use encryption keys managed by Amazon S3 or customer master keys (CMKs) stored in AWS Key Management Service (AWS KMS) – If you want AWS to manage the keys used to encrypt data, specify the following headers in the request.
    
    x-amz-server-side-encryption
    
    x-amz-server-side-encryption-aws-kms-key-id
    
    x-amz-server-side-encryption-context
    
    If you specify x-amz-server-side-encryption:aws:kms, but don't provide x-amz-server-side-encryption-aws-kms-key-id, Amazon S3 uses the AWS managed CMK in AWS KMS to protect the data. If you want to use a customer managed AWS KMS CMK, you must provide the x-amz-server-side-encryption-aws-kms-key-id of the symmetric customer managed CMK. Amazon S3 only supports symmetric CMKs and not asymmetric CMKs. For more information, see Using Symmetric and Asymmetric Keys in the AWS Key Management Service Developer Guide.
    
    All GET and PUT requests for an object protected by AWS KMS fail if you don't make them with SSL or by using SigV4.
    
    For more information about server-side encryption with CMKs stored in AWS KMS (SSE-KMS), see Protecting Data Using Server-Side Encryption with CMKs stored in AWS.
    
    Use customer-provided encryption keys – If you want to manage your own encryption keys, provide all the following headers in the request.
    
    x-amz-server-side-encryption-customer-algorithm
    
    x-amz-server-side-encryption-customer-key
    
    x-amz-server-side-encryption-customer-key-MD5
    
    For more information about server-side encryption with CMKs stored in KMS (SSE-KMS), see Protecting Data Using Server-Side Encryption with CMKs stored in AWS.
    
    Access-Control-List (ACL)-Specific Request Headers
    
    You also can use the following access control–related headers with this operation. By default, all objects are private. Only the owner has full access control. When adding a new object, you can grant permissions to individual AWS accounts or to predefined groups defined by Amazon S3. These permissions are then added to the Access Control List (ACL) on the object. For more information, see Using ACLs. With this operation, you can grant access permissions using one of the following two methods:
    
    Specify a canned ACL (x-amz-acl) — Amazon S3 supports a set of predefined ACLs, known as canned ACLs. Each canned ACL has a predefined set of grantees and permissions. For more information, see Canned ACL.
    
    Specify access permissions explicitly — To explicitly grant access permissions to specific AWS accounts or groups, use the following headers. Each header maps to specific permissions that Amazon S3 supports in an ACL. For more information, see Access Control List (ACL) Overview. In the header, you specify a list of grantees who get the specific permission. To grant permissions explicitly use:
    
    x-amz-grant-read
    
    x-amz-grant-write
    
    x-amz-grant-read-acp
    
    x-amz-grant-write-acp
    
    x-amz-grant-full-control
    
    You specify each grantee as a type=value pair, where the type is one of the following:
    
    emailAddress – if the value specified is the email address of an AWS account
    
    Using email addresses to specify a grantee is only supported in the following AWS Regions:
    
    US East (N. Virginia)
    
    US West (N. California)
    
    US West (Oregon)
    
    Asia Pacific (Singapore)
    
    Asia Pacific (Sydney)
    
    Asia Pacific (Tokyo)
    
    EU (Ireland)
    
    South America (São Paulo)
    
    For a list of all the Amazon S3 supported Regions and endpoints, see Regions and Endpoints in the AWS General Reference
    
    id – if the value specified is the canonical user ID of an AWS account
    
    uri – if you are granting permissions to a predefined group
    
    For example, the following x-amz-grant-read header grants the AWS accounts identified by email addresses permissions to read object data and its metadata:
    
    x-amz-grant-read: emailAddress="[email protected]", emailAddress="[email protected]"
    
    Server-Side- Encryption-Specific Request Headers
    
    You can optionally tell Amazon S3 to encrypt data at rest using server-side encryption. Server-side encryption is for data encryption at rest. Amazon S3 encrypts your data as it writes it to disks in its data centers and decrypts it when you access it. The option you use depends on whether you want to use AWS-managed encryption keys or provide your own encryption key.
    
    Use encryption keys managed by Amazon S3 or customer master keys (CMKs) stored in AWS Key Management Service (AWS KMS) – If you want AWS to manage the keys used to encrypt data, specify the following headers in the request.
    
    x-amz-server-side-encryption
    
    x-amz-server-side-encryption-aws-kms-key-id
    
    x-amz-server-side-encryption-context
    
    If you specify x-amz-server-side-encryption:aws:kms, but don't provide x-amz-server-side-encryption-aws-kms-key-id, Amazon S3 uses the AWS managed CMK in AWS KMS to protect the data. If you want to use a customer managed AWS KMS CMK, you must provide the x-amz-server-side-encryption-aws-kms-key-id of the symmetric customer managed CMK. Amazon S3 only supports symmetric CMKs and not asymmetric CMKs. For more information, see Using Symmetric and Asymmetric Keys in the AWS Key Management Service Developer Guide.
    
    All GET and PUT requests for an object protected by AWS KMS fail if you don't make them with SSL or by using SigV4.
    
    For more information about server-side encryption with CMKs stored in AWS KMS (SSE-KMS), see Protecting Data Using Server-Side Encryption with CMKs stored in AWS KMS.
    
    Use customer-provided encryption keys – If you want to manage your own encryption keys, provide all the following headers in the request.
    
    If you use this feature, the ETag value that Amazon S3 returns in the response is not the MD5 of the object.
    
    x-amz-server-side-encryption-customer-algorithm
    
    x-amz-server-side-encryption-customer-key
    
    x-amz-server-side-encryption-customer-key-MD5
    
    For more information about server-side encryption with CMKs stored in AWS KMS (SSE-KMS), see Protecting Data Using Server-Side Encryption with CMKs stored in AWS KMS.
    Storage Class Options
    
    By default, Amazon S3 uses the Standard storage class to store newly created objects. The Standard storage class provides high durability and high availability. You can specify other storage classes depending on the performance needs. For more information, see Storage Classes in the Amazon Simple Storage Service Developer Guide.
    
    Versioning
    
    If you enable versioning for a bucket, Amazon S3 automatically generates a unique version ID for the object being stored. Amazon S3 returns this ID in the response using the x-amz-version-id response header. If versioning is suspended, Amazon S3 always uses null as the version ID for the object stored. For more information about returning the versioning state of a bucket, see GetBucketVersioning. If you enable versioning for a bucket, when Amazon S3 receives multiple write requests for the same object simultaneously, it stores all of the objects.
    
    Related Resources
    - CopyObject
    - DeleteObject
    This is a convenience which creates an instance of the PutObjectRequest.Builder avoiding the need to create one manually via PutObjectRequest.builder()
    Parameters:
    
    putObjectRequest - A Consumer that will call methods on PutObjectRequest.Builder to create a request.
    
    sourcePath - Path to file containing data to send to the service. File will be read entirely and may be read multiple times in the event of a retry. If the file does not exist or the current user does not have access to read it then an exception will be thrown. The service documentation for the request content is as follows '
    Object data.
    '
    
    Returns:
    A Java Future containing the result of the PutObject operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putObjectAcl
```
default CompletableFuture<PutObjectAclResponse> putObjectAcl(PutObjectAclRequest putObjectAclRequest)
```
    Uses the acl subresource to set the access control list (ACL) permissions for an object that already exists in a bucket. You must have WRITE_ACP permission to set the ACL of an object.
    
    Depending on your application needs, you can choose to set the ACL on an object using either the request body or the headers. For example, if you have an existing application that updates a bucket ACL using the request body, you can continue to use that approach.
    
    Access Permissions
    
    You can set access permissions using one of the following methods:
    - Specify a canned ACL with the x-amz-acl request header. Amazon S3 supports a set of predefined ACLs, known as canned ACLs. Each canned ACL has a predefined set of grantees and permissions. Specify the canned ACL name as the value of x-amz-acl. If you use this header, you cannot use other access control-specific headers in your request. For more information, see Canned ACL.
    - Specify access permissions explicitly with the x-amz-grant-read, x-amz-grant-read-acp, x-amz-grant-write-acp, and x-amz-grant-full-control headers. When using these headers, you specify explicit access permissions and grantees (AWS accounts or Amazon S3 groups) who will receive the permission. If you use these ACL-specific headers, you cannot use x-amz-acl header to set a canned ACL. These parameters map to the set of permissions that Amazon S3 supports in an ACL. For more information, see Access Control List (ACL) Overview.
      
      You specify each grantee as a type=value pair, where the type is one of the following:
      
      emailAddress – if the value specified is the email address of an AWS account
      
      id – if the value specified is the canonical user ID of an AWS account
      
      uri – if you are granting permissions to a predefined group
      
      For example, the following x-amz-grant-read header grants list objects permission to the two AWS accounts identified by their email addresses.
      
      x-amz-grant-read: emailAddress="[email protected]", emailAddress="[email protected]"
    You can use either a canned ACL or specify access permissions explicitly. You cannot do both.
    
    Grantee Values
    
    You can specify the person (grantee) to whom you're assigning access rights (using request elements) in the following ways:
    - By Email address:
      
      <Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="AmazonCustomerByEmail"><EmailAddress><>[email protected]<></EmailAddress>lt;/Grantee>
      
      The grantee is resolved to the CanonicalUser and, in a response to a GET Object acl request, appears as the CanonicalUser.
    - By the person's ID:
      
      <Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="CanonicalUser"><ID><>ID<></ID><DisplayName><>GranteesEmail<></DisplayName> </Grantee>
      
      DisplayName is optional and ignored in the request.
    - By URI:
      
      <Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="Group"><URI><>http://acs.amazonaws.com/groups/global/AuthenticatedUsers<></URI></Grantee>
    Versioning
    
    The ACL of an object is set at the object version level. By default, PUT sets the ACL of the current version of an object. To set the ACL of a different version, use the versionId subresource.
    
    Related Resources
    - CopyObject
    - GetObject
    Parameters:
    
    putObjectAclRequest -
    
    Returns:
    A Java Future containing the result of the PutObjectAcl operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    NoSuchKeyException The specified key does not exist.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putObjectAcl
```
default CompletableFuture<PutObjectAclResponse> putObjectAcl(Consumer<PutObjectAclRequest.Builder> putObjectAclRequest)
```
    Uses the acl subresource to set the access control list (ACL) permissions for an object that already exists in a bucket. You must have WRITE_ACP permission to set the ACL of an object.
    
    Depending on your application needs, you can choose to set the ACL on an object using either the request body or the headers. For example, if you have an existing application that updates a bucket ACL using the request body, you can continue to use that approach.
    
    Access Permissions
    
    You can set access permissions using one of the following methods:
    - Specify a canned ACL with the x-amz-acl request header. Amazon S3 supports a set of predefined ACLs, known as canned ACLs. Each canned ACL has a predefined set of grantees and permissions. Specify the canned ACL name as the value of x-amz-acl. If you use this header, you cannot use other access control-specific headers in your request. For more information, see Canned ACL.
    - Specify access permissions explicitly with the x-amz-grant-read, x-amz-grant-read-acp, x-amz-grant-write-acp, and x-amz-grant-full-control headers. When using these headers, you specify explicit access permissions and grantees (AWS accounts or Amazon S3 groups) who will receive the permission. If you use these ACL-specific headers, you cannot use x-amz-acl header to set a canned ACL. These parameters map to the set of permissions that Amazon S3 supports in an ACL. For more information, see Access Control List (ACL) Overview.
      
      You specify each grantee as a type=value pair, where the type is one of the following:
      
      emailAddress – if the value specified is the email address of an AWS account
      
      id – if the value specified is the canonical user ID of an AWS account
      
      uri – if you are granting permissions to a predefined group
      
      For example, the following x-amz-grant-read header grants list objects permission to the two AWS accounts identified by their email addresses.
      
      x-amz-grant-read: emailAddress="[email protected]", emailAddress="[email protected]"
    You can use either a canned ACL or specify access permissions explicitly. You cannot do both.
    
    Grantee Values
    
    You can specify the person (grantee) to whom you're assigning access rights (using request elements) in the following ways:
    - By Email address:
      
      <Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="AmazonCustomerByEmail"><EmailAddress><>[email protected]<></EmailAddress>lt;/Grantee>
      
      The grantee is resolved to the CanonicalUser and, in a response to a GET Object acl request, appears as the CanonicalUser.
    - By the person's ID:
      
      <Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="CanonicalUser"><ID><>ID<></ID><DisplayName><>GranteesEmail<></DisplayName> </Grantee>
      
      DisplayName is optional and ignored in the request.
    - By URI:
      
      <Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="Group"><URI><>http://acs.amazonaws.com/groups/global/AuthenticatedUsers<></URI></Grantee>
    Versioning
    
    The ACL of an object is set at the object version level. By default, PUT sets the ACL of the current version of an object. To set the ACL of a different version, use the versionId subresource.
    
    Related Resources
    - CopyObject
    - GetObject
    This is a convenience which creates an instance of the PutObjectAclRequest.Builder avoiding the need to create one manually via PutObjectAclRequest.builder()
    Parameters:
    
    putObjectAclRequest - A Consumer that will call methods on PutObjectAclRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the PutObjectAcl operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    NoSuchKeyException The specified key does not exist.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putObjectLegalHold
```
default CompletableFuture<PutObjectLegalHoldResponse> putObjectLegalHold(PutObjectLegalHoldRequest putObjectLegalHoldRequest)
```
    Applies a Legal Hold configuration to the specified object.
    
    Related Resources
    - Locking Objects
    Parameters:
    
    putObjectLegalHoldRequest -
    
    Returns:
    A Java Future containing the result of the PutObjectLegalHold operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putObjectLegalHold
```
default CompletableFuture<PutObjectLegalHoldResponse> putObjectLegalHold(Consumer<PutObjectLegalHoldRequest.Builder> putObjectLegalHoldRequest)
```
    Applies a Legal Hold configuration to the specified object.
    
    Related Resources
    - Locking Objects
    This is a convenience which creates an instance of the PutObjectLegalHoldRequest.Builder avoiding the need to create one manually via PutObjectLegalHoldRequest.builder()
    Parameters:
    
    putObjectLegalHoldRequest - A Consumer that will call methods on PutObjectLegalHoldRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the PutObjectLegalHold operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putObjectLockConfiguration
```
default CompletableFuture<PutObjectLockConfigurationResponse> putObjectLockConfiguration(PutObjectLockConfigurationRequest putObjectLockConfigurationRequest)
```
    Places an Object Lock configuration on the specified bucket. The rule specified in the Object Lock configuration will be applied by default to every new object placed in the specified bucket.
    
    DefaultRetention requires either Days or Years. You can't specify both at the same time.
    
    Related Resources
    - Locking Objects
    Parameters:
    
    putObjectLockConfigurationRequest -
    
    Returns:
    A Java Future containing the result of the PutObjectLockConfiguration operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putObjectLockConfiguration
```
default CompletableFuture<PutObjectLockConfigurationResponse> putObjectLockConfiguration(Consumer<PutObjectLockConfigurationRequest.Builder> putObjectLockConfigurationRequest)
```
    Places an Object Lock configuration on the specified bucket. The rule specified in the Object Lock configuration will be applied by default to every new object placed in the specified bucket.
    
    DefaultRetention requires either Days or Years. You can't specify both at the same time.
    
    Related Resources
    - Locking Objects
    This is a convenience which creates an instance of the PutObjectLockConfigurationRequest.Builder avoiding the need to create one manually via PutObjectLockConfigurationRequest.builder()
    Parameters:
    
    putObjectLockConfigurationRequest - A Consumer that will call methods on PutObjectLockConfigurationRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the PutObjectLockConfiguration operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putObjectRetention
```
default CompletableFuture<PutObjectRetentionResponse> putObjectRetention(PutObjectRetentionRequest putObjectRetentionRequest)
```
    Places an Object Retention configuration on an object.
    
    Related Resources
    - Locking Objects
    Parameters:
    
    putObjectRetentionRequest -
    
    Returns:
    A Java Future containing the result of the PutObjectRetention operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putObjectRetention
```
default CompletableFuture<PutObjectRetentionResponse> putObjectRetention(Consumer<PutObjectRetentionRequest.Builder> putObjectRetentionRequest)
```
    Places an Object Retention configuration on an object.
    
    Related Resources
    - Locking Objects
    This is a convenience which creates an instance of the PutObjectRetentionRequest.Builder avoiding the need to create one manually via PutObjectRetentionRequest.builder()
    Parameters:
    
    putObjectRetentionRequest - A Consumer that will call methods on PutObjectRetentionRequest.Builder to create a request.
    
    Returns:
    A Java Future containing the result of the PutObjectRetention operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  - putObjectTagging
```
default CompletableFuture<PutObjectTaggingResponse> putObjectTagging(PutObjectTaggingRequest putObjectTaggingRequest)
```
    Sets the supplied tag-set to an object that already exists in a bucket
    
    A tag is a key-value pair. You can associate tags with an object by sending a PUT request against the tagging subresource that is associated with the object. You can retrieve tags by sending a GET request. For more information, see GetObjectTagging.
    
    For tagging-related restrictions related to characters and encodings, see Tag Restrictions. Note that Amazon S3 limits the maximum number of tags to 10 tags per object.
    
    To use this operation, you must have permission to perform the s3:PutObjectTagging action. By default, the bucket owner has this permission and can grant this permission to others.
    
    To put tags of any other version, use the versionId query parameter. You also need permission for the s3:PutObjectVersionTagging action.
    
    For information about the Amazon S3 object tagging feature, see Object Tagging.
    
    Special Errors
    - Code: InvalidTagError
      
      Cause: The tag provided was not a valid tag. This error can occur if the tag did not pass input validation. For more information, see Object Tagging.
    Related Resources
    
    GetObjectTagging
    Parameters:
    
    putObjectTaggingRequest -
    
    Returns:
    
    A Java Future containing the result of the PutObjectTagging operation returned by the service.
    The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
    
    SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
    
    SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
    
    S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  putObjectTagging
  
  default CompletableFuture<PutObjectTaggingResponse> putObjectTagging(Consumer<PutObjectTaggingRequest.Builder> putObjectTaggingRequest)
  
  Sets the supplied tag-set to an object that already exists in a bucket
  
  A tag is a key-value pair. You can associate tags with an object by sending a PUT request against the tagging subresource that is associated with the object. You can retrieve tags by sending a GET request. For more information, see GetObjectTagging.
  
  For tagging-related restrictions related to characters and encodings, see Tag Restrictions. Note that Amazon S3 limits the maximum number of tags to 10 tags per object.
  
  To use this operation, you must have permission to perform the s3:PutObjectTagging action. By default, the bucket owner has this permission and can grant this permission to others.
  
  To put tags of any other version, use the versionId query parameter. You also need permission for the s3:PutObjectVersionTagging action.
  
  For information about the Amazon S3 object tagging feature, see Object Tagging.
  
  Special Errors
  
  Code: InvalidTagError
  
  Cause: The tag provided was not a valid tag. This error can occur if the tag did not pass input validation. For more information, see Object Tagging.
  
  Code: MalformedXMLError
  
  Cause: The XML provided does not match the schema.
  
  Code: OperationAbortedError
  
  Cause: A conflicting conditional operation is currently in progress against this resource. Please try again.
  
  Code: InternalError
  
  Cause: The service was unable to apply the provided tag to the object.
  
  Related Resources
  
  GetObjectTagging
  
  This is a convenience which creates an instance of the PutObjectTaggingRequest.Builder avoiding the need to create one manually via PutObjectTaggingRequest.builder()
  
  Parameters:
  
  putObjectTaggingRequest - A Consumer that will call methods on PutObjectTaggingRequest.Builder to create a request.
  
  Returns:
  
  A Java Future containing the result of the PutObjectTagging operation returned by the service.
  The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
  
  SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
  
  SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
  
  S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  
  putPublicAccessBlock
  
  default CompletableFuture<PutPublicAccessBlockResponse> putPublicAccessBlock(PutPublicAccessBlockRequest putPublicAccessBlockRequest)
  
  Creates or modifies the PublicAccessBlock configuration for an Amazon S3 bucket. To use this operation, you must have the s3:PutBucketPublicAccessBlock permission. For more information about Amazon S3 permissions, see Specifying Permissions in a Policy.
  
  When Amazon S3 evaluates the PublicAccessBlock configuration for a bucket or an object, it checks the PublicAccessBlock configuration for both the bucket (or the bucket that contains the object) and the bucket owner's account. If the PublicAccessBlock configurations are different between the bucket and the account, Amazon S3 uses the most restrictive combination of the bucket-level and account-level settings.
  
  For more information about when Amazon S3 considers a bucket or an object public, see The Meaning of "Public".
  
  Related Resources
  
  GetPublicAccessBlock
  
  DeletePublicAccessBlock
  
  GetBucketPolicyStatus
  
  Using Amazon S3 Block Public Access
  
  Parameters:
  
  putPublicAccessBlockRequest -
  
  Returns:
  
  A Java Future containing the result of the PutPublicAccessBlock operation returned by the service.
  The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
  
  SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
  
  SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
  
  S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  
  putPublicAccessBlock
  
  default CompletableFuture<PutPublicAccessBlockResponse> putPublicAccessBlock(Consumer<PutPublicAccessBlockRequest.Builder> putPublicAccessBlockRequest)
  
  Creates or modifies the PublicAccessBlock configuration for an Amazon S3 bucket. To use this operation, you must have the s3:PutBucketPublicAccessBlock permission. For more information about Amazon S3 permissions, see Specifying Permissions in a Policy.
  
  When Amazon S3 evaluates the PublicAccessBlock configuration for a bucket or an object, it checks the PublicAccessBlock configuration for both the bucket (or the bucket that contains the object) and the bucket owner's account. If the PublicAccessBlock configurations are different between the bucket and the account, Amazon S3 uses the most restrictive combination of the bucket-level and account-level settings.
  
  For more information about when Amazon S3 considers a bucket or an object public, see The Meaning of "Public".
  
  Related Resources
  
  GetPublicAccessBlock
  
  DeletePublicAccessBlock
  
  GetBucketPolicyStatus
  
  Using Amazon S3 Block Public Access
  
  This is a convenience which creates an instance of the PutPublicAccessBlockRequest.Builder avoiding the need to create one manually via PutPublicAccessBlockRequest.builder()
  
  Parameters:
  
  putPublicAccessBlockRequest - A Consumer that will call methods on PutPublicAccessBlockRequest.Builder to create a request.
  
  Returns:
  
  A Java Future containing the result of the PutPublicAccessBlock operation returned by the service.
  The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
  
  SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
  
  SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
  
  S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  
  restoreObject
  
  default CompletableFuture<RestoreObjectResponse> restoreObject(RestoreObjectRequest restoreObjectRequest)
  
  Restores an archived copy of an object back into Amazon S3
  
  This operation performs the following types of requests:
  
  select - Perform a select query on an archived object
  
  restore an archive - Restore an archived object
  
  To use this operation, you must have permissions to perform the s3:RestoreObject and s3:GetObject actions. The bucket owner has this permission by default and can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources in the Amazon Simple Storage Service Developer Guide.
  
  Querying Archives with Select Requests
  
  You use a select type of request to perform SQL queries on archived objects. The archived objects that are being queried by the select request must be formatted as uncompressed comma-separated values (CSV) files. You can run queries and custom analytics on your archived data without having to restore your data to a hotter Amazon S3 tier. For an overview about select requests, see Querying Archived Objects in the Amazon Simple Storage Service Developer Guide.
  
  When making a select request, do the following:
  
  Define an output location for the select query's output. This must be an Amazon S3 bucket in the same AWS Region as the bucket that contains the archive object that is being queried. The AWS account that initiates the job must have permissions to write to the S3 bucket. You can specify the storage class and encryption for the output objects stored in the bucket. For more information about output, see Querying Archived Objects in the Amazon Simple Storage Service Developer Guide.
  
  For more information about the S3 structure in the request body, see the following:
  
  PutObject
  
  Managing Access with ACLs in the Amazon Simple Storage Service Developer Guide
  
  Protecting Data Using Server-Side Encryption in the Amazon Simple Storage Service Developer Guide
  
  Define the SQL expression for the SELECT type of restoration for your query in the request body's SelectParameters structure. You can use expressions like the following examples.
  
  The following expression returns all records from the specified object.
  
  SELECT * FROM Object
  
  Assuming that you are not using any headers for data stored in the object, you can specify columns with positional headers.
  
  SELECT s._1, s._2 FROM Object s WHERE s._3 > 100
  
  If you have headers and you set the fileHeaderInfo in the CSV structure in the request body to USE, you can specify headers in the query. (If you set the fileHeaderInfo field to IGNORE, the first row is skipped for the query.) You cannot mix ordinal positions with header column names.
  
  SELECT s.Id, s.FirstName, s.SSN FROM S3Object s
  
  For more information about using SQL with Glacier Select restore, see SQL Reference for Amazon S3 Select and Glacier Select in the Amazon Simple Storage Service Developer Guide.
  
  When making a select request, you can also do the following:
  
  To expedite your queries, specify the Expedited tier. For more information about tiers, see "Restoring Archives," later in this topic.
  
  Specify details about the data serialization format of both the input object that is being queried and the serialization of the CSV-encoded query results.
  
  The following are additional important facts about the select feature:
  
  The output results are new Amazon S3 objects. Unlike archive retrievals, they are stored until explicitly deleted-manually or through a lifecycle policy.
  
  You can issue more than one select request on the same Amazon S3 object. Amazon S3 doesn't deduplicate requests, so avoid issuing duplicate requests.
  
  Amazon S3 accepts a select request even if the object has already been restored. A select request doesn’t return error response 409.
  
  Restoring Archives
  
  Objects in the GLACIER and DEEP_ARCHIVE storage classes are archived. To access an archived object, you must first initiate a restore request. This restores a temporary copy of the archived object. In a restore request, you specify the number of days that you want the restored copy to exist. After the specified period, Amazon S3 deletes the temporary copy but the object remains archived in the GLACIER or DEEP_ARCHIVE storage class that object was restored from.
  
  To restore a specific object version, you can provide a version ID. If you don't provide a version ID, Amazon S3 restores the current version.
  
  The time it takes restore jobs to finish depends on which storage class the object is being restored from and which data access tier you specify.
  
  When restoring an archived object (or using a select request), you can specify one of the following data access tier options in the Tier element of the request body:
  
  Expedited - Expedited retrievals allow you to quickly access your data stored in the GLACIER storage class when occasional urgent requests for a subset of archives are required. For all but the largest archived objects (250 MB+), data accessed using Expedited retrievals are typically made available within 1–5 minutes. Provisioned capacity ensures that retrieval capacity for Expedited retrievals is available when you need it. Expedited retrievals and provisioned capacity are not available for the DEEP_ARCHIVE storage class.
  
  Standard - Standard retrievals allow you to access any of your archived objects within several hours. This is the default option for the GLACIER and DEEP_ARCHIVE retrieval requests that do not specify the retrieval option. Standard retrievals typically complete within 3-5 hours from the GLACIER storage class and typically complete within 12 hours from the DEEP_ARCHIVE storage class.
  
  Bulk - Bulk retrievals are Amazon S3 Glacier’s lowest-cost retrieval option, enabling you to retrieve large amounts, even petabytes, of data inexpensively in a day. Bulk retrievals typically complete within 5-12 hours from the GLACIER storage class and typically complete within 48 hours from the DEEP_ARCHIVE storage class.
  
  For more information about archive retrieval options and provisioned capacity for Expedited data access, see Restoring Archived Objects in the Amazon Simple Storage Service Developer Guide.
  
  You can use Amazon S3 restore speed upgrade to change the restore speed to a faster speed while it is in progress. You upgrade the speed of an in-progress restoration by issuing another restore request to the same object, setting a new Tier request element. When issuing a request to upgrade the restore tier, you must choose a tier that is faster than the tier that the in-progress restore is using. You must not change any other parameters, such as the Days request element. For more information, see Upgrading the Speed of an In-Progress Restore in the Amazon Simple Storage Service Developer Guide.
  
  To get the status of object restoration, you can send a HEAD request. Operations return the x-amz-restore header, which provides information about the restoration status, in the response. You can use Amazon S3 event notifications to notify you when a restore is initiated or completed. For more information, see Configuring Amazon S3 Event Notifications in the Amazon Simple Storage Service Developer Guide.
  
  After restoring an archived object, you can update the restoration period by reissuing the request with a new period. Amazon S3 updates the restoration period relative to the current time and charges only for the request-there are no data transfer charges. You cannot update the restoration period when Amazon S3 is actively processing your current restore request for the object.
  
  If your bucket has a lifecycle configuration with a rule that includes an expiration action, the object expiration overrides the life span that you specify in a restore request. For example, if you restore an object copy for 10 days, but the object is scheduled to expire in 3 days, Amazon S3 deletes the object in 3 days. For more information about lifecycle configuration, see PutBucketLifecycleConfiguration and Object Lifecycle Management in Amazon Simple Storage Service Developer Guide.
  
  Responses
  
  A successful operation returns either the 200 OK or 202 Accepted status code.
  
  If the object copy is not previously restored, then Amazon S3 returns 202 Accepted in the response.
  
  If the object copy is previously restored, Amazon S3 returns 200 OK in the response.
  
  Special Errors
  
  Code: RestoreAlreadyInProgress
  
  Cause: Object restore is already in progress. (This error does not apply to SELECT type requests.)
  
  HTTP Status Code: 409 Conflict
  
  SOAP Fault Code Prefix: Client
  
  Code: GlacierExpeditedRetrievalNotAvailable
  
  Cause: Glacier expedited retrievals are currently not available. Try again later. (Returned if there is insufficient capacity to process the Expedited request. This error applies only to Expedited retrievals and not to Standard or Bulk retrievals.)
  
  HTTP Status Code: 503
  
  SOAP Fault Code Prefix: N/A
  
  Related Resources
  
  PutBucketLifecycleConfiguration
  
  GetBucketNotificationConfiguration
  
  SQL Reference for Amazon S3 Select and Glacier Select in the Amazon Simple Storage Service Developer Guide
  
  Parameters:
  
  restoreObjectRequest -
  
  Returns:
  
  A Java Future containing the result of the RestoreObject operation returned by the service.
  The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
  
  ObjectAlreadyInActiveTierErrorException This operation is not allowed against this storage tier.
  
  SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
  
  SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
  
  S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  
  restoreObject
  
  default CompletableFuture<RestoreObjectResponse> restoreObject(Consumer<RestoreObjectRequest.Builder> restoreObjectRequest)
  
  Restores an archived copy of an object back into Amazon S3
  
  This operation performs the following types of requests:
  
  select - Perform a select query on an archived object
  
  restore an archive - Restore an archived object
  
  To use this operation, you must have permissions to perform the s3:RestoreObject and s3:GetObject actions. The bucket owner has this permission by default and can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources in the Amazon Simple Storage Service Developer Guide.
  
  Querying Archives with Select Requests
  
  You use a select type of request to perform SQL queries on archived objects. The archived objects that are being queried by the select request must be formatted as uncompressed comma-separated values (CSV) files. You can run queries and custom analytics on your archived data without having to restore your data to a hotter Amazon S3 tier. For an overview about select requests, see Querying Archived Objects in the Amazon Simple Storage Service Developer Guide.
  
  When making a select request, do the following:
  
  Define an output location for the select query's output. This must be an Amazon S3 bucket in the same AWS Region as the bucket that contains the archive object that is being queried. The AWS account that initiates the job must have permissions to write to the S3 bucket. You can specify the storage class and encryption for the output objects stored in the bucket. For more information about output, see Querying Archived Objects in the Amazon Simple Storage Service Developer Guide.
  
  For more information about the S3 structure in the request body, see the following:
  
  PutObject
  
  Managing Access with ACLs in the Amazon Simple Storage Service Developer Guide
  
  Protecting Data Using Server-Side Encryption in the Amazon Simple Storage Service Developer Guide
  
  Define the SQL expression for the SELECT type of restoration for your query in the request body's SelectParameters structure. You can use expressions like the following examples.
  
  The following expression returns all records from the specified object.
  
  SELECT * FROM Object
  
  Assuming that you are not using any headers for data stored in the object, you can specify columns with positional headers.
  
  SELECT s._1, s._2 FROM Object s WHERE s._3 > 100
  
  If you have headers and you set the fileHeaderInfo in the CSV structure in the request body to USE, you can specify headers in the query. (If you set the fileHeaderInfo field to IGNORE, the first row is skipped for the query.) You cannot mix ordinal positions with header column names.
  
  SELECT s.Id, s.FirstName, s.SSN FROM S3Object s
  
  For more information about using SQL with Glacier Select restore, see SQL Reference for Amazon S3 Select and Glacier Select in the Amazon Simple Storage Service Developer Guide.
  
  When making a select request, you can also do the following:
  
  To expedite your queries, specify the Expedited tier. For more information about tiers, see "Restoring Archives," later in this topic.
  
  Specify details about the data serialization format of both the input object that is being queried and the serialization of the CSV-encoded query results.
  
  The following are additional important facts about the select feature:
  
  The output results are new Amazon S3 objects. Unlike archive retrievals, they are stored until explicitly deleted-manually or through a lifecycle policy.
  
  You can issue more than one select request on the same Amazon S3 object. Amazon S3 doesn't deduplicate requests, so avoid issuing duplicate requests.
  
  Amazon S3 accepts a select request even if the object has already been restored. A select request doesn’t return error response 409.
  
  Restoring Archives
  
  Objects in the GLACIER and DEEP_ARCHIVE storage classes are archived. To access an archived object, you must first initiate a restore request. This restores a temporary copy of the archived object. In a restore request, you specify the number of days that you want the restored copy to exist. After the specified period, Amazon S3 deletes the temporary copy but the object remains archived in the GLACIER or DEEP_ARCHIVE storage class that object was restored from.
  
  To restore a specific object version, you can provide a version ID. If you don't provide a version ID, Amazon S3 restores the current version.
  
  The time it takes restore jobs to finish depends on which storage class the object is being restored from and which data access tier you specify.
  
  When restoring an archived object (or using a select request), you can specify one of the following data access tier options in the Tier element of the request body:
  
  Expedited - Expedited retrievals allow you to quickly access your data stored in the GLACIER storage class when occasional urgent requests for a subset of archives are required. For all but the largest archived objects (250 MB+), data accessed using Expedited retrievals are typically made available within 1–5 minutes. Provisioned capacity ensures that retrieval capacity for Expedited retrievals is available when you need it. Expedited retrievals and provisioned capacity are not available for the DEEP_ARCHIVE storage class.
  
  Standard - Standard retrievals allow you to access any of your archived objects within several hours. This is the default option for the GLACIER and DEEP_ARCHIVE retrieval requests that do not specify the retrieval option. Standard retrievals typically complete within 3-5 hours from the GLACIER storage class and typically complete within 12 hours from the DEEP_ARCHIVE storage class.
  
  Bulk - Bulk retrievals are Amazon S3 Glacier’s lowest-cost retrieval option, enabling you to retrieve large amounts, even petabytes, of data inexpensively in a day. Bulk retrievals typically complete within 5-12 hours from the GLACIER storage class and typically complete within 48 hours from the DEEP_ARCHIVE storage class.
  
  For more information about archive retrieval options and provisioned capacity for Expedited data access, see Restoring Archived Objects in the Amazon Simple Storage Service Developer Guide.
  
  You can use Amazon S3 restore speed upgrade to change the restore speed to a faster speed while it is in progress. You upgrade the speed of an in-progress restoration by issuing another restore request to the same object, setting a new Tier request element. When issuing a request to upgrade the restore tier, you must choose a tier that is faster than the tier that the in-progress restore is using. You must not change any other parameters, such as the Days request element. For more information, see Upgrading the Speed of an In-Progress Restore in the Amazon Simple Storage Service Developer Guide.
  
  To get the status of object restoration, you can send a HEAD request. Operations return the x-amz-restore header, which provides information about the restoration status, in the response. You can use Amazon S3 event notifications to notify you when a restore is initiated or completed. For more information, see Configuring Amazon S3 Event Notifications in the Amazon Simple Storage Service Developer Guide.
  
  After restoring an archived object, you can update the restoration period by reissuing the request with a new period. Amazon S3 updates the restoration period relative to the current time and charges only for the request-there are no data transfer charges. You cannot update the restoration period when Amazon S3 is actively processing your current restore request for the object.
  
  If your bucket has a lifecycle configuration with a rule that includes an expiration action, the object expiration overrides the life span that you specify in a restore request. For example, if you restore an object copy for 10 days, but the object is scheduled to expire in 3 days, Amazon S3 deletes the object in 3 days. For more information about lifecycle configuration, see PutBucketLifecycleConfiguration and Object Lifecycle Management in Amazon Simple Storage Service Developer Guide.
  
  Responses
  
  A successful operation returns either the 200 OK or 202 Accepted status code.
  
  If the object copy is not previously restored, then Amazon S3 returns 202 Accepted in the response.
  
  If the object copy is previously restored, Amazon S3 returns 200 OK in the response.
  
  Special Errors
  
  Code: RestoreAlreadyInProgress
  
  Cause: Object restore is already in progress. (This error does not apply to SELECT type requests.)
  
  HTTP Status Code: 409 Conflict
  
  SOAP Fault Code Prefix: Client
  
  Code: GlacierExpeditedRetrievalNotAvailable
  
  Cause: Glacier expedited retrievals are currently not available. Try again later. (Returned if there is insufficient capacity to process the Expedited request. This error applies only to Expedited retrievals and not to Standard or Bulk retrievals.)
  
  HTTP Status Code: 503
  
  SOAP Fault Code Prefix: N/A
  
  Related Resources
  
  PutBucketLifecycleConfiguration
  
  GetBucketNotificationConfiguration
  
  SQL Reference for Amazon S3 Select and Glacier Select in the Amazon Simple Storage Service Developer Guide
  
  This is a convenience which creates an instance of the RestoreObjectRequest.Builder avoiding the need to create one manually via RestoreObjectRequest.builder()
  
  Parameters:
  
  restoreObjectRequest - A Consumer that will call methods on RestoreObjectRequest.Builder to create a request.
  
  Returns:
  
  A Java Future containing the result of the RestoreObject operation returned by the service.
  The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
  
  ObjectAlreadyInActiveTierErrorException This operation is not allowed against this storage tier.
  
  SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
  
  SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
  
  S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  
  uploadPart
  
  default CompletableFuture<UploadPartResponse> uploadPart(UploadPartRequest uploadPartRequest, AsyncRequestBody requestBody)
  
  Uploads a part in a multipart upload.
  
  In this operation, you provide part data in your request. However, you have an option to specify your existing Amazon S3 object as a data source for the part you are uploading. To upload a part from an existing object, you use the UploadPartCopy operation.
  
  You must initiate a multipart upload (see CreateMultipartUpload) before you can upload any part. In response to your initiate request, Amazon S3 returns an upload ID, a unique identifier, that you must include in your upload part request.
  
  Part numbers can be any number from 1 to 10,000, inclusive. A part number uniquely identifies a part and also defines its position within the object being created. If you upload a new part using the same part number that was used with a previous part, the previously uploaded part is overwritten. Each part must be at least 5 MB in size, except the last part. There is no size limit on the last part of your multipart upload.
  
  To ensure that data is not corrupted when traversing the network, specify the Content-MD5 header in the upload part request. Amazon S3 checks the part data against the provided MD5 value. If they do not match, Amazon S3 returns an error.
  
  Note: After you initiate multipart upload and upload one or more parts, you must either complete or abort multipart upload in order to stop getting charged for storage of the uploaded parts. Only after you either complete or abort multipart upload, Amazon S3 frees up the parts storage and stops charging you for the parts storage.
  
  For more information on multipart uploads, go to Multipart Upload Overview in the Amazon Simple Storage Service Developer Guide .
  
  For information on the permissions required to use the multipart upload API, go to Multipart Upload API and Permissions in the Amazon Simple Storage Service Developer Guide.
  
  You can optionally request server-side encryption where Amazon S3 encrypts your data as it writes it to disks in its data centers and decrypts it for you when you access it. You have the option of providing your own encryption key, or you can use the AWS managed encryption keys. If you choose to provide your own encryption key, the request headers you provide in the request must match the headers you used in the request to initiate the upload by using CreateMultipartUpload. For more information, go to Using Server-Side Encryption in the Amazon Simple Storage Service Developer Guide.
  
  Server-side encryption is supported by the S3 Multipart Upload actions. Unless you are using a customer-provided encryption key, you don't need to specify the encryption parameters in each UploadPart request. Instead, you only need to specify the server-side encryption parameters in the initial Initiate Multipart request. For more information, see CreateMultipartUpload.
  
  If you requested server-side encryption using a customer-provided encryption key in your initiate multipart upload request, you must provide identical encryption information in each part upload using the following headers.
  
  x-amz-server-side-encryption-customer-algorithm
  
  x-amz-server-side-encryption-customer-key
  
  x-amz-server-side-encryption-customer-key-MD5
  
  Special Errors
  
  Code: NoSuchUpload
  
  Cause: The specified multipart upload does not exist. The upload ID might be invalid, or the multipart upload might have been aborted or completed.
  
  HTTP Status Code: 404 Not Found
  
  SOAP Fault Code Prefix: Client
  
  Related Resources
  
  CreateMultipartUpload
  
  CompleteMultipartUpload
  
  AbortMultipartUpload
  
  ListParts
  
  ListMultipartUploads
  
  Parameters:
  
  uploadPartRequest -
  
  requestBody - Functional interface that can be implemented to produce the request content in a non-blocking manner. The size of the content is expected to be known up front. See AsyncRequestBody for specific details on implementing this interface as well as links to precanned implementations for common scenarios like uploading from a file. The service documentation for the request content is as follows '
  Object data.
  '
  
  Returns:
  
  A Java Future containing the result of the UploadPart operation returned by the service.
  The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
  
  SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
  
  SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
  
  S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  
  uploadPart
  
  default CompletableFuture<UploadPartResponse> uploadPart(Consumer<UploadPartRequest.Builder> uploadPartRequest, AsyncRequestBody requestBody)
  
  Uploads a part in a multipart upload.
  
  In this operation, you provide part data in your request. However, you have an option to specify your existing Amazon S3 object as a data source for the part you are uploading. To upload a part from an existing object, you use the UploadPartCopy operation.
  
  You must initiate a multipart upload (see CreateMultipartUpload) before you can upload any part. In response to your initiate request, Amazon S3 returns an upload ID, a unique identifier, that you must include in your upload part request.
  
  Part numbers can be any number from 1 to 10,000, inclusive. A part number uniquely identifies a part and also defines its position within the object being created. If you upload a new part using the same part number that was used with a previous part, the previously uploaded part is overwritten. Each part must be at least 5 MB in size, except the last part. There is no size limit on the last part of your multipart upload.
  
  To ensure that data is not corrupted when traversing the network, specify the Content-MD5 header in the upload part request. Amazon S3 checks the part data against the provided MD5 value. If they do not match, Amazon S3 returns an error.
  
  Note: After you initiate multipart upload and upload one or more parts, you must either complete or abort multipart upload in order to stop getting charged for storage of the uploaded parts. Only after you either complete or abort multipart upload, Amazon S3 frees up the parts storage and stops charging you for the parts storage.
  
  For more information on multipart uploads, go to Multipart Upload Overview in the Amazon Simple Storage Service Developer Guide .
  
  For information on the permissions required to use the multipart upload API, go to Multipart Upload API and Permissions in the Amazon Simple Storage Service Developer Guide.
  
  You can optionally request server-side encryption where Amazon S3 encrypts your data as it writes it to disks in its data centers and decrypts it for you when you access it. You have the option of providing your own encryption key, or you can use the AWS managed encryption keys. If you choose to provide your own encryption key, the request headers you provide in the request must match the headers you used in the request to initiate the upload by using CreateMultipartUpload. For more information, go to Using Server-Side Encryption in the Amazon Simple Storage Service Developer Guide.
  
  Server-side encryption is supported by the S3 Multipart Upload actions. Unless you are using a customer-provided encryption key, you don't need to specify the encryption parameters in each UploadPart request. Instead, you only need to specify the server-side encryption parameters in the initial Initiate Multipart request. For more information, see CreateMultipartUpload.
  
  If you requested server-side encryption using a customer-provided encryption key in your initiate multipart upload request, you must provide identical encryption information in each part upload using the following headers.
  
  x-amz-server-side-encryption-customer-algorithm
  
  x-amz-server-side-encryption-customer-key
  
  x-amz-server-side-encryption-customer-key-MD5
  
  Special Errors
  
  Code: NoSuchUpload
  
  Cause: The specified multipart upload does not exist. The upload ID might be invalid, or the multipart upload might have been aborted or completed.
  
  HTTP Status Code: 404 Not Found
  
  SOAP Fault Code Prefix: Client
  
  Related Resources
  
  CreateMultipartUpload
  
  CompleteMultipartUpload
  
  AbortMultipartUpload
  
  ListParts
  
  ListMultipartUploads
  
  This is a convenience which creates an instance of the UploadPartRequest.Builder avoiding the need to create one manually via UploadPartRequest.builder()
  
  Parameters:
  
  uploadPartRequest - A Consumer that will call methods on UploadPartRequest.Builder to create a request.
  
  requestBody - Functional interface that can be implemented to produce the request content in a non-blocking manner. The size of the content is expected to be known up front. See AsyncRequestBody for specific details on implementing this interface as well as links to precanned implementations for common scenarios like uploading from a file. The service documentation for the request content is as follows '
  Object data.
  '
  
  Returns:
  
  A Java Future containing the result of the UploadPart operation returned by the service.
  The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
  
  SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
  
  SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
  
  S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  
  uploadPart
  
  default CompletableFuture<UploadPartResponse> uploadPart(UploadPartRequest uploadPartRequest, Path sourcePath)
  
  Uploads a part in a multipart upload.
  
  In this operation, you provide part data in your request. However, you have an option to specify your existing Amazon S3 object as a data source for the part you are uploading. To upload a part from an existing object, you use the UploadPartCopy operation.
  
  You must initiate a multipart upload (see CreateMultipartUpload) before you can upload any part. In response to your initiate request, Amazon S3 returns an upload ID, a unique identifier, that you must include in your upload part request.
  
  Part numbers can be any number from 1 to 10,000, inclusive. A part number uniquely identifies a part and also defines its position within the object being created. If you upload a new part using the same part number that was used with a previous part, the previously uploaded part is overwritten. Each part must be at least 5 MB in size, except the last part. There is no size limit on the last part of your multipart upload.
  
  To ensure that data is not corrupted when traversing the network, specify the Content-MD5 header in the upload part request. Amazon S3 checks the part data against the provided MD5 value. If they do not match, Amazon S3 returns an error.
  
  Note: After you initiate multipart upload and upload one or more parts, you must either complete or abort multipart upload in order to stop getting charged for storage of the uploaded parts. Only after you either complete or abort multipart upload, Amazon S3 frees up the parts storage and stops charging you for the parts storage.
  
  For more information on multipart uploads, go to Multipart Upload Overview in the Amazon Simple Storage Service Developer Guide .
  
  For information on the permissions required to use the multipart upload API, go to Multipart Upload API and Permissions in the Amazon Simple Storage Service Developer Guide.
  
  You can optionally request server-side encryption where Amazon S3 encrypts your data as it writes it to disks in its data centers and decrypts it for you when you access it. You have the option of providing your own encryption key, or you can use the AWS managed encryption keys. If you choose to provide your own encryption key, the request headers you provide in the request must match the headers you used in the request to initiate the upload by using CreateMultipartUpload. For more information, go to Using Server-Side Encryption in the Amazon Simple Storage Service Developer Guide.
  
  Server-side encryption is supported by the S3 Multipart Upload actions. Unless you are using a customer-provided encryption key, you don't need to specify the encryption parameters in each UploadPart request. Instead, you only need to specify the server-side encryption parameters in the initial Initiate Multipart request. For more information, see CreateMultipartUpload.
  
  If you requested server-side encryption using a customer-provided encryption key in your initiate multipart upload request, you must provide identical encryption information in each part upload using the following headers.
  
  x-amz-server-side-encryption-customer-algorithm
  
  x-amz-server-side-encryption-customer-key
  
  x-amz-server-side-encryption-customer-key-MD5
  
  Special Errors
  
  Code: NoSuchUpload
  
  Cause: The specified multipart upload does not exist. The upload ID might be invalid, or the multipart upload might have been aborted or completed.
  
  HTTP Status Code: 404 Not Found
  
  SOAP Fault Code Prefix: Client
  
  Related Resources
  
  CreateMultipartUpload
  
  CompleteMultipartUpload
  
  AbortMultipartUpload
  
  ListParts
  
  ListMultipartUploads
  
  Parameters:
  
  uploadPartRequest -
  
  sourcePath - Path to file containing data to send to the service. File will be read entirely and may be read multiple times in the event of a retry. If the file does not exist or the current user does not have access to read it then an exception will be thrown. The service documentation for the request content is as follows '
  Object data.
  '
  
  Returns:
  
  A Java Future containing the result of the UploadPart operation returned by the service.
  The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
  
  SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
  
  SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
  
  S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  
  uploadPart
  
  default CompletableFuture<UploadPartResponse> uploadPart(Consumer<UploadPartRequest.Builder> uploadPartRequest, Path sourcePath)
  
  Uploads a part in a multipart upload.
  
  In this operation, you provide part data in your request. However, you have an option to specify your existing Amazon S3 object as a data source for the part you are uploading. To upload a part from an existing object, you use the UploadPartCopy operation.
  
  You must initiate a multipart upload (see CreateMultipartUpload) before you can upload any part. In response to your initiate request, Amazon S3 returns an upload ID, a unique identifier, that you must include in your upload part request.
  
  Part numbers can be any number from 1 to 10,000, inclusive. A part number uniquely identifies a part and also defines its position within the object being created. If you upload a new part using the same part number that was used with a previous part, the previously uploaded part is overwritten. Each part must be at least 5 MB in size, except the last part. There is no size limit on the last part of your multipart upload.
  
  To ensure that data is not corrupted when traversing the network, specify the Content-MD5 header in the upload part request. Amazon S3 checks the part data against the provided MD5 value. If they do not match, Amazon S3 returns an error.
  
  Note: After you initiate multipart upload and upload one or more parts, you must either complete or abort multipart upload in order to stop getting charged for storage of the uploaded parts. Only after you either complete or abort multipart upload, Amazon S3 frees up the parts storage and stops charging you for the parts storage.
  
  For more information on multipart uploads, go to Multipart Upload Overview in the Amazon Simple Storage Service Developer Guide .
  
  For information on the permissions required to use the multipart upload API, go to Multipart Upload API and Permissions in the Amazon Simple Storage Service Developer Guide.
  
  You can optionally request server-side encryption where Amazon S3 encrypts your data as it writes it to disks in its data centers and decrypts it for you when you access it. You have the option of providing your own encryption key, or you can use the AWS managed encryption keys. If you choose to provide your own encryption key, the request headers you provide in the request must match the headers you used in the request to initiate the upload by using CreateMultipartUpload. For more information, go to Using Server-Side Encryption in the Amazon Simple Storage Service Developer Guide.
  
  Server-side encryption is supported by the S3 Multipart Upload actions. Unless you are using a customer-provided encryption key, you don't need to specify the encryption parameters in each UploadPart request. Instead, you only need to specify the server-side encryption parameters in the initial Initiate Multipart request. For more information, see CreateMultipartUpload.
  
  If you requested server-side encryption using a customer-provided encryption key in your initiate multipart upload request, you must provide identical encryption information in each part upload using the following headers.
  
  x-amz-server-side-encryption-customer-algorithm
  
  x-amz-server-side-encryption-customer-key
  
  x-amz-server-side-encryption-customer-key-MD5
  
  Special Errors
  
  Code: NoSuchUpload
  
  Cause: The specified multipart upload does not exist. The upload ID might be invalid, or the multipart upload might have been aborted or completed.
  
  HTTP Status Code: 404 Not Found
  
  SOAP Fault Code Prefix: Client
  
  Related Resources
  
  CreateMultipartUpload
  
  CompleteMultipartUpload
  
  AbortMultipartUpload
  
  ListParts
  
  ListMultipartUploads
  
  This is a convenience which creates an instance of the UploadPartRequest.Builder avoiding the need to create one manually via UploadPartRequest.builder()
  
  Parameters:
  
  uploadPartRequest - A Consumer that will call methods on UploadPartRequest.Builder to create a request.
  
  sourcePath - Path to file containing data to send to the service. File will be read entirely and may be read multiple times in the event of a retry. If the file does not exist or the current user does not have access to read it then an exception will be thrown. The service documentation for the request content is as follows '
  Object data.
  '
  
  Returns:
  
  A Java Future containing the result of the UploadPart operation returned by the service.
  The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
  
  SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
  
  SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
  
  S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  
  uploadPartCopy
  
  default CompletableFuture<UploadPartCopyResponse> uploadPartCopy(UploadPartCopyRequest uploadPartCopyRequest)
  
  Uploads a part by copying data from an existing object as data source. You specify the data source by adding the request header x-amz-copy-source in your request and a byte range by adding the request header x-amz-copy-source-range in your request.
  
  The minimum allowable part size for a multipart upload is 5 MB. For more information about multipart upload limits, go to Quick Facts in the Amazon Simple Storage Service Developer Guide.
  
  Instead of using an existing object as part data, you might use the UploadPart operation and provide data in your request.
  
  You must initiate a multipart upload before you can upload any part. In response to your initiate request. Amazon S3 returns a unique identifier, the upload ID, that you must include in your upload part request.
  
  For more information about using the UploadPartCopy operation, see the following:
  
  For conceptual information about multipart uploads, see Uploading Objects Using Multipart Upload in the Amazon Simple Storage Service Developer Guide.
  
  For information about permissions required to use the multipart upload API, see Multipart Upload API and Permissions in the Amazon Simple Storage Service Developer Guide.
  
  For information about copying objects using a single atomic operation vs. the multipart upload, see Operations on Objects in the Amazon Simple Storage Service Developer Guide.
  
  For information about using server-side encryption with customer-provided encryption keys with the UploadPartCopy operation, see CopyObject and UploadPart.
  
  Note the following additional considerations about the request headers x-amz-copy-source-if-match, x-amz-copy-source-if-none-match, x-amz-copy-source-if-unmodified-since, and x-amz-copy-source-if-modified-since:
  
  Consideration 1 - If both of the x-amz-copy-source-if-match and x-amz-copy-source-if-unmodified-since headers are present in the request as follows:
  
  x-amz-copy-source-if-match condition evaluates to true, and;
  
  x-amz-copy-source-if-unmodified-since condition evaluates to false;
  
  Amazon S3 returns 200 OK and copies the data.
  
  Consideration 2 - If both of the x-amz-copy-source-if-none-match and x-amz-copy-source-if-modified-since headers are present in the request as follows:
  
  x-amz-copy-source-if-none-match condition evaluates to false, and;
  
  x-amz-copy-source-if-modified-since condition evaluates to true;
  
  Amazon S3 returns 412 Precondition Failed response code.
  
  Versioning
  
  If your bucket has versioning enabled, you could have multiple versions of the same object. By default, x-amz-copy-source identifies the current version of the object to copy. If the current version is a delete marker and you don't specify a versionId in the x-amz-copy-source, Amazon S3 returns a 404 error, because the object does not exist. If you specify versionId in the x-amz-copy-source and the versionId is a delete marker, Amazon S3 returns an HTTP 400 error, because you are not allowed to specify a delete marker as a version for the x-amz-copy-source.
  
  You can optionally specify a specific version of the source object to copy by adding the versionId subresource as shown in the following example:
  
  x-amz-copy-source: /bucket/object?versionId=version id
  
  Special Errors
  
  Code: NoSuchUpload
  
  Cause: The specified multipart upload does not exist. The upload ID might be invalid, or the multipart upload might have been aborted or completed.
  
  HTTP Status Code: 404 Not Found
  
  Code: InvalidRequest
  
  Cause: The specified copy source is not supported as a byte-range copy source.
  
  HTTP Status Code: 400 Bad Request
  
  Related Resources
  
  CreateMultipartUpload
  
  UploadPart
  
  CompleteMultipartUpload
  
  AbortMultipartUpload
  
  ListParts
  
  ListMultipartUploads
  
  Parameters:
  
  uploadPartCopyRequest -
  
  Returns:
  
  A Java Future containing the result of the UploadPartCopy operation returned by the service.
  The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
  
  SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
  
  SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
  
  S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  
  uploadPartCopy
  
  default CompletableFuture<UploadPartCopyResponse> uploadPartCopy(Consumer<UploadPartCopyRequest.Builder> uploadPartCopyRequest)
  
  Uploads a part by copying data from an existing object as data source. You specify the data source by adding the request header x-amz-copy-source in your request and a byte range by adding the request header x-amz-copy-source-range in your request.
  
  The minimum allowable part size for a multipart upload is 5 MB. For more information about multipart upload limits, go to Quick Facts in the Amazon Simple Storage Service Developer Guide.
  
  Instead of using an existing object as part data, you might use the UploadPart operation and provide data in your request.
  
  You must initiate a multipart upload before you can upload any part. In response to your initiate request. Amazon S3 returns a unique identifier, the upload ID, that you must include in your upload part request.
  
  For more information about using the UploadPartCopy operation, see the following:
  
  For conceptual information about multipart uploads, see Uploading Objects Using Multipart Upload in the Amazon Simple Storage Service Developer Guide.
  
  For information about permissions required to use the multipart upload API, see Multipart Upload API and Permissions in the Amazon Simple Storage Service Developer Guide.
  
  For information about copying objects using a single atomic operation vs. the multipart upload, see Operations on Objects in the Amazon Simple Storage Service Developer Guide.
  
  For information about using server-side encryption with customer-provided encryption keys with the UploadPartCopy operation, see CopyObject and UploadPart.
  
  Note the following additional considerations about the request headers x-amz-copy-source-if-match, x-amz-copy-source-if-none-match, x-amz-copy-source-if-unmodified-since, and x-amz-copy-source-if-modified-since:
  
  Consideration 1 - If both of the x-amz-copy-source-if-match and x-amz-copy-source-if-unmodified-since headers are present in the request as follows:
  
  x-amz-copy-source-if-match condition evaluates to true, and;
  
  x-amz-copy-source-if-unmodified-since condition evaluates to false;
  
  Amazon S3 returns 200 OK and copies the data.
  
  Consideration 2 - If both of the x-amz-copy-source-if-none-match and x-amz-copy-source-if-modified-since headers are present in the request as follows:
  
  x-amz-copy-source-if-none-match condition evaluates to false, and;
  
  x-amz-copy-source-if-modified-since condition evaluates to true;
  
  Amazon S3 returns 412 Precondition Failed response code.
  
  Versioning
  
  If your bucket has versioning enabled, you could have multiple versions of the same object. By default, x-amz-copy-source identifies the current version of the object to copy. If the current version is a delete marker and you don't specify a versionId in the x-amz-copy-source, Amazon S3 returns a 404 error, because the object does not exist. If you specify versionId in the x-amz-copy-source and the versionId is a delete marker, Amazon S3 returns an HTTP 400 error, because you are not allowed to specify a delete marker as a version for the x-amz-copy-source.
  
  You can optionally specify a specific version of the source object to copy by adding the versionId subresource as shown in the following example:
  
  x-amz-copy-source: /bucket/object?versionId=version id
  
  Special Errors
  
  Code: NoSuchUpload
  
  Cause: The specified multipart upload does not exist. The upload ID might be invalid, or the multipart upload might have been aborted or completed.
  
  HTTP Status Code: 404 Not Found
  
  Code: InvalidRequest
  
  Cause: The specified copy source is not supported as a byte-range copy source.
  
  HTTP Status Code: 400 Bad Request
  
  Related Resources
  
  CreateMultipartUpload
  
  UploadPart
  
  CompleteMultipartUpload
  
  AbortMultipartUpload
  
  ListParts
  
  ListMultipartUploads
  
  This is a convenience which creates an instance of the UploadPartCopyRequest.Builder avoiding the need to create one manually via UploadPartCopyRequest.builder()
  
  Parameters:
  
  uploadPartCopyRequest - A Consumer that will call methods on UploadPartCopyRequest.Builder to create a request.
  
  Returns:
  
  A Java Future containing the result of the UploadPartCopy operation returned by the service.
  The CompletableFuture returned by this method can be completed exceptionally with the following exceptions.
  
  SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
  
  SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
  
  S3Exception Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
  
  utilities
  
  default S3Utilities utilities()
  
  Creates an instance of S3Utilities object with the configuration set on this client.

Interface S3AsyncClient

Field Summary

Method Summary

Methods inherited from interface software.amazon.awssdk.core.SdkClient

Methods inherited from interface software.amazon.awssdk.utils.SdkAutoCloseable

Field Detail

SERVICE_NAME

Method Detail

create

builder

abortMultipartUpload

abortMultipartUpload

completeMultipartUpload

completeMultipartUpload

copyObject

copyObject

createBucket

createBucket

createMultipartUpload

createMultipartUpload

deleteBucket

deleteBucket

deleteBucketAnalyticsConfiguration

deleteBucketAnalyticsConfiguration

deleteBucketCors

deleteBucketCors

deleteBucketEncryption

deleteBucketEncryption

deleteBucketInventoryConfiguration

deleteBucketInventoryConfiguration

deleteBucketLifecycle

deleteBucketLifecycle

deleteBucketMetricsConfiguration

deleteBucketMetricsConfiguration

deleteBucketPolicy

deleteBucketPolicy

deleteBucketReplication

deleteBucketReplication

deleteBucketTagging

deleteBucketTagging

deleteBucketWebsite

deleteBucketWebsite

deleteObject

deleteObject

deleteObjectTagging

deleteObjectTagging

deleteObjects

deleteObjects

deletePublicAccessBlock

deletePublicAccessBlock

getBucketAccelerateConfiguration

getBucketAccelerateConfiguration

getBucketAcl

getBucketAcl

getBucketAnalyticsConfiguration

getBucketAnalyticsConfiguration

getBucketCors

getBucketCors

getBucketEncryption

getBucketEncryption

getBucketInventoryConfiguration

getBucketInventoryConfiguration

getBucketLifecycleConfiguration

getBucketLifecycleConfiguration

getBucketLocation

getBucketLocation

getBucketLogging

getBucketLogging

getBucketMetricsConfiguration

getBucketMetricsConfiguration

getBucketNotificationConfiguration

getBucketNotificationConfiguration

getBucketPolicy

getBucketPolicy

getBucketPolicyStatus

getBucketPolicyStatus

getBucketReplication

getBucketReplication

getBucketRequestPayment

getBucketRequestPayment