@Generated(value="com.amazonaws:aws-java-sdk-code-generator") public class AbstractAWSS3ControlAsync extends AbstractAWSS3Control implements AWSS3ControlAsync
AWSS3ControlAsync. Convenient method forms pass through to the corresponding
overload that takes a request object and an AsyncHandler, which throws an
UnsupportedOperationException.ENDPOINT_PREFIXassociateAccessGrantsIdentityCenter, createAccessGrant, createAccessGrantsInstance, createAccessGrantsLocation, createAccessPoint, createAccessPointForObjectLambda, createBucket, createJob, createMultiRegionAccessPoint, createStorageLensGroup, deleteAccessGrant, deleteAccessGrantsInstance, deleteAccessGrantsInstanceResourcePolicy, deleteAccessGrantsLocation, deleteAccessPoint, deleteAccessPointForObjectLambda, deleteAccessPointPolicy, deleteAccessPointPolicyForObjectLambda, deleteBucket, deleteBucketLifecycleConfiguration, deleteBucketPolicy, deleteBucketReplication, deleteBucketTagging, deleteJobTagging, deleteMultiRegionAccessPoint, deletePublicAccessBlock, deleteStorageLensConfiguration, deleteStorageLensConfigurationTagging, deleteStorageLensGroup, describeJob, describeMultiRegionAccessPointOperation, dissociateAccessGrantsIdentityCenter, getAccessGrant, getAccessGrantsInstance, getAccessGrantsInstanceForPrefix, getAccessGrantsInstanceResourcePolicy, getAccessGrantsLocation, getAccessPoint, getAccessPointConfigurationForObjectLambda, getAccessPointForObjectLambda, getAccessPointPolicy, getAccessPointPolicyForObjectLambda, getAccessPointPolicyStatus, getAccessPointPolicyStatusForObjectLambda, getBucket, getBucketLifecycleConfiguration, getBucketPolicy, getBucketReplication, getBucketTagging, getBucketVersioning, getCachedResponseMetadata, getDataAccess, getJobTagging, getMultiRegionAccessPoint, getMultiRegionAccessPointPolicy, getMultiRegionAccessPointPolicyStatus, getMultiRegionAccessPointRoutes, getPublicAccessBlock, getStorageLensConfiguration, getStorageLensConfigurationTagging, getStorageLensGroup, listAccessGrants, listAccessGrantsInstances, listAccessGrantsLocations, listAccessPoints, listAccessPointsForObjectLambda, listJobs, listMultiRegionAccessPoints, listRegionalBuckets, listStorageLensConfigurations, listStorageLensGroups, listTagsForResource, putAccessGrantsInstanceResourcePolicy, putAccessPointConfigurationForObjectLambda, putAccessPointPolicy, putAccessPointPolicyForObjectLambda, putBucketLifecycleConfiguration, putBucketPolicy, putBucketReplication, putBucketTagging, putBucketVersioning, putJobTagging, putMultiRegionAccessPointPolicy, putPublicAccessBlock, putStorageLensConfiguration, putStorageLensConfigurationTagging, shutdown, submitMultiRegionAccessPointRoutes, tagResource, untagResource, updateAccessGrantsLocation, updateJobPriority, updateJobStatus, updateStorageLensGroupequals, getClass, hashCode, notify, notifyAll, toString, wait, wait, waitassociateAccessGrantsIdentityCenter, createAccessGrant, createAccessGrantsInstance, createAccessGrantsLocation, createAccessPoint, createAccessPointForObjectLambda, createBucket, createJob, createMultiRegionAccessPoint, createStorageLensGroup, deleteAccessGrant, deleteAccessGrantsInstance, deleteAccessGrantsInstanceResourcePolicy, deleteAccessGrantsLocation, deleteAccessPoint, deleteAccessPointForObjectLambda, deleteAccessPointPolicy, deleteAccessPointPolicyForObjectLambda, deleteBucket, deleteBucketLifecycleConfiguration, deleteBucketPolicy, deleteBucketReplication, deleteBucketTagging, deleteJobTagging, deleteMultiRegionAccessPoint, deletePublicAccessBlock, deleteStorageLensConfiguration, deleteStorageLensConfigurationTagging, deleteStorageLensGroup, describeJob, describeMultiRegionAccessPointOperation, dissociateAccessGrantsIdentityCenter, getAccessGrant, getAccessGrantsInstance, getAccessGrantsInstanceForPrefix, getAccessGrantsInstanceResourcePolicy, getAccessGrantsLocation, getAccessPoint, getAccessPointConfigurationForObjectLambda, getAccessPointForObjectLambda, getAccessPointPolicy, getAccessPointPolicyForObjectLambda, getAccessPointPolicyStatus, getAccessPointPolicyStatusForObjectLambda, getBucket, getBucketLifecycleConfiguration, getBucketPolicy, getBucketReplication, getBucketTagging, getBucketVersioning, getCachedResponseMetadata, getDataAccess, getJobTagging, getMultiRegionAccessPoint, getMultiRegionAccessPointPolicy, getMultiRegionAccessPointPolicyStatus, getMultiRegionAccessPointRoutes, getPublicAccessBlock, getStorageLensConfiguration, getStorageLensConfigurationTagging, getStorageLensGroup, listAccessGrants, listAccessGrantsInstances, listAccessGrantsLocations, listAccessPoints, listAccessPointsForObjectLambda, listJobs, listMultiRegionAccessPoints, listRegionalBuckets, listStorageLensConfigurations, listStorageLensGroups, listTagsForResource, putAccessGrantsInstanceResourcePolicy, putAccessPointConfigurationForObjectLambda, putAccessPointPolicy, putAccessPointPolicyForObjectLambda, putBucketLifecycleConfiguration, putBucketPolicy, putBucketReplication, putBucketTagging, putBucketVersioning, putJobTagging, putMultiRegionAccessPointPolicy, putPublicAccessBlock, putStorageLensConfiguration, putStorageLensConfigurationTagging, shutdown, submitMultiRegionAccessPointRoutes, tagResource, untagResource, updateAccessGrantsLocation, updateJobPriority, updateJobStatus, updateStorageLensGrouppublic Future<AssociateAccessGrantsIdentityCenterResult> associateAccessGrantsIdentityCenterAsync(AssociateAccessGrantsIdentityCenterRequest request)
AWSS3ControlAsyncAssociate your S3 Access Grants instance with an Amazon Web Services IAM Identity Center instance. Use this action if you want to create access grants for users or groups from your corporate identity directory. First, you must add your corporate identity directory to Amazon Web Services IAM Identity Center. Then, you can associate this IAM Identity Center instance with your S3 Access Grants instance.
You must have the s3:AssociateAccessGrantsIdentityCenter permission to use this operation.
You must also have the following permissions: sso:CreateApplication,
sso:PutApplicationGrant, and sso:PutApplicationAuthenticationMethod.
associateAccessGrantsIdentityCenterAsync in interface AWSS3ControlAsyncpublic Future<AssociateAccessGrantsIdentityCenterResult> associateAccessGrantsIdentityCenterAsync(AssociateAccessGrantsIdentityCenterRequest request, AsyncHandler<AssociateAccessGrantsIdentityCenterRequest,AssociateAccessGrantsIdentityCenterResult> asyncHandler)
AWSS3ControlAsyncAssociate your S3 Access Grants instance with an Amazon Web Services IAM Identity Center instance. Use this action if you want to create access grants for users or groups from your corporate identity directory. First, you must add your corporate identity directory to Amazon Web Services IAM Identity Center. Then, you can associate this IAM Identity Center instance with your S3 Access Grants instance.
You must have the s3:AssociateAccessGrantsIdentityCenter permission to use this operation.
You must also have the following permissions: sso:CreateApplication,
sso:PutApplicationGrant, and sso:PutApplicationAuthenticationMethod.
associateAccessGrantsIdentityCenterAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<CreateAccessGrantResult> createAccessGrantAsync(CreateAccessGrantRequest request)
AWSS3ControlAsyncCreates an access grant that gives a grantee access to your S3 data. The grantee can be an IAM user or role or a directory user, or group. Before you can create a grant, you must have an S3 Access Grants instance in the same Region as the S3 data. You can create an S3 Access Grants instance using the CreateAccessGrantsInstance. You must also have registered at least one S3 data location in your S3 Access Grants instance using CreateAccessGrantsLocation.
You must have the s3:CreateAccessGrant permission to use this operation.
For any directory identity - sso:DescribeInstance and sso:DescribeApplication
For directory users - identitystore:DescribeUser
For directory groups - identitystore:DescribeGroup
createAccessGrantAsync in interface AWSS3ControlAsyncpublic Future<CreateAccessGrantResult> createAccessGrantAsync(CreateAccessGrantRequest request, AsyncHandler<CreateAccessGrantRequest,CreateAccessGrantResult> asyncHandler)
AWSS3ControlAsyncCreates an access grant that gives a grantee access to your S3 data. The grantee can be an IAM user or role or a directory user, or group. Before you can create a grant, you must have an S3 Access Grants instance in the same Region as the S3 data. You can create an S3 Access Grants instance using the CreateAccessGrantsInstance. You must also have registered at least one S3 data location in your S3 Access Grants instance using CreateAccessGrantsLocation.
You must have the s3:CreateAccessGrant permission to use this operation.
For any directory identity - sso:DescribeInstance and sso:DescribeApplication
For directory users - identitystore:DescribeUser
For directory groups - identitystore:DescribeGroup
createAccessGrantAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<CreateAccessGrantsInstanceResult> createAccessGrantsInstanceAsync(CreateAccessGrantsInstanceRequest request)
AWSS3ControlAsyncCreates an S3 Access Grants instance, which serves as a logical grouping for access grants. You can create one S3 Access Grants instance per Region per account.
You must have the s3:CreateAccessGrantsInstance permission to use this operation.
To associate an IAM Identity Center instance with your S3 Access Grants instance, you must also have the
sso:DescribeInstance, sso:CreateApplication, sso:PutApplicationGrant, and
sso:PutApplicationAuthenticationMethod permissions.
createAccessGrantsInstanceAsync in interface AWSS3ControlAsyncpublic Future<CreateAccessGrantsInstanceResult> createAccessGrantsInstanceAsync(CreateAccessGrantsInstanceRequest request, AsyncHandler<CreateAccessGrantsInstanceRequest,CreateAccessGrantsInstanceResult> asyncHandler)
AWSS3ControlAsyncCreates an S3 Access Grants instance, which serves as a logical grouping for access grants. You can create one S3 Access Grants instance per Region per account.
You must have the s3:CreateAccessGrantsInstance permission to use this operation.
To associate an IAM Identity Center instance with your S3 Access Grants instance, you must also have the
sso:DescribeInstance, sso:CreateApplication, sso:PutApplicationGrant, and
sso:PutApplicationAuthenticationMethod permissions.
createAccessGrantsInstanceAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<CreateAccessGrantsLocationResult> createAccessGrantsLocationAsync(CreateAccessGrantsLocationRequest request)
AWSS3ControlAsyncThe S3 data location that you would like to register in your S3 Access Grants instance. Your S3 data must be in the same Region as your S3 Access Grants instance. The location can be one of the following:
The default S3 location s3://
A bucket - S3://<bucket-name>
A bucket and prefix - S3://<bucket-name>/<prefix>
When you register a location, you must include the IAM role that has permission to manage the S3 location that you are registering. Give S3 Access Grants permission to assume this role using a policy. S3 Access Grants assumes this role to manage access to the location and to vend temporary credentials to grantees or client applications.
You must have the s3:CreateAccessGrantsLocation permission to use this operation.
You must also have the following permission for the specified IAM role: iam:PassRole
createAccessGrantsLocationAsync in interface AWSS3ControlAsyncpublic Future<CreateAccessGrantsLocationResult> createAccessGrantsLocationAsync(CreateAccessGrantsLocationRequest request, AsyncHandler<CreateAccessGrantsLocationRequest,CreateAccessGrantsLocationResult> asyncHandler)
AWSS3ControlAsyncThe S3 data location that you would like to register in your S3 Access Grants instance. Your S3 data must be in the same Region as your S3 Access Grants instance. The location can be one of the following:
The default S3 location s3://
A bucket - S3://<bucket-name>
A bucket and prefix - S3://<bucket-name>/<prefix>
When you register a location, you must include the IAM role that has permission to manage the S3 location that you are registering. Give S3 Access Grants permission to assume this role using a policy. S3 Access Grants assumes this role to manage access to the location and to vend temporary credentials to grantees or client applications.
You must have the s3:CreateAccessGrantsLocation permission to use this operation.
You must also have the following permission for the specified IAM role: iam:PassRole
createAccessGrantsLocationAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<CreateAccessPointResult> createAccessPointAsync(CreateAccessPointRequest request)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Creates an access point and associates it with the specified bucket. For more information, see Managing Data Access with Amazon S3 Access Points in the Amazon S3 User Guide.
S3 on Outposts only supports VPC-style access points.
For more information, see Accessing Amazon S3 on Outposts using virtual private cloud (VPC) only access points in the Amazon S3 User Guide.
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
The following actions are related to CreateAccessPoint:
createAccessPointAsync in interface AWSS3ControlAsyncpublic Future<CreateAccessPointResult> createAccessPointAsync(CreateAccessPointRequest request, AsyncHandler<CreateAccessPointRequest,CreateAccessPointResult> asyncHandler)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Creates an access point and associates it with the specified bucket. For more information, see Managing Data Access with Amazon S3 Access Points in the Amazon S3 User Guide.
S3 on Outposts only supports VPC-style access points.
For more information, see Accessing Amazon S3 on Outposts using virtual private cloud (VPC) only access points in the Amazon S3 User Guide.
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
The following actions are related to CreateAccessPoint:
createAccessPointAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<CreateAccessPointForObjectLambdaResult> createAccessPointForObjectLambdaAsync(CreateAccessPointForObjectLambdaRequest request)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Creates an Object Lambda Access Point. For more information, see Transforming objects with Object Lambda Access Points in the Amazon S3 User Guide.
The following actions are related to CreateAccessPointForObjectLambda:
createAccessPointForObjectLambdaAsync in interface AWSS3ControlAsyncpublic Future<CreateAccessPointForObjectLambdaResult> createAccessPointForObjectLambdaAsync(CreateAccessPointForObjectLambdaRequest request, AsyncHandler<CreateAccessPointForObjectLambdaRequest,CreateAccessPointForObjectLambdaResult> asyncHandler)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Creates an Object Lambda Access Point. For more information, see Transforming objects with Object Lambda Access Points in the Amazon S3 User Guide.
The following actions are related to CreateAccessPointForObjectLambda:
createAccessPointForObjectLambdaAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<CreateBucketResult> createBucketAsync(CreateBucketRequest request)
AWSS3ControlAsyncThis action creates an Amazon S3 on Outposts bucket. To create an S3 bucket, see Create Bucket in the Amazon S3 API Reference.
Creates a new Outposts bucket. By creating the bucket, you become the bucket owner. To create an Outposts bucket, you must have S3 on Outposts. For more information, see Using Amazon S3 on Outposts in Amazon S3 User Guide.
Not every string is an acceptable bucket name. For information on bucket naming restrictions, see Working with Amazon S3 Buckets.
S3 on Outposts buckets support:
Tags
LifecycleConfigurations for deleting expired objects
For a complete list of restrictions and Amazon S3 feature limitations on S3 on Outposts, see Amazon S3 on Outposts Restrictions and Limitations.
For an example of the request syntax for Amazon S3 on Outposts that uses the S3 on Outposts endpoint hostname
prefix and x-amz-outpost-id in your API request, see the Examples section.
The following actions are related to CreateBucket for Amazon S3 on Outposts:
createBucketAsync in interface AWSS3ControlAsyncpublic Future<CreateBucketResult> createBucketAsync(CreateBucketRequest request, AsyncHandler<CreateBucketRequest,CreateBucketResult> asyncHandler)
AWSS3ControlAsyncThis action creates an Amazon S3 on Outposts bucket. To create an S3 bucket, see Create Bucket in the Amazon S3 API Reference.
Creates a new Outposts bucket. By creating the bucket, you become the bucket owner. To create an Outposts bucket, you must have S3 on Outposts. For more information, see Using Amazon S3 on Outposts in Amazon S3 User Guide.
Not every string is an acceptable bucket name. For information on bucket naming restrictions, see Working with Amazon S3 Buckets.
S3 on Outposts buckets support:
Tags
LifecycleConfigurations for deleting expired objects
For a complete list of restrictions and Amazon S3 feature limitations on S3 on Outposts, see Amazon S3 on Outposts Restrictions and Limitations.
For an example of the request syntax for Amazon S3 on Outposts that uses the S3 on Outposts endpoint hostname
prefix and x-amz-outpost-id in your API request, see the Examples section.
The following actions are related to CreateBucket for Amazon S3 on Outposts:
createBucketAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<CreateJobResult> createJobAsync(CreateJobRequest request)
AWSS3ControlAsyncThis operation creates an S3 Batch Operations job.
You can use S3 Batch Operations to perform large-scale batch actions on Amazon S3 objects. Batch Operations can run a single action on lists of Amazon S3 objects that you specify. For more information, see S3 Batch Operations in the Amazon S3 User Guide.
For information about permissions required to use the Batch Operations, see Granting permissions for S3 Batch Operations in the Amazon S3 User Guide.
Related actions include:
createJobAsync in interface AWSS3ControlAsyncpublic Future<CreateJobResult> createJobAsync(CreateJobRequest request, AsyncHandler<CreateJobRequest,CreateJobResult> asyncHandler)
AWSS3ControlAsyncThis operation creates an S3 Batch Operations job.
You can use S3 Batch Operations to perform large-scale batch actions on Amazon S3 objects. Batch Operations can run a single action on lists of Amazon S3 objects that you specify. For more information, see S3 Batch Operations in the Amazon S3 User Guide.
For information about permissions required to use the Batch Operations, see Granting permissions for S3 Batch Operations in the Amazon S3 User Guide.
Related actions include:
createJobAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<CreateMultiRegionAccessPointResult> createMultiRegionAccessPointAsync(CreateMultiRegionAccessPointRequest request)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Creates a Multi-Region Access Point and associates it with the specified buckets. For more information about creating Multi-Region Access Points, see Creating Multi-Region Access Points in the Amazon S3 User Guide.
This action will always be routed to the US West (Oregon) Region. For more information about the restrictions around working with Multi-Region Access Points, see Multi-Region Access Point restrictions and limitations in the Amazon S3 User Guide.
This request is asynchronous, meaning that you might receive a response before the command has completed. When
this request provides a response, it provides a token that you can use to monitor the status of the request with
DescribeMultiRegionAccessPointOperation.
The following actions are related to CreateMultiRegionAccessPoint:
createMultiRegionAccessPointAsync in interface AWSS3ControlAsyncpublic Future<CreateMultiRegionAccessPointResult> createMultiRegionAccessPointAsync(CreateMultiRegionAccessPointRequest request, AsyncHandler<CreateMultiRegionAccessPointRequest,CreateMultiRegionAccessPointResult> asyncHandler)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Creates a Multi-Region Access Point and associates it with the specified buckets. For more information about creating Multi-Region Access Points, see Creating Multi-Region Access Points in the Amazon S3 User Guide.
This action will always be routed to the US West (Oregon) Region. For more information about the restrictions around working with Multi-Region Access Points, see Multi-Region Access Point restrictions and limitations in the Amazon S3 User Guide.
This request is asynchronous, meaning that you might receive a response before the command has completed. When
this request provides a response, it provides a token that you can use to monitor the status of the request with
DescribeMultiRegionAccessPointOperation.
The following actions are related to CreateMultiRegionAccessPoint:
createMultiRegionAccessPointAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<CreateStorageLensGroupResult> createStorageLensGroupAsync(CreateStorageLensGroupRequest request)
AWSS3ControlAsyncCreates a new S3 Storage Lens group and associates it with the specified Amazon Web Services account ID. An S3 Storage Lens group is a custom grouping of objects based on prefix, suffix, object tags, object size, object age, or a combination of these filters. For each Storage Lens group that you’ve created, you can also optionally add Amazon Web Services resource tags. For more information about S3 Storage Lens groups, see Working with S3 Storage Lens groups.
To use this operation, you must have the permission to perform the s3:CreateStorageLensGroup action.
If you’re trying to create a Storage Lens group with Amazon Web Services resource tags, you must also have
permission to perform the s3:TagResource action. For more information about the required Storage
Lens Groups permissions, see Setting account permissions to use S3 Storage Lens groups.
For information about Storage Lens groups errors, see List of Amazon S3 Storage Lens error codes.
createStorageLensGroupAsync in interface AWSS3ControlAsyncpublic Future<CreateStorageLensGroupResult> createStorageLensGroupAsync(CreateStorageLensGroupRequest request, AsyncHandler<CreateStorageLensGroupRequest,CreateStorageLensGroupResult> asyncHandler)
AWSS3ControlAsyncCreates a new S3 Storage Lens group and associates it with the specified Amazon Web Services account ID. An S3 Storage Lens group is a custom grouping of objects based on prefix, suffix, object tags, object size, object age, or a combination of these filters. For each Storage Lens group that you’ve created, you can also optionally add Amazon Web Services resource tags. For more information about S3 Storage Lens groups, see Working with S3 Storage Lens groups.
To use this operation, you must have the permission to perform the s3:CreateStorageLensGroup action.
If you’re trying to create a Storage Lens group with Amazon Web Services resource tags, you must also have
permission to perform the s3:TagResource action. For more information about the required Storage
Lens Groups permissions, see Setting account permissions to use S3 Storage Lens groups.
For information about Storage Lens groups errors, see List of Amazon S3 Storage Lens error codes.
createStorageLensGroupAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<DeleteAccessGrantResult> deleteAccessGrantAsync(DeleteAccessGrantRequest request)
AWSS3ControlAsyncDeletes the access grant from the S3 Access Grants instance. You cannot undo an access grant deletion and the grantee will no longer have access to the S3 data.
You must have the s3:DeleteAccessGrant permission to use this operation.
deleteAccessGrantAsync in interface AWSS3ControlAsyncpublic Future<DeleteAccessGrantResult> deleteAccessGrantAsync(DeleteAccessGrantRequest request, AsyncHandler<DeleteAccessGrantRequest,DeleteAccessGrantResult> asyncHandler)
AWSS3ControlAsyncDeletes the access grant from the S3 Access Grants instance. You cannot undo an access grant deletion and the grantee will no longer have access to the S3 data.
You must have the s3:DeleteAccessGrant permission to use this operation.
deleteAccessGrantAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<DeleteAccessGrantsInstanceResult> deleteAccessGrantsInstanceAsync(DeleteAccessGrantsInstanceRequest request)
AWSS3ControlAsyncDeletes your S3 Access Grants instance. You must first delete the access grants and locations before S3 Access Grants can delete the instance. See DeleteAccessGrant and DeleteAccessGrantsLocation. If you have associated an IAM Identity Center instance with your S3 Access Grants instance, you must first dissassociate the Identity Center instance from the S3 Access Grants instance before you can delete the S3 Access Grants instance. See AssociateAccessGrantsIdentityCenter and DissociateAccessGrantsIdentityCenter.
You must have the s3:DeleteAccessGrantsInstance permission to use this operation.
deleteAccessGrantsInstanceAsync in interface AWSS3ControlAsyncpublic Future<DeleteAccessGrantsInstanceResult> deleteAccessGrantsInstanceAsync(DeleteAccessGrantsInstanceRequest request, AsyncHandler<DeleteAccessGrantsInstanceRequest,DeleteAccessGrantsInstanceResult> asyncHandler)
AWSS3ControlAsyncDeletes your S3 Access Grants instance. You must first delete the access grants and locations before S3 Access Grants can delete the instance. See DeleteAccessGrant and DeleteAccessGrantsLocation. If you have associated an IAM Identity Center instance with your S3 Access Grants instance, you must first dissassociate the Identity Center instance from the S3 Access Grants instance before you can delete the S3 Access Grants instance. See AssociateAccessGrantsIdentityCenter and DissociateAccessGrantsIdentityCenter.
You must have the s3:DeleteAccessGrantsInstance permission to use this operation.
deleteAccessGrantsInstanceAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<DeleteAccessGrantsInstanceResourcePolicyResult> deleteAccessGrantsInstanceResourcePolicyAsync(DeleteAccessGrantsInstanceResourcePolicyRequest request)
AWSS3ControlAsyncDeletes the resource policy of the S3 Access Grants instance. The resource policy is used to manage cross-account access to your S3 Access Grants instance. By deleting the resource policy, you delete any cross-account permissions to your S3 Access Grants instance.
You must have the s3:DeleteAccessGrantsInstanceResourcePolicy permission to use this operation.
deleteAccessGrantsInstanceResourcePolicyAsync in interface AWSS3ControlAsyncpublic Future<DeleteAccessGrantsInstanceResourcePolicyResult> deleteAccessGrantsInstanceResourcePolicyAsync(DeleteAccessGrantsInstanceResourcePolicyRequest request, AsyncHandler<DeleteAccessGrantsInstanceResourcePolicyRequest,DeleteAccessGrantsInstanceResourcePolicyResult> asyncHandler)
AWSS3ControlAsyncDeletes the resource policy of the S3 Access Grants instance. The resource policy is used to manage cross-account access to your S3 Access Grants instance. By deleting the resource policy, you delete any cross-account permissions to your S3 Access Grants instance.
You must have the s3:DeleteAccessGrantsInstanceResourcePolicy permission to use this operation.
deleteAccessGrantsInstanceResourcePolicyAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<DeleteAccessGrantsLocationResult> deleteAccessGrantsLocationAsync(DeleteAccessGrantsLocationRequest request)
AWSS3ControlAsyncDeregisters a location from your S3 Access Grants instance. You can only delete a location registration from an S3 Access Grants instance if there are no grants associated with this location. See Delete a grant for information on how to delete grants. You need to have at least one registered location in your S3 Access Grants instance in order to create access grants.
You must have the s3:DeleteAccessGrantsLocation permission to use this operation.
deleteAccessGrantsLocationAsync in interface AWSS3ControlAsyncpublic Future<DeleteAccessGrantsLocationResult> deleteAccessGrantsLocationAsync(DeleteAccessGrantsLocationRequest request, AsyncHandler<DeleteAccessGrantsLocationRequest,DeleteAccessGrantsLocationResult> asyncHandler)
AWSS3ControlAsyncDeregisters a location from your S3 Access Grants instance. You can only delete a location registration from an S3 Access Grants instance if there are no grants associated with this location. See Delete a grant for information on how to delete grants. You need to have at least one registered location in your S3 Access Grants instance in order to create access grants.
You must have the s3:DeleteAccessGrantsLocation permission to use this operation.
deleteAccessGrantsLocationAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<DeleteAccessPointResult> deleteAccessPointAsync(DeleteAccessPointRequest request)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Deletes the specified access point.
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
The following actions are related to DeleteAccessPoint:
deleteAccessPointAsync in interface AWSS3ControlAsyncpublic Future<DeleteAccessPointResult> deleteAccessPointAsync(DeleteAccessPointRequest request, AsyncHandler<DeleteAccessPointRequest,DeleteAccessPointResult> asyncHandler)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Deletes the specified access point.
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
The following actions are related to DeleteAccessPoint:
deleteAccessPointAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<DeleteAccessPointForObjectLambdaResult> deleteAccessPointForObjectLambdaAsync(DeleteAccessPointForObjectLambdaRequest request)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Deletes the specified Object Lambda Access Point.
The following actions are related to DeleteAccessPointForObjectLambda:
deleteAccessPointForObjectLambdaAsync in interface AWSS3ControlAsyncpublic Future<DeleteAccessPointForObjectLambdaResult> deleteAccessPointForObjectLambdaAsync(DeleteAccessPointForObjectLambdaRequest request, AsyncHandler<DeleteAccessPointForObjectLambdaRequest,DeleteAccessPointForObjectLambdaResult> asyncHandler)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Deletes the specified Object Lambda Access Point.
The following actions are related to DeleteAccessPointForObjectLambda:
deleteAccessPointForObjectLambdaAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<DeleteAccessPointPolicyResult> deleteAccessPointPolicyAsync(DeleteAccessPointPolicyRequest request)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Deletes the access point policy for the specified access point.
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
The following actions are related to DeleteAccessPointPolicy:
deleteAccessPointPolicyAsync in interface AWSS3ControlAsyncpublic Future<DeleteAccessPointPolicyResult> deleteAccessPointPolicyAsync(DeleteAccessPointPolicyRequest request, AsyncHandler<DeleteAccessPointPolicyRequest,DeleteAccessPointPolicyResult> asyncHandler)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Deletes the access point policy for the specified access point.
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
The following actions are related to DeleteAccessPointPolicy:
deleteAccessPointPolicyAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<DeleteAccessPointPolicyForObjectLambdaResult> deleteAccessPointPolicyForObjectLambdaAsync(DeleteAccessPointPolicyForObjectLambdaRequest request)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Removes the resource policy for an Object Lambda Access Point.
The following actions are related to DeleteAccessPointPolicyForObjectLambda:
deleteAccessPointPolicyForObjectLambdaAsync in interface AWSS3ControlAsyncpublic Future<DeleteAccessPointPolicyForObjectLambdaResult> deleteAccessPointPolicyForObjectLambdaAsync(DeleteAccessPointPolicyForObjectLambdaRequest request, AsyncHandler<DeleteAccessPointPolicyForObjectLambdaRequest,DeleteAccessPointPolicyForObjectLambdaResult> asyncHandler)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Removes the resource policy for an Object Lambda Access Point.
The following actions are related to DeleteAccessPointPolicyForObjectLambda:
deleteAccessPointPolicyForObjectLambdaAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<DeleteBucketResult> deleteBucketAsync(DeleteBucketRequest request)
AWSS3ControlAsyncThis action deletes an Amazon S3 on Outposts bucket. To delete an S3 bucket, see DeleteBucket in the Amazon S3 API Reference.
Deletes the Amazon S3 on Outposts bucket. All objects (including all object versions and delete markers) in the bucket must be deleted before the bucket itself can be deleted. For more information, see Using Amazon S3 on Outposts in Amazon S3 User Guide.
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
Related Resources
deleteBucketAsync in interface AWSS3ControlAsyncpublic Future<DeleteBucketResult> deleteBucketAsync(DeleteBucketRequest request, AsyncHandler<DeleteBucketRequest,DeleteBucketResult> asyncHandler)
AWSS3ControlAsyncThis action deletes an Amazon S3 on Outposts bucket. To delete an S3 bucket, see DeleteBucket in the Amazon S3 API Reference.
Deletes the Amazon S3 on Outposts bucket. All objects (including all object versions and delete markers) in the bucket must be deleted before the bucket itself can be deleted. For more information, see Using Amazon S3 on Outposts in Amazon S3 User Guide.
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
Related Resources
deleteBucketAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<DeleteBucketLifecycleConfigurationResult> deleteBucketLifecycleConfigurationAsync(DeleteBucketLifecycleConfigurationRequest request)
AWSS3ControlAsyncThis action deletes an Amazon S3 on Outposts bucket's lifecycle configuration. To delete an S3 bucket's lifecycle configuration, see DeleteBucketLifecycle in the Amazon S3 API Reference.
Deletes the lifecycle configuration from the specified Outposts bucket. Amazon S3 on Outposts removes all the lifecycle configuration rules in the lifecycle subresource associated with the bucket. Your objects never expire, and Amazon S3 on Outposts no longer automatically deletes any objects on the basis of rules contained in the deleted lifecycle configuration. For more information, see Using Amazon S3 on Outposts in Amazon S3 User Guide.
To use this operation, you must have permission to perform the s3-outposts:PutLifecycleConfiguration
action. By default, the bucket owner has this permission and the Outposts bucket owner can grant this permission
to others.
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
For more information about object expiration, see Elements to Describe Lifecycle Actions.
Related actions include:
deleteBucketLifecycleConfigurationAsync in interface AWSS3ControlAsyncpublic Future<DeleteBucketLifecycleConfigurationResult> deleteBucketLifecycleConfigurationAsync(DeleteBucketLifecycleConfigurationRequest request, AsyncHandler<DeleteBucketLifecycleConfigurationRequest,DeleteBucketLifecycleConfigurationResult> asyncHandler)
AWSS3ControlAsyncThis action deletes an Amazon S3 on Outposts bucket's lifecycle configuration. To delete an S3 bucket's lifecycle configuration, see DeleteBucketLifecycle in the Amazon S3 API Reference.
Deletes the lifecycle configuration from the specified Outposts bucket. Amazon S3 on Outposts removes all the lifecycle configuration rules in the lifecycle subresource associated with the bucket. Your objects never expire, and Amazon S3 on Outposts no longer automatically deletes any objects on the basis of rules contained in the deleted lifecycle configuration. For more information, see Using Amazon S3 on Outposts in Amazon S3 User Guide.
To use this operation, you must have permission to perform the s3-outposts:PutLifecycleConfiguration
action. By default, the bucket owner has this permission and the Outposts bucket owner can grant this permission
to others.
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
For more information about object expiration, see Elements to Describe Lifecycle Actions.
Related actions include:
deleteBucketLifecycleConfigurationAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<DeleteBucketPolicyResult> deleteBucketPolicyAsync(DeleteBucketPolicyRequest request)
AWSS3ControlAsyncThis action deletes an Amazon S3 on Outposts bucket policy. To delete an S3 bucket policy, see DeleteBucketPolicy in the Amazon S3 API Reference.
This implementation of the DELETE action uses the policy subresource to delete the policy of a specified Amazon
S3 on Outposts bucket. If you are using an identity other than the root user of the Amazon Web Services account
that owns the bucket, the calling identity must have the s3-outposts:DeleteBucketPolicy permissions
on the specified Outposts bucket and belong to the bucket owner's account to use this action. For more
information, see Using Amazon
S3 on Outposts in Amazon S3 User Guide.
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 Amazon Web Services account that owns a bucket can always use this action, 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.
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
The following actions are related to DeleteBucketPolicy:
deleteBucketPolicyAsync in interface AWSS3ControlAsyncpublic Future<DeleteBucketPolicyResult> deleteBucketPolicyAsync(DeleteBucketPolicyRequest request, AsyncHandler<DeleteBucketPolicyRequest,DeleteBucketPolicyResult> asyncHandler)
AWSS3ControlAsyncThis action deletes an Amazon S3 on Outposts bucket policy. To delete an S3 bucket policy, see DeleteBucketPolicy in the Amazon S3 API Reference.
This implementation of the DELETE action uses the policy subresource to delete the policy of a specified Amazon
S3 on Outposts bucket. If you are using an identity other than the root user of the Amazon Web Services account
that owns the bucket, the calling identity must have the s3-outposts:DeleteBucketPolicy permissions
on the specified Outposts bucket and belong to the bucket owner's account to use this action. For more
information, see Using Amazon
S3 on Outposts in Amazon S3 User Guide.
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 Amazon Web Services account that owns a bucket can always use this action, 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.
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
The following actions are related to DeleteBucketPolicy:
deleteBucketPolicyAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<DeleteBucketReplicationResult> deleteBucketReplicationAsync(DeleteBucketReplicationRequest request)
AWSS3ControlAsyncThis operation deletes an Amazon S3 on Outposts bucket's replication configuration. To delete an S3 bucket's replication configuration, see DeleteBucketReplication in the Amazon S3 API Reference.
Deletes the replication configuration from the specified S3 on Outposts bucket.
To use this operation, you must have permissions to perform the
s3-outposts:PutReplicationConfiguration action. The Outposts bucket owner has this permission by
default and can grant it to others. For more information about permissions, see Setting up IAM with S3 on
Outposts and Managing access to S3 on
Outposts buckets in the Amazon S3 User Guide.
It can take a while to propagate PUT or DELETE requests for a replication configuration
to all S3 on Outposts systems. Therefore, the replication configuration that's returned by a GET
request soon after a PUT or DELETE request might return a more recent result than
what's on the Outpost. If an Outpost is offline, the delay in updating the replication configuration on that
Outpost can be significant.
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
For information about S3 replication on Outposts configuration, see Replicating objects for S3 on Outposts in the Amazon S3 User Guide.
The following operations are related to DeleteBucketReplication:
deleteBucketReplicationAsync in interface AWSS3ControlAsyncpublic Future<DeleteBucketReplicationResult> deleteBucketReplicationAsync(DeleteBucketReplicationRequest request, AsyncHandler<DeleteBucketReplicationRequest,DeleteBucketReplicationResult> asyncHandler)
AWSS3ControlAsyncThis operation deletes an Amazon S3 on Outposts bucket's replication configuration. To delete an S3 bucket's replication configuration, see DeleteBucketReplication in the Amazon S3 API Reference.
Deletes the replication configuration from the specified S3 on Outposts bucket.
To use this operation, you must have permissions to perform the
s3-outposts:PutReplicationConfiguration action. The Outposts bucket owner has this permission by
default and can grant it to others. For more information about permissions, see Setting up IAM with S3 on
Outposts and Managing access to S3 on
Outposts buckets in the Amazon S3 User Guide.
It can take a while to propagate PUT or DELETE requests for a replication configuration
to all S3 on Outposts systems. Therefore, the replication configuration that's returned by a GET
request soon after a PUT or DELETE request might return a more recent result than
what's on the Outpost. If an Outpost is offline, the delay in updating the replication configuration on that
Outpost can be significant.
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
For information about S3 replication on Outposts configuration, see Replicating objects for S3 on Outposts in the Amazon S3 User Guide.
The following operations are related to DeleteBucketReplication:
deleteBucketReplicationAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<DeleteBucketTaggingResult> deleteBucketTaggingAsync(DeleteBucketTaggingRequest request)
AWSS3ControlAsyncThis action deletes an Amazon S3 on Outposts bucket's tags. To delete an S3 bucket tags, see DeleteBucketTagging in the Amazon S3 API Reference.
Deletes the tags from the Outposts bucket. For more information, see Using Amazon S3 on Outposts in Amazon S3 User Guide.
To use this action, you must have permission to perform the PutBucketTagging action. By default, the
bucket owner has this permission and can grant this permission to others.
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
The following actions are related to DeleteBucketTagging:
deleteBucketTaggingAsync in interface AWSS3ControlAsyncpublic Future<DeleteBucketTaggingResult> deleteBucketTaggingAsync(DeleteBucketTaggingRequest request, AsyncHandler<DeleteBucketTaggingRequest,DeleteBucketTaggingResult> asyncHandler)
AWSS3ControlAsyncThis action deletes an Amazon S3 on Outposts bucket's tags. To delete an S3 bucket tags, see DeleteBucketTagging in the Amazon S3 API Reference.
Deletes the tags from the Outposts bucket. For more information, see Using Amazon S3 on Outposts in Amazon S3 User Guide.
To use this action, you must have permission to perform the PutBucketTagging action. By default, the
bucket owner has this permission and can grant this permission to others.
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
The following actions are related to DeleteBucketTagging:
deleteBucketTaggingAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<DeleteJobTaggingResult> deleteJobTaggingAsync(DeleteJobTaggingRequest request)
AWSS3ControlAsyncRemoves the entire tag set from the specified S3 Batch Operations job.
To use the DeleteJobTagging operation, you must have permission to perform the
s3:DeleteJobTagging action. For more information, see Controlling access and labeling jobs using tags in the Amazon S3 User Guide.
Related actions include:
deleteJobTaggingAsync in interface AWSS3ControlAsyncpublic Future<DeleteJobTaggingResult> deleteJobTaggingAsync(DeleteJobTaggingRequest request, AsyncHandler<DeleteJobTaggingRequest,DeleteJobTaggingResult> asyncHandler)
AWSS3ControlAsyncRemoves the entire tag set from the specified S3 Batch Operations job.
To use the DeleteJobTagging operation, you must have permission to perform the
s3:DeleteJobTagging action. For more information, see Controlling access and labeling jobs using tags in the Amazon S3 User Guide.
Related actions include:
deleteJobTaggingAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<DeleteMultiRegionAccessPointResult> deleteMultiRegionAccessPointAsync(DeleteMultiRegionAccessPointRequest request)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Deletes a Multi-Region Access Point. This action does not delete the buckets associated with the Multi-Region Access Point, only the Multi-Region Access Point itself.
This action will always be routed to the US West (Oregon) Region. For more information about the restrictions around working with Multi-Region Access Points, see Multi-Region Access Point restrictions and limitations in the Amazon S3 User Guide.
This request is asynchronous, meaning that you might receive a response before the command has completed. When
this request provides a response, it provides a token that you can use to monitor the status of the request with
DescribeMultiRegionAccessPointOperation.
The following actions are related to DeleteMultiRegionAccessPoint:
deleteMultiRegionAccessPointAsync in interface AWSS3ControlAsyncpublic Future<DeleteMultiRegionAccessPointResult> deleteMultiRegionAccessPointAsync(DeleteMultiRegionAccessPointRequest request, AsyncHandler<DeleteMultiRegionAccessPointRequest,DeleteMultiRegionAccessPointResult> asyncHandler)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Deletes a Multi-Region Access Point. This action does not delete the buckets associated with the Multi-Region Access Point, only the Multi-Region Access Point itself.
This action will always be routed to the US West (Oregon) Region. For more information about the restrictions around working with Multi-Region Access Points, see Multi-Region Access Point restrictions and limitations in the Amazon S3 User Guide.
This request is asynchronous, meaning that you might receive a response before the command has completed. When
this request provides a response, it provides a token that you can use to monitor the status of the request with
DescribeMultiRegionAccessPointOperation.
The following actions are related to DeleteMultiRegionAccessPoint:
deleteMultiRegionAccessPointAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<DeletePublicAccessBlockResult> deletePublicAccessBlockAsync(DeletePublicAccessBlockRequest request)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Removes the PublicAccessBlock configuration for an Amazon Web Services account. For more
information, see Using Amazon S3
block public access.
Related actions include:
deletePublicAccessBlockAsync in interface AWSS3ControlAsyncpublic Future<DeletePublicAccessBlockResult> deletePublicAccessBlockAsync(DeletePublicAccessBlockRequest request, AsyncHandler<DeletePublicAccessBlockRequest,DeletePublicAccessBlockResult> asyncHandler)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Removes the PublicAccessBlock configuration for an Amazon Web Services account. For more
information, see Using Amazon S3
block public access.
Related actions include:
deletePublicAccessBlockAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<DeleteStorageLensConfigurationResult> deleteStorageLensConfigurationAsync(DeleteStorageLensConfigurationRequest request)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Deletes the Amazon S3 Storage Lens configuration. For more information about S3 Storage Lens, see Assessing your storage activity and usage with Amazon S3 Storage Lens in the Amazon S3 User Guide.
To use this action, you must have permission to perform the s3:DeleteStorageLensConfiguration
action. For more information, see Setting permissions to
use Amazon S3 Storage Lens in the Amazon S3 User Guide.
deleteStorageLensConfigurationAsync in interface AWSS3ControlAsyncpublic Future<DeleteStorageLensConfigurationResult> deleteStorageLensConfigurationAsync(DeleteStorageLensConfigurationRequest request, AsyncHandler<DeleteStorageLensConfigurationRequest,DeleteStorageLensConfigurationResult> asyncHandler)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Deletes the Amazon S3 Storage Lens configuration. For more information about S3 Storage Lens, see Assessing your storage activity and usage with Amazon S3 Storage Lens in the Amazon S3 User Guide.
To use this action, you must have permission to perform the s3:DeleteStorageLensConfiguration
action. For more information, see Setting permissions to
use Amazon S3 Storage Lens in the Amazon S3 User Guide.
deleteStorageLensConfigurationAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<DeleteStorageLensConfigurationTaggingResult> deleteStorageLensConfigurationTaggingAsync(DeleteStorageLensConfigurationTaggingRequest request)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Deletes the Amazon S3 Storage Lens configuration tags. For more information about S3 Storage Lens, see Assessing your storage activity and usage with Amazon S3 Storage Lens in the Amazon S3 User Guide.
To use this action, you must have permission to perform the s3:DeleteStorageLensConfigurationTagging
action. For more information, see Setting permissions to
use Amazon S3 Storage Lens in the Amazon S3 User Guide.
deleteStorageLensConfigurationTaggingAsync in interface AWSS3ControlAsyncpublic Future<DeleteStorageLensConfigurationTaggingResult> deleteStorageLensConfigurationTaggingAsync(DeleteStorageLensConfigurationTaggingRequest request, AsyncHandler<DeleteStorageLensConfigurationTaggingRequest,DeleteStorageLensConfigurationTaggingResult> asyncHandler)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Deletes the Amazon S3 Storage Lens configuration tags. For more information about S3 Storage Lens, see Assessing your storage activity and usage with Amazon S3 Storage Lens in the Amazon S3 User Guide.
To use this action, you must have permission to perform the s3:DeleteStorageLensConfigurationTagging
action. For more information, see Setting permissions to
use Amazon S3 Storage Lens in the Amazon S3 User Guide.
deleteStorageLensConfigurationTaggingAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<DeleteStorageLensGroupResult> deleteStorageLensGroupAsync(DeleteStorageLensGroupRequest request)
AWSS3ControlAsyncDeletes an existing S3 Storage Lens group.
To use this operation, you must have the permission to perform the s3:DeleteStorageLensGroup action.
For more information about the required Storage Lens Groups permissions, see Setting account permissions to use S3 Storage Lens groups.
For information about Storage Lens groups errors, see List of Amazon S3 Storage Lens error codes.
deleteStorageLensGroupAsync in interface AWSS3ControlAsyncpublic Future<DeleteStorageLensGroupResult> deleteStorageLensGroupAsync(DeleteStorageLensGroupRequest request, AsyncHandler<DeleteStorageLensGroupRequest,DeleteStorageLensGroupResult> asyncHandler)
AWSS3ControlAsyncDeletes an existing S3 Storage Lens group.
To use this operation, you must have the permission to perform the s3:DeleteStorageLensGroup action.
For more information about the required Storage Lens Groups permissions, see Setting account permissions to use S3 Storage Lens groups.
For information about Storage Lens groups errors, see List of Amazon S3 Storage Lens error codes.
deleteStorageLensGroupAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<DescribeJobResult> describeJobAsync(DescribeJobRequest request)
AWSS3ControlAsyncRetrieves the configuration parameters and status for a Batch Operations job. For more information, see S3 Batch Operations in the Amazon S3 User Guide.
To use the DescribeJob operation, you must have permission to perform the
s3:DescribeJob action.
Related actions include:
describeJobAsync in interface AWSS3ControlAsyncpublic Future<DescribeJobResult> describeJobAsync(DescribeJobRequest request, AsyncHandler<DescribeJobRequest,DescribeJobResult> asyncHandler)
AWSS3ControlAsyncRetrieves the configuration parameters and status for a Batch Operations job. For more information, see S3 Batch Operations in the Amazon S3 User Guide.
To use the DescribeJob operation, you must have permission to perform the
s3:DescribeJob action.
Related actions include:
describeJobAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<DescribeMultiRegionAccessPointOperationResult> describeMultiRegionAccessPointOperationAsync(DescribeMultiRegionAccessPointOperationRequest request)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Retrieves the status of an asynchronous request to manage a Multi-Region Access Point. For more information about managing Multi-Region Access Points and how asynchronous requests work, see Using Multi-Region Access Points in the Amazon S3 User Guide.
The following actions are related to GetMultiRegionAccessPoint:
describeMultiRegionAccessPointOperationAsync in interface AWSS3ControlAsyncpublic Future<DescribeMultiRegionAccessPointOperationResult> describeMultiRegionAccessPointOperationAsync(DescribeMultiRegionAccessPointOperationRequest request, AsyncHandler<DescribeMultiRegionAccessPointOperationRequest,DescribeMultiRegionAccessPointOperationResult> asyncHandler)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Retrieves the status of an asynchronous request to manage a Multi-Region Access Point. For more information about managing Multi-Region Access Points and how asynchronous requests work, see Using Multi-Region Access Points in the Amazon S3 User Guide.
The following actions are related to GetMultiRegionAccessPoint:
describeMultiRegionAccessPointOperationAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<DissociateAccessGrantsIdentityCenterResult> dissociateAccessGrantsIdentityCenterAsync(DissociateAccessGrantsIdentityCenterRequest request)
AWSS3ControlAsyncDissociates the Amazon Web Services IAM Identity Center instance from the S3 Access Grants instance.
You must have the s3:DissociateAccessGrantsIdentityCenter permission to use this operation.
You must have the sso:DeleteApplication permission to use this operation.
dissociateAccessGrantsIdentityCenterAsync in interface AWSS3ControlAsyncpublic Future<DissociateAccessGrantsIdentityCenterResult> dissociateAccessGrantsIdentityCenterAsync(DissociateAccessGrantsIdentityCenterRequest request, AsyncHandler<DissociateAccessGrantsIdentityCenterRequest,DissociateAccessGrantsIdentityCenterResult> asyncHandler)
AWSS3ControlAsyncDissociates the Amazon Web Services IAM Identity Center instance from the S3 Access Grants instance.
You must have the s3:DissociateAccessGrantsIdentityCenter permission to use this operation.
You must have the sso:DeleteApplication permission to use this operation.
dissociateAccessGrantsIdentityCenterAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<GetAccessGrantResult> getAccessGrantAsync(GetAccessGrantRequest request)
AWSS3ControlAsyncGet the details of an access grant from your S3 Access Grants instance.
You must have the s3:GetAccessGrant permission to use this operation.
getAccessGrantAsync in interface AWSS3ControlAsyncpublic Future<GetAccessGrantResult> getAccessGrantAsync(GetAccessGrantRequest request, AsyncHandler<GetAccessGrantRequest,GetAccessGrantResult> asyncHandler)
AWSS3ControlAsyncGet the details of an access grant from your S3 Access Grants instance.
You must have the s3:GetAccessGrant permission to use this operation.
getAccessGrantAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<GetAccessGrantsInstanceResult> getAccessGrantsInstanceAsync(GetAccessGrantsInstanceRequest request)
AWSS3ControlAsyncRetrieves the S3 Access Grants instance for a Region in your account.
You must have the s3:GetAccessGrantsInstance permission to use this operation.
getAccessGrantsInstanceAsync in interface AWSS3ControlAsyncpublic Future<GetAccessGrantsInstanceResult> getAccessGrantsInstanceAsync(GetAccessGrantsInstanceRequest request, AsyncHandler<GetAccessGrantsInstanceRequest,GetAccessGrantsInstanceResult> asyncHandler)
AWSS3ControlAsyncRetrieves the S3 Access Grants instance for a Region in your account.
You must have the s3:GetAccessGrantsInstance permission to use this operation.
getAccessGrantsInstanceAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<GetAccessGrantsInstanceForPrefixResult> getAccessGrantsInstanceForPrefixAsync(GetAccessGrantsInstanceForPrefixRequest request)
AWSS3ControlAsyncRetrieve the S3 Access Grants instance that contains a particular prefix.
You must have the s3:GetAccessGrantsInstanceForPrefix permission for the caller account to use this
operation.
The prefix owner account must grant you the following permissions to their S3 Access Grants instance:
s3:GetAccessGrantsInstanceForPrefix.
getAccessGrantsInstanceForPrefixAsync in interface AWSS3ControlAsyncpublic Future<GetAccessGrantsInstanceForPrefixResult> getAccessGrantsInstanceForPrefixAsync(GetAccessGrantsInstanceForPrefixRequest request, AsyncHandler<GetAccessGrantsInstanceForPrefixRequest,GetAccessGrantsInstanceForPrefixResult> asyncHandler)
AWSS3ControlAsyncRetrieve the S3 Access Grants instance that contains a particular prefix.
You must have the s3:GetAccessGrantsInstanceForPrefix permission for the caller account to use this
operation.
The prefix owner account must grant you the following permissions to their S3 Access Grants instance:
s3:GetAccessGrantsInstanceForPrefix.
getAccessGrantsInstanceForPrefixAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<GetAccessGrantsInstanceResourcePolicyResult> getAccessGrantsInstanceResourcePolicyAsync(GetAccessGrantsInstanceResourcePolicyRequest request)
AWSS3ControlAsyncReturns the resource policy of the S3 Access Grants instance.
You must have the s3:GetAccessGrantsInstanceResourcePolicy permission to use this operation.
getAccessGrantsInstanceResourcePolicyAsync in interface AWSS3ControlAsyncpublic Future<GetAccessGrantsInstanceResourcePolicyResult> getAccessGrantsInstanceResourcePolicyAsync(GetAccessGrantsInstanceResourcePolicyRequest request, AsyncHandler<GetAccessGrantsInstanceResourcePolicyRequest,GetAccessGrantsInstanceResourcePolicyResult> asyncHandler)
AWSS3ControlAsyncReturns the resource policy of the S3 Access Grants instance.
You must have the s3:GetAccessGrantsInstanceResourcePolicy permission to use this operation.
getAccessGrantsInstanceResourcePolicyAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<GetAccessGrantsLocationResult> getAccessGrantsLocationAsync(GetAccessGrantsLocationRequest request)
AWSS3ControlAsyncRetrieves the details of a particular location registered in your S3 Access Grants instance.
You must have the s3:GetAccessGrantsLocation permission to use this operation.
getAccessGrantsLocationAsync in interface AWSS3ControlAsyncpublic Future<GetAccessGrantsLocationResult> getAccessGrantsLocationAsync(GetAccessGrantsLocationRequest request, AsyncHandler<GetAccessGrantsLocationRequest,GetAccessGrantsLocationResult> asyncHandler)
AWSS3ControlAsyncRetrieves the details of a particular location registered in your S3 Access Grants instance.
You must have the s3:GetAccessGrantsLocation permission to use this operation.
getAccessGrantsLocationAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<GetAccessPointResult> getAccessPointAsync(GetAccessPointRequest request)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Returns configuration information about the specified access point.
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
The following actions are related to GetAccessPoint:
getAccessPointAsync in interface AWSS3ControlAsyncpublic Future<GetAccessPointResult> getAccessPointAsync(GetAccessPointRequest request, AsyncHandler<GetAccessPointRequest,GetAccessPointResult> asyncHandler)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Returns configuration information about the specified access point.
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
The following actions are related to GetAccessPoint:
getAccessPointAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<GetAccessPointConfigurationForObjectLambdaResult> getAccessPointConfigurationForObjectLambdaAsync(GetAccessPointConfigurationForObjectLambdaRequest request)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Returns configuration for an Object Lambda Access Point.
The following actions are related to GetAccessPointConfigurationForObjectLambda:
getAccessPointConfigurationForObjectLambdaAsync in interface AWSS3ControlAsyncpublic Future<GetAccessPointConfigurationForObjectLambdaResult> getAccessPointConfigurationForObjectLambdaAsync(GetAccessPointConfigurationForObjectLambdaRequest request, AsyncHandler<GetAccessPointConfigurationForObjectLambdaRequest,GetAccessPointConfigurationForObjectLambdaResult> asyncHandler)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Returns configuration for an Object Lambda Access Point.
The following actions are related to GetAccessPointConfigurationForObjectLambda:
getAccessPointConfigurationForObjectLambdaAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<GetAccessPointForObjectLambdaResult> getAccessPointForObjectLambdaAsync(GetAccessPointForObjectLambdaRequest request)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Returns configuration information about the specified Object Lambda Access Point
The following actions are related to GetAccessPointForObjectLambda:
getAccessPointForObjectLambdaAsync in interface AWSS3ControlAsyncpublic Future<GetAccessPointForObjectLambdaResult> getAccessPointForObjectLambdaAsync(GetAccessPointForObjectLambdaRequest request, AsyncHandler<GetAccessPointForObjectLambdaRequest,GetAccessPointForObjectLambdaResult> asyncHandler)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Returns configuration information about the specified Object Lambda Access Point
The following actions are related to GetAccessPointForObjectLambda:
getAccessPointForObjectLambdaAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<GetAccessPointPolicyResult> getAccessPointPolicyAsync(GetAccessPointPolicyRequest request)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Returns the access point policy associated with the specified access point.
The following actions are related to GetAccessPointPolicy:
getAccessPointPolicyAsync in interface AWSS3ControlAsyncpublic Future<GetAccessPointPolicyResult> getAccessPointPolicyAsync(GetAccessPointPolicyRequest request, AsyncHandler<GetAccessPointPolicyRequest,GetAccessPointPolicyResult> asyncHandler)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Returns the access point policy associated with the specified access point.
The following actions are related to GetAccessPointPolicy:
getAccessPointPolicyAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<GetAccessPointPolicyForObjectLambdaResult> getAccessPointPolicyForObjectLambdaAsync(GetAccessPointPolicyForObjectLambdaRequest request)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Returns the resource policy for an Object Lambda Access Point.
The following actions are related to GetAccessPointPolicyForObjectLambda:
getAccessPointPolicyForObjectLambdaAsync in interface AWSS3ControlAsyncpublic Future<GetAccessPointPolicyForObjectLambdaResult> getAccessPointPolicyForObjectLambdaAsync(GetAccessPointPolicyForObjectLambdaRequest request, AsyncHandler<GetAccessPointPolicyForObjectLambdaRequest,GetAccessPointPolicyForObjectLambdaResult> asyncHandler)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Returns the resource policy for an Object Lambda Access Point.
The following actions are related to GetAccessPointPolicyForObjectLambda:
getAccessPointPolicyForObjectLambdaAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<GetAccessPointPolicyStatusResult> getAccessPointPolicyStatusAsync(GetAccessPointPolicyStatusRequest request)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Indicates whether the specified access point currently has a policy that allows public access. For more information about public access through access points, see Managing Data Access with Amazon S3 access points in the Amazon S3 User Guide.
getAccessPointPolicyStatusAsync in interface AWSS3ControlAsyncpublic Future<GetAccessPointPolicyStatusResult> getAccessPointPolicyStatusAsync(GetAccessPointPolicyStatusRequest request, AsyncHandler<GetAccessPointPolicyStatusRequest,GetAccessPointPolicyStatusResult> asyncHandler)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Indicates whether the specified access point currently has a policy that allows public access. For more information about public access through access points, see Managing Data Access with Amazon S3 access points in the Amazon S3 User Guide.
getAccessPointPolicyStatusAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<GetAccessPointPolicyStatusForObjectLambdaResult> getAccessPointPolicyStatusForObjectLambdaAsync(GetAccessPointPolicyStatusForObjectLambdaRequest request)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Returns the status of the resource policy associated with an Object Lambda Access Point.
getAccessPointPolicyStatusForObjectLambdaAsync in interface AWSS3ControlAsyncpublic Future<GetAccessPointPolicyStatusForObjectLambdaResult> getAccessPointPolicyStatusForObjectLambdaAsync(GetAccessPointPolicyStatusForObjectLambdaRequest request, AsyncHandler<GetAccessPointPolicyStatusForObjectLambdaRequest,GetAccessPointPolicyStatusForObjectLambdaResult> asyncHandler)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Returns the status of the resource policy associated with an Object Lambda Access Point.
getAccessPointPolicyStatusForObjectLambdaAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<GetBucketResult> getBucketAsync(GetBucketRequest request)
AWSS3ControlAsyncGets an Amazon S3 on Outposts bucket. For more information, see Using Amazon S3 on Outposts in the Amazon S3 User Guide.
If you are using an identity other than the root user of the Amazon Web Services account that owns the Outposts
bucket, the calling identity must have the s3-outposts:GetBucket permissions on the specified
Outposts bucket and belong to the Outposts bucket owner's account in order to use this action. Only users from
Outposts bucket owner account with the right permissions can perform actions on an Outposts bucket.
If you don't have s3-outposts:GetBucket permissions or you're not using an identity that belongs to
the bucket owner's account, Amazon S3 returns a 403 Access Denied error.
The following actions are related to GetBucket for Amazon S3 on Outposts:
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
getBucketAsync in interface AWSS3ControlAsyncpublic Future<GetBucketResult> getBucketAsync(GetBucketRequest request, AsyncHandler<GetBucketRequest,GetBucketResult> asyncHandler)
AWSS3ControlAsyncGets an Amazon S3 on Outposts bucket. For more information, see Using Amazon S3 on Outposts in the Amazon S3 User Guide.
If you are using an identity other than the root user of the Amazon Web Services account that owns the Outposts
bucket, the calling identity must have the s3-outposts:GetBucket permissions on the specified
Outposts bucket and belong to the Outposts bucket owner's account in order to use this action. Only users from
Outposts bucket owner account with the right permissions can perform actions on an Outposts bucket.
If you don't have s3-outposts:GetBucket permissions or you're not using an identity that belongs to
the bucket owner's account, Amazon S3 returns a 403 Access Denied error.
The following actions are related to GetBucket for Amazon S3 on Outposts:
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
getBucketAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<GetBucketLifecycleConfigurationResult> getBucketLifecycleConfigurationAsync(GetBucketLifecycleConfigurationRequest request)
AWSS3ControlAsyncThis action gets an Amazon S3 on Outposts bucket's lifecycle configuration. To get an S3 bucket's lifecycle configuration, see GetBucketLifecycleConfiguration in the Amazon S3 API Reference.
Returns the lifecycle configuration information set on the Outposts bucket. For more information, see Using Amazon S3 on Outposts and for information about lifecycle configuration, see Object Lifecycle Management in Amazon S3 User Guide.
To use this action, you must have permission to perform the s3-outposts:GetLifecycleConfiguration
action. The Outposts 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.
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
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 actions are related to GetBucketLifecycleConfiguration:
getBucketLifecycleConfigurationAsync in interface AWSS3ControlAsyncpublic Future<GetBucketLifecycleConfigurationResult> getBucketLifecycleConfigurationAsync(GetBucketLifecycleConfigurationRequest request, AsyncHandler<GetBucketLifecycleConfigurationRequest,GetBucketLifecycleConfigurationResult> asyncHandler)
AWSS3ControlAsyncThis action gets an Amazon S3 on Outposts bucket's lifecycle configuration. To get an S3 bucket's lifecycle configuration, see GetBucketLifecycleConfiguration in the Amazon S3 API Reference.
Returns the lifecycle configuration information set on the Outposts bucket. For more information, see Using Amazon S3 on Outposts and for information about lifecycle configuration, see Object Lifecycle Management in Amazon S3 User Guide.
To use this action, you must have permission to perform the s3-outposts:GetLifecycleConfiguration
action. The Outposts 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.
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
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 actions are related to GetBucketLifecycleConfiguration:
getBucketLifecycleConfigurationAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<GetBucketPolicyResult> getBucketPolicyAsync(GetBucketPolicyRequest request)
AWSS3ControlAsyncThis action gets a bucket policy for an Amazon S3 on Outposts bucket. To get a policy for an S3 bucket, see GetBucketPolicy in the Amazon S3 API Reference.
Returns the policy of a specified Outposts bucket. For more information, see Using Amazon S3 on Outposts in the Amazon S3 User Guide.
If you are using an identity other than the root user of the Amazon Web Services account that owns the bucket,
the calling identity must have the GetBucketPolicy permissions on the specified bucket and belong to
the bucket owner's account in order to use this action.
Only users from Outposts bucket owner account with the right permissions can perform actions on an Outposts
bucket. If you don't have s3-outposts:GetBucketPolicy permissions or you're not using an identity
that belongs to the bucket owner's account, Amazon S3 returns a 403 Access Denied error.
As a security precaution, the root user of the Amazon Web Services account that owns a bucket can always use this action, 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.
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
The following actions are related to GetBucketPolicy:
getBucketPolicyAsync in interface AWSS3ControlAsyncpublic Future<GetBucketPolicyResult> getBucketPolicyAsync(GetBucketPolicyRequest request, AsyncHandler<GetBucketPolicyRequest,GetBucketPolicyResult> asyncHandler)
AWSS3ControlAsyncThis action gets a bucket policy for an Amazon S3 on Outposts bucket. To get a policy for an S3 bucket, see GetBucketPolicy in the Amazon S3 API Reference.
Returns the policy of a specified Outposts bucket. For more information, see Using Amazon S3 on Outposts in the Amazon S3 User Guide.
If you are using an identity other than the root user of the Amazon Web Services account that owns the bucket,
the calling identity must have the GetBucketPolicy permissions on the specified bucket and belong to
the bucket owner's account in order to use this action.
Only users from Outposts bucket owner account with the right permissions can perform actions on an Outposts
bucket. If you don't have s3-outposts:GetBucketPolicy permissions or you're not using an identity
that belongs to the bucket owner's account, Amazon S3 returns a 403 Access Denied error.
As a security precaution, the root user of the Amazon Web Services account that owns a bucket can always use this action, 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.
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
The following actions are related to GetBucketPolicy:
getBucketPolicyAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<GetBucketReplicationResult> getBucketReplicationAsync(GetBucketReplicationRequest request)
AWSS3ControlAsyncThis operation gets an Amazon S3 on Outposts bucket's replication configuration. To get an S3 bucket's replication configuration, see GetBucketReplication in the Amazon S3 API Reference.
Returns the replication configuration of an S3 on Outposts bucket. For more information about S3 on Outposts, see Using Amazon S3 on Outposts in the Amazon S3 User Guide. For information about S3 replication on Outposts configuration, see Replicating objects for S3 on Outposts in the Amazon S3 User Guide.
It can take a while to propagate PUT or DELETE requests for a replication configuration
to all S3 on Outposts systems. Therefore, the replication configuration that's returned by a GET
request soon after a PUT or DELETE request might return a more recent result than
what's on the Outpost. If an Outpost is offline, the delay in updating the replication configuration on that
Outpost can be significant.
This action requires permissions for the s3-outposts:GetReplicationConfiguration action. The
Outposts bucket owner has this permission by default and can grant it to others. For more information about
permissions, see Setting up
IAM with S3 on Outposts and Managing access to S3 on
Outposts bucket in the Amazon S3 User Guide.
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
If you include the Filter element in a replication configuration, you must also include the
DeleteMarkerReplication, Status, and Priority elements. The response also
returns those elements.
For information about S3 on Outposts replication failure reasons, see Replication failure reasons in the Amazon S3 User Guide.
The following operations are related to GetBucketReplication:
getBucketReplicationAsync in interface AWSS3ControlAsyncpublic Future<GetBucketReplicationResult> getBucketReplicationAsync(GetBucketReplicationRequest request, AsyncHandler<GetBucketReplicationRequest,GetBucketReplicationResult> asyncHandler)
AWSS3ControlAsyncThis operation gets an Amazon S3 on Outposts bucket's replication configuration. To get an S3 bucket's replication configuration, see GetBucketReplication in the Amazon S3 API Reference.
Returns the replication configuration of an S3 on Outposts bucket. For more information about S3 on Outposts, see Using Amazon S3 on Outposts in the Amazon S3 User Guide. For information about S3 replication on Outposts configuration, see Replicating objects for S3 on Outposts in the Amazon S3 User Guide.
It can take a while to propagate PUT or DELETE requests for a replication configuration
to all S3 on Outposts systems. Therefore, the replication configuration that's returned by a GET
request soon after a PUT or DELETE request might return a more recent result than
what's on the Outpost. If an Outpost is offline, the delay in updating the replication configuration on that
Outpost can be significant.
This action requires permissions for the s3-outposts:GetReplicationConfiguration action. The
Outposts bucket owner has this permission by default and can grant it to others. For more information about
permissions, see Setting up
IAM with S3 on Outposts and Managing access to S3 on
Outposts bucket in the Amazon S3 User Guide.
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
If you include the Filter element in a replication configuration, you must also include the
DeleteMarkerReplication, Status, and Priority elements. The response also
returns those elements.
For information about S3 on Outposts replication failure reasons, see Replication failure reasons in the Amazon S3 User Guide.
The following operations are related to GetBucketReplication:
getBucketReplicationAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<GetBucketTaggingResult> getBucketTaggingAsync(GetBucketTaggingRequest request)
AWSS3ControlAsyncThis action gets an Amazon S3 on Outposts bucket's tags. To get an S3 bucket tags, see GetBucketTagging in the Amazon S3 API Reference.
Returns the tag set associated with the Outposts bucket. For more information, see Using Amazon S3 on Outposts in the Amazon S3 User Guide.
To use this action, you must have permission to perform the 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.
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
The following actions are related to GetBucketTagging:
getBucketTaggingAsync in interface AWSS3ControlAsyncpublic Future<GetBucketTaggingResult> getBucketTaggingAsync(GetBucketTaggingRequest request, AsyncHandler<GetBucketTaggingRequest,GetBucketTaggingResult> asyncHandler)
AWSS3ControlAsyncThis action gets an Amazon S3 on Outposts bucket's tags. To get an S3 bucket tags, see GetBucketTagging in the Amazon S3 API Reference.
Returns the tag set associated with the Outposts bucket. For more information, see Using Amazon S3 on Outposts in the Amazon S3 User Guide.
To use this action, you must have permission to perform the 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.
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
The following actions are related to GetBucketTagging:
getBucketTaggingAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<GetBucketVersioningResult> getBucketVersioningAsync(GetBucketVersioningRequest request)
AWSS3ControlAsyncThis operation returns the versioning state for S3 on Outposts buckets only. To return the versioning state for an S3 bucket, see GetBucketVersioning in the Amazon S3 API Reference.
Returns the versioning state for an S3 on Outposts bucket. With S3 Versioning, you can save multiple distinct copies of your objects and recover from unintended user actions and application failures.
If you've never set versioning on your bucket, it has no versioning state. In that case, the
GetBucketVersioning request does not return a versioning state value.
For more information about versioning, see Versioning in the Amazon S3 User Guide.
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
The following operations are related to GetBucketVersioning for S3 on Outposts.
getBucketVersioningAsync in interface AWSS3ControlAsyncpublic Future<GetBucketVersioningResult> getBucketVersioningAsync(GetBucketVersioningRequest request, AsyncHandler<GetBucketVersioningRequest,GetBucketVersioningResult> asyncHandler)
AWSS3ControlAsyncThis operation returns the versioning state for S3 on Outposts buckets only. To return the versioning state for an S3 bucket, see GetBucketVersioning in the Amazon S3 API Reference.
Returns the versioning state for an S3 on Outposts bucket. With S3 Versioning, you can save multiple distinct copies of your objects and recover from unintended user actions and application failures.
If you've never set versioning on your bucket, it has no versioning state. In that case, the
GetBucketVersioning request does not return a versioning state value.
For more information about versioning, see Versioning in the Amazon S3 User Guide.
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
The following operations are related to GetBucketVersioning for S3 on Outposts.
getBucketVersioningAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<GetDataAccessResult> getDataAccessAsync(GetDataAccessRequest request)
AWSS3ControlAsyncReturns a temporary access credential from S3 Access Grants to the grantee or client application. The temporary credential is an Amazon Web Services STS token that grants them access to the S3 data.
You must have the s3:GetDataAccess permission to use this operation.
The IAM role that S3 Access Grants assumes must have the following permissions specified in the trust policy when
registering the location: sts:AssumeRole, for directory users or groups sts:SetContext,
and for IAM users or roles sts:SetSourceIdentity.
getDataAccessAsync in interface AWSS3ControlAsyncpublic Future<GetDataAccessResult> getDataAccessAsync(GetDataAccessRequest request, AsyncHandler<GetDataAccessRequest,GetDataAccessResult> asyncHandler)
AWSS3ControlAsyncReturns a temporary access credential from S3 Access Grants to the grantee or client application. The temporary credential is an Amazon Web Services STS token that grants them access to the S3 data.
You must have the s3:GetDataAccess permission to use this operation.
The IAM role that S3 Access Grants assumes must have the following permissions specified in the trust policy when
registering the location: sts:AssumeRole, for directory users or groups sts:SetContext,
and for IAM users or roles sts:SetSourceIdentity.
getDataAccessAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<GetJobTaggingResult> getJobTaggingAsync(GetJobTaggingRequest request)
AWSS3ControlAsyncReturns the tags on an S3 Batch Operations job.
To use the GetJobTagging operation, you must have permission to perform the
s3:GetJobTagging action. For more information, see Controlling access and labeling jobs using tags in the Amazon S3 User Guide.
Related actions include:
getJobTaggingAsync in interface AWSS3ControlAsyncpublic Future<GetJobTaggingResult> getJobTaggingAsync(GetJobTaggingRequest request, AsyncHandler<GetJobTaggingRequest,GetJobTaggingResult> asyncHandler)
AWSS3ControlAsyncReturns the tags on an S3 Batch Operations job.
To use the GetJobTagging operation, you must have permission to perform the
s3:GetJobTagging action. For more information, see Controlling access and labeling jobs using tags in the Amazon S3 User Guide.
Related actions include:
getJobTaggingAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<GetMultiRegionAccessPointResult> getMultiRegionAccessPointAsync(GetMultiRegionAccessPointRequest request)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Returns configuration information about the specified Multi-Region Access Point.
This action will always be routed to the US West (Oregon) Region. For more information about the restrictions around working with Multi-Region Access Points, see Multi-Region Access Point restrictions and limitations in the Amazon S3 User Guide.
The following actions are related to GetMultiRegionAccessPoint:
getMultiRegionAccessPointAsync in interface AWSS3ControlAsyncpublic Future<GetMultiRegionAccessPointResult> getMultiRegionAccessPointAsync(GetMultiRegionAccessPointRequest request, AsyncHandler<GetMultiRegionAccessPointRequest,GetMultiRegionAccessPointResult> asyncHandler)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Returns configuration information about the specified Multi-Region Access Point.
This action will always be routed to the US West (Oregon) Region. For more information about the restrictions around working with Multi-Region Access Points, see Multi-Region Access Point restrictions and limitations in the Amazon S3 User Guide.
The following actions are related to GetMultiRegionAccessPoint:
getMultiRegionAccessPointAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<GetMultiRegionAccessPointPolicyResult> getMultiRegionAccessPointPolicyAsync(GetMultiRegionAccessPointPolicyRequest request)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Returns the access control policy of the specified Multi-Region Access Point.
This action will always be routed to the US West (Oregon) Region. For more information about the restrictions around working with Multi-Region Access Points, see Multi-Region Access Point restrictions and limitations in the Amazon S3 User Guide.
The following actions are related to GetMultiRegionAccessPointPolicy:
getMultiRegionAccessPointPolicyAsync in interface AWSS3ControlAsyncpublic Future<GetMultiRegionAccessPointPolicyResult> getMultiRegionAccessPointPolicyAsync(GetMultiRegionAccessPointPolicyRequest request, AsyncHandler<GetMultiRegionAccessPointPolicyRequest,GetMultiRegionAccessPointPolicyResult> asyncHandler)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Returns the access control policy of the specified Multi-Region Access Point.
This action will always be routed to the US West (Oregon) Region. For more information about the restrictions around working with Multi-Region Access Points, see Multi-Region Access Point restrictions and limitations in the Amazon S3 User Guide.
The following actions are related to GetMultiRegionAccessPointPolicy:
getMultiRegionAccessPointPolicyAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<GetMultiRegionAccessPointPolicyStatusResult> getMultiRegionAccessPointPolicyStatusAsync(GetMultiRegionAccessPointPolicyStatusRequest request)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Indicates whether the specified Multi-Region Access Point has an access control policy that allows public access.
This action will always be routed to the US West (Oregon) Region. For more information about the restrictions around working with Multi-Region Access Points, see Multi-Region Access Point restrictions and limitations in the Amazon S3 User Guide.
The following actions are related to GetMultiRegionAccessPointPolicyStatus:
getMultiRegionAccessPointPolicyStatusAsync in interface AWSS3ControlAsyncpublic Future<GetMultiRegionAccessPointPolicyStatusResult> getMultiRegionAccessPointPolicyStatusAsync(GetMultiRegionAccessPointPolicyStatusRequest request, AsyncHandler<GetMultiRegionAccessPointPolicyStatusRequest,GetMultiRegionAccessPointPolicyStatusResult> asyncHandler)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Indicates whether the specified Multi-Region Access Point has an access control policy that allows public access.
This action will always be routed to the US West (Oregon) Region. For more information about the restrictions around working with Multi-Region Access Points, see Multi-Region Access Point restrictions and limitations in the Amazon S3 User Guide.
The following actions are related to GetMultiRegionAccessPointPolicyStatus:
getMultiRegionAccessPointPolicyStatusAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<GetMultiRegionAccessPointRoutesResult> getMultiRegionAccessPointRoutesAsync(GetMultiRegionAccessPointRoutesRequest request)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Returns the routing configuration for a Multi-Region Access Point, indicating which Regions are active or passive.
To obtain routing control changes and failover requests, use the Amazon S3 failover control infrastructure endpoints in these five Amazon Web Services Regions:
us-east-1
us-west-2
ap-southeast-2
ap-northeast-1
eu-west-1
getMultiRegionAccessPointRoutesAsync in interface AWSS3ControlAsyncpublic Future<GetMultiRegionAccessPointRoutesResult> getMultiRegionAccessPointRoutesAsync(GetMultiRegionAccessPointRoutesRequest request, AsyncHandler<GetMultiRegionAccessPointRoutesRequest,GetMultiRegionAccessPointRoutesResult> asyncHandler)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Returns the routing configuration for a Multi-Region Access Point, indicating which Regions are active or passive.
To obtain routing control changes and failover requests, use the Amazon S3 failover control infrastructure endpoints in these five Amazon Web Services Regions:
us-east-1
us-west-2
ap-southeast-2
ap-northeast-1
eu-west-1
getMultiRegionAccessPointRoutesAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<GetPublicAccessBlockResult> getPublicAccessBlockAsync(GetPublicAccessBlockRequest request)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Retrieves the PublicAccessBlock configuration for an Amazon Web Services account. For more
information, see Using Amazon S3
block public access.
Related actions include:
getPublicAccessBlockAsync in interface AWSS3ControlAsyncpublic Future<GetPublicAccessBlockResult> getPublicAccessBlockAsync(GetPublicAccessBlockRequest request, AsyncHandler<GetPublicAccessBlockRequest,GetPublicAccessBlockResult> asyncHandler)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Retrieves the PublicAccessBlock configuration for an Amazon Web Services account. For more
information, see Using Amazon S3
block public access.
Related actions include:
getPublicAccessBlockAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<GetStorageLensConfigurationResult> getStorageLensConfigurationAsync(GetStorageLensConfigurationRequest request)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Gets the Amazon S3 Storage Lens configuration. For more information, see Assessing your storage activity and usage with Amazon S3 Storage Lens in the Amazon S3 User Guide. For a complete list of S3 Storage Lens metrics, see S3 Storage Lens metrics glossary in the Amazon S3 User Guide.
To use this action, you must have permission to perform the s3:GetStorageLensConfiguration action.
For more information, see Setting permissions to
use Amazon S3 Storage Lens in the Amazon S3 User Guide.
getStorageLensConfigurationAsync in interface AWSS3ControlAsyncpublic Future<GetStorageLensConfigurationResult> getStorageLensConfigurationAsync(GetStorageLensConfigurationRequest request, AsyncHandler<GetStorageLensConfigurationRequest,GetStorageLensConfigurationResult> asyncHandler)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Gets the Amazon S3 Storage Lens configuration. For more information, see Assessing your storage activity and usage with Amazon S3 Storage Lens in the Amazon S3 User Guide. For a complete list of S3 Storage Lens metrics, see S3 Storage Lens metrics glossary in the Amazon S3 User Guide.
To use this action, you must have permission to perform the s3:GetStorageLensConfiguration action.
For more information, see Setting permissions to
use Amazon S3 Storage Lens in the Amazon S3 User Guide.
getStorageLensConfigurationAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<GetStorageLensConfigurationTaggingResult> getStorageLensConfigurationTaggingAsync(GetStorageLensConfigurationTaggingRequest request)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Gets the tags of Amazon S3 Storage Lens configuration. For more information about S3 Storage Lens, see Assessing your storage activity and usage with Amazon S3 Storage Lens in the Amazon S3 User Guide.
To use this action, you must have permission to perform the s3:GetStorageLensConfigurationTagging
action. For more information, see Setting permissions to
use Amazon S3 Storage Lens in the Amazon S3 User Guide.
getStorageLensConfigurationTaggingAsync in interface AWSS3ControlAsyncpublic Future<GetStorageLensConfigurationTaggingResult> getStorageLensConfigurationTaggingAsync(GetStorageLensConfigurationTaggingRequest request, AsyncHandler<GetStorageLensConfigurationTaggingRequest,GetStorageLensConfigurationTaggingResult> asyncHandler)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Gets the tags of Amazon S3 Storage Lens configuration. For more information about S3 Storage Lens, see Assessing your storage activity and usage with Amazon S3 Storage Lens in the Amazon S3 User Guide.
To use this action, you must have permission to perform the s3:GetStorageLensConfigurationTagging
action. For more information, see Setting permissions to
use Amazon S3 Storage Lens in the Amazon S3 User Guide.
getStorageLensConfigurationTaggingAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<GetStorageLensGroupResult> getStorageLensGroupAsync(GetStorageLensGroupRequest request)
AWSS3ControlAsyncRetrieves the Storage Lens group configuration details.
To use this operation, you must have the permission to perform the s3:GetStorageLensGroup action.
For more information about the required Storage Lens Groups permissions, see Setting account permissions to use S3 Storage Lens groups.
For information about Storage Lens groups errors, see List of Amazon S3 Storage Lens error codes.
getStorageLensGroupAsync in interface AWSS3ControlAsyncpublic Future<GetStorageLensGroupResult> getStorageLensGroupAsync(GetStorageLensGroupRequest request, AsyncHandler<GetStorageLensGroupRequest,GetStorageLensGroupResult> asyncHandler)
AWSS3ControlAsyncRetrieves the Storage Lens group configuration details.
To use this operation, you must have the permission to perform the s3:GetStorageLensGroup action.
For more information about the required Storage Lens Groups permissions, see Setting account permissions to use S3 Storage Lens groups.
For information about Storage Lens groups errors, see List of Amazon S3 Storage Lens error codes.
getStorageLensGroupAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<ListAccessGrantsResult> listAccessGrantsAsync(ListAccessGrantsRequest request)
AWSS3ControlAsyncReturns the list of access grants in your S3 Access Grants instance.
You must have the s3:ListAccessGrants permission to use this operation.
listAccessGrantsAsync in interface AWSS3ControlAsyncpublic Future<ListAccessGrantsResult> listAccessGrantsAsync(ListAccessGrantsRequest request, AsyncHandler<ListAccessGrantsRequest,ListAccessGrantsResult> asyncHandler)
AWSS3ControlAsyncReturns the list of access grants in your S3 Access Grants instance.
You must have the s3:ListAccessGrants permission to use this operation.
listAccessGrantsAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<ListAccessGrantsInstancesResult> listAccessGrantsInstancesAsync(ListAccessGrantsInstancesRequest request)
AWSS3ControlAsyncReturns a list of S3 Access Grants instances. An S3 Access Grants instance serves as a logical grouping for your individual access grants. You can only have one S3 Access Grants instance per Region per account.
You must have the s3:ListAccessGrantsInstances permission to use this operation.
listAccessGrantsInstancesAsync in interface AWSS3ControlAsyncpublic Future<ListAccessGrantsInstancesResult> listAccessGrantsInstancesAsync(ListAccessGrantsInstancesRequest request, AsyncHandler<ListAccessGrantsInstancesRequest,ListAccessGrantsInstancesResult> asyncHandler)
AWSS3ControlAsyncReturns a list of S3 Access Grants instances. An S3 Access Grants instance serves as a logical grouping for your individual access grants. You can only have one S3 Access Grants instance per Region per account.
You must have the s3:ListAccessGrantsInstances permission to use this operation.
listAccessGrantsInstancesAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<ListAccessGrantsLocationsResult> listAccessGrantsLocationsAsync(ListAccessGrantsLocationsRequest request)
AWSS3ControlAsyncReturns a list of the locations registered in your S3 Access Grants instance.
You must have the s3:ListAccessGrantsLocations permission to use this operation.
listAccessGrantsLocationsAsync in interface AWSS3ControlAsyncpublic Future<ListAccessGrantsLocationsResult> listAccessGrantsLocationsAsync(ListAccessGrantsLocationsRequest request, AsyncHandler<ListAccessGrantsLocationsRequest,ListAccessGrantsLocationsResult> asyncHandler)
AWSS3ControlAsyncReturns a list of the locations registered in your S3 Access Grants instance.
You must have the s3:ListAccessGrantsLocations permission to use this operation.
listAccessGrantsLocationsAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<ListAccessPointsResult> listAccessPointsAsync(ListAccessPointsRequest request)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Returns a list of the access points that are owned by the current account that's associated with the specified
bucket. You can retrieve up to 1000 access points per call. If the specified bucket has more than 1,000 access
points (or the number specified in maxResults, whichever is less), the response will include a
continuation token that you can use to list the additional access points.
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
The following actions are related to ListAccessPoints:
listAccessPointsAsync in interface AWSS3ControlAsyncpublic Future<ListAccessPointsResult> listAccessPointsAsync(ListAccessPointsRequest request, AsyncHandler<ListAccessPointsRequest,ListAccessPointsResult> asyncHandler)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Returns a list of the access points that are owned by the current account that's associated with the specified
bucket. You can retrieve up to 1000 access points per call. If the specified bucket has more than 1,000 access
points (or the number specified in maxResults, whichever is less), the response will include a
continuation token that you can use to list the additional access points.
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
The following actions are related to ListAccessPoints:
listAccessPointsAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<ListAccessPointsForObjectLambdaResult> listAccessPointsForObjectLambdaAsync(ListAccessPointsForObjectLambdaRequest request)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Returns some or all (up to 1,000) access points associated with the Object Lambda Access Point per call. If there are more access points than what can be returned in one call, the response will include a continuation token that you can use to list the additional access points.
The following actions are related to ListAccessPointsForObjectLambda:
listAccessPointsForObjectLambdaAsync in interface AWSS3ControlAsyncpublic Future<ListAccessPointsForObjectLambdaResult> listAccessPointsForObjectLambdaAsync(ListAccessPointsForObjectLambdaRequest request, AsyncHandler<ListAccessPointsForObjectLambdaRequest,ListAccessPointsForObjectLambdaResult> asyncHandler)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Returns some or all (up to 1,000) access points associated with the Object Lambda Access Point per call. If there are more access points than what can be returned in one call, the response will include a continuation token that you can use to list the additional access points.
The following actions are related to ListAccessPointsForObjectLambda:
listAccessPointsForObjectLambdaAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<ListJobsResult> listJobsAsync(ListJobsRequest request)
AWSS3ControlAsyncLists current S3 Batch Operations jobs as well as the jobs that have ended within the last 90 days for the Amazon Web Services account making the request. For more information, see S3 Batch Operations in the Amazon S3 User Guide.
To use the ListJobs operation, you must have permission to perform the s3:ListJobs
action.
Related actions include:
listJobsAsync in interface AWSS3ControlAsyncpublic Future<ListJobsResult> listJobsAsync(ListJobsRequest request, AsyncHandler<ListJobsRequest,ListJobsResult> asyncHandler)
AWSS3ControlAsyncLists current S3 Batch Operations jobs as well as the jobs that have ended within the last 90 days for the Amazon Web Services account making the request. For more information, see S3 Batch Operations in the Amazon S3 User Guide.
To use the ListJobs operation, you must have permission to perform the s3:ListJobs
action.
Related actions include:
listJobsAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<ListMultiRegionAccessPointsResult> listMultiRegionAccessPointsAsync(ListMultiRegionAccessPointsRequest request)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Returns a list of the Multi-Region Access Points currently associated with the specified Amazon Web Services account. Each call can return up to 100 Multi-Region Access Points, the maximum number of Multi-Region Access Points that can be associated with a single account.
This action will always be routed to the US West (Oregon) Region. For more information about the restrictions around working with Multi-Region Access Points, see Multi-Region Access Point restrictions and limitations in the Amazon S3 User Guide.
The following actions are related to ListMultiRegionAccessPoint:
listMultiRegionAccessPointsAsync in interface AWSS3ControlAsyncpublic Future<ListMultiRegionAccessPointsResult> listMultiRegionAccessPointsAsync(ListMultiRegionAccessPointsRequest request, AsyncHandler<ListMultiRegionAccessPointsRequest,ListMultiRegionAccessPointsResult> asyncHandler)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Returns a list of the Multi-Region Access Points currently associated with the specified Amazon Web Services account. Each call can return up to 100 Multi-Region Access Points, the maximum number of Multi-Region Access Points that can be associated with a single account.
This action will always be routed to the US West (Oregon) Region. For more information about the restrictions around working with Multi-Region Access Points, see Multi-Region Access Point restrictions and limitations in the Amazon S3 User Guide.
The following actions are related to ListMultiRegionAccessPoint:
listMultiRegionAccessPointsAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<ListRegionalBucketsResult> listRegionalBucketsAsync(ListRegionalBucketsRequest request)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Returns a list of all Outposts buckets in an Outpost that are owned by the authenticated sender of the request. For more information, see Using Amazon S3 on Outposts in the Amazon S3 User Guide.
For an example of the request syntax for Amazon S3 on Outposts that uses the S3 on Outposts endpoint hostname
prefix and x-amz-outpost-id in your request, see the Examples section.
listRegionalBucketsAsync in interface AWSS3ControlAsyncpublic Future<ListRegionalBucketsResult> listRegionalBucketsAsync(ListRegionalBucketsRequest request, AsyncHandler<ListRegionalBucketsRequest,ListRegionalBucketsResult> asyncHandler)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Returns a list of all Outposts buckets in an Outpost that are owned by the authenticated sender of the request. For more information, see Using Amazon S3 on Outposts in the Amazon S3 User Guide.
For an example of the request syntax for Amazon S3 on Outposts that uses the S3 on Outposts endpoint hostname
prefix and x-amz-outpost-id in your request, see the Examples section.
listRegionalBucketsAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<ListStorageLensConfigurationsResult> listStorageLensConfigurationsAsync(ListStorageLensConfigurationsRequest request)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Gets a list of Amazon S3 Storage Lens configurations. For more information about S3 Storage Lens, see Assessing your storage activity and usage with Amazon S3 Storage Lens in the Amazon S3 User Guide.
To use this action, you must have permission to perform the s3:ListStorageLensConfigurations action.
For more information, see Setting permissions to
use Amazon S3 Storage Lens in the Amazon S3 User Guide.
listStorageLensConfigurationsAsync in interface AWSS3ControlAsyncpublic Future<ListStorageLensConfigurationsResult> listStorageLensConfigurationsAsync(ListStorageLensConfigurationsRequest request, AsyncHandler<ListStorageLensConfigurationsRequest,ListStorageLensConfigurationsResult> asyncHandler)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Gets a list of Amazon S3 Storage Lens configurations. For more information about S3 Storage Lens, see Assessing your storage activity and usage with Amazon S3 Storage Lens in the Amazon S3 User Guide.
To use this action, you must have permission to perform the s3:ListStorageLensConfigurations action.
For more information, see Setting permissions to
use Amazon S3 Storage Lens in the Amazon S3 User Guide.
listStorageLensConfigurationsAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<ListStorageLensGroupsResult> listStorageLensGroupsAsync(ListStorageLensGroupsRequest request)
AWSS3ControlAsyncLists all the Storage Lens groups in the specified home Region.
To use this operation, you must have the permission to perform the s3:ListStorageLensGroups action.
For more information about the required Storage Lens Groups permissions, see Setting account permissions to use S3 Storage Lens groups.
For information about Storage Lens groups errors, see List of Amazon S3 Storage Lens error codes.
listStorageLensGroupsAsync in interface AWSS3ControlAsyncpublic Future<ListStorageLensGroupsResult> listStorageLensGroupsAsync(ListStorageLensGroupsRequest request, AsyncHandler<ListStorageLensGroupsRequest,ListStorageLensGroupsResult> asyncHandler)
AWSS3ControlAsyncLists all the Storage Lens groups in the specified home Region.
To use this operation, you must have the permission to perform the s3:ListStorageLensGroups action.
For more information about the required Storage Lens Groups permissions, see Setting account permissions to use S3 Storage Lens groups.
For information about Storage Lens groups errors, see List of Amazon S3 Storage Lens error codes.
listStorageLensGroupsAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<ListTagsForResourceResult> listTagsForResourceAsync(ListTagsForResourceRequest request)
AWSS3ControlAsyncThis operation allows you to list all the Amazon Web Services resource tags for a specified resource. Each tag is a label consisting of a user-defined key and value. Tags can help you manage, identify, organize, search for, and filter resources.
You must have the s3:ListTagsForResource permission to use this operation.
This operation is only supported for S3 Storage Lens groups and for S3 Access Grants. The tagged resource can be an S3 Storage Lens group or S3 Access Grants instance, registered location, or grant.
For more information about the required Storage Lens Groups permissions, see Setting account permissions to use S3 Storage Lens groups.
For information about S3 Tagging errors, see List of Amazon S3 Tagging error codes.
listTagsForResourceAsync in interface AWSS3ControlAsyncpublic Future<ListTagsForResourceResult> listTagsForResourceAsync(ListTagsForResourceRequest request, AsyncHandler<ListTagsForResourceRequest,ListTagsForResourceResult> asyncHandler)
AWSS3ControlAsyncThis operation allows you to list all the Amazon Web Services resource tags for a specified resource. Each tag is a label consisting of a user-defined key and value. Tags can help you manage, identify, organize, search for, and filter resources.
You must have the s3:ListTagsForResource permission to use this operation.
This operation is only supported for S3 Storage Lens groups and for S3 Access Grants. The tagged resource can be an S3 Storage Lens group or S3 Access Grants instance, registered location, or grant.
For more information about the required Storage Lens Groups permissions, see Setting account permissions to use S3 Storage Lens groups.
For information about S3 Tagging errors, see List of Amazon S3 Tagging error codes.
listTagsForResourceAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<PutAccessGrantsInstanceResourcePolicyResult> putAccessGrantsInstanceResourcePolicyAsync(PutAccessGrantsInstanceResourcePolicyRequest request)
AWSS3ControlAsyncUpdates the resource policy of the S3 Access Grants instance.
You must have the s3:PutAccessGrantsInstanceResourcePolicy permission to use this operation.
putAccessGrantsInstanceResourcePolicyAsync in interface AWSS3ControlAsyncpublic Future<PutAccessGrantsInstanceResourcePolicyResult> putAccessGrantsInstanceResourcePolicyAsync(PutAccessGrantsInstanceResourcePolicyRequest request, AsyncHandler<PutAccessGrantsInstanceResourcePolicyRequest,PutAccessGrantsInstanceResourcePolicyResult> asyncHandler)
AWSS3ControlAsyncUpdates the resource policy of the S3 Access Grants instance.
You must have the s3:PutAccessGrantsInstanceResourcePolicy permission to use this operation.
putAccessGrantsInstanceResourcePolicyAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<PutAccessPointConfigurationForObjectLambdaResult> putAccessPointConfigurationForObjectLambdaAsync(PutAccessPointConfigurationForObjectLambdaRequest request)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Replaces configuration for an Object Lambda Access Point.
The following actions are related to PutAccessPointConfigurationForObjectLambda:
putAccessPointConfigurationForObjectLambdaAsync in interface AWSS3ControlAsyncpublic Future<PutAccessPointConfigurationForObjectLambdaResult> putAccessPointConfigurationForObjectLambdaAsync(PutAccessPointConfigurationForObjectLambdaRequest request, AsyncHandler<PutAccessPointConfigurationForObjectLambdaRequest,PutAccessPointConfigurationForObjectLambdaResult> asyncHandler)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Replaces configuration for an Object Lambda Access Point.
The following actions are related to PutAccessPointConfigurationForObjectLambda:
putAccessPointConfigurationForObjectLambdaAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<PutAccessPointPolicyResult> putAccessPointPolicyAsync(PutAccessPointPolicyRequest request)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Associates an access policy with the specified access point. Each access point can have only one policy, so a request made to this API replaces any existing policy associated with the specified access point.
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
The following actions are related to PutAccessPointPolicy:
putAccessPointPolicyAsync in interface AWSS3ControlAsyncpublic Future<PutAccessPointPolicyResult> putAccessPointPolicyAsync(PutAccessPointPolicyRequest request, AsyncHandler<PutAccessPointPolicyRequest,PutAccessPointPolicyResult> asyncHandler)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Associates an access policy with the specified access point. Each access point can have only one policy, so a request made to this API replaces any existing policy associated with the specified access point.
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
The following actions are related to PutAccessPointPolicy:
putAccessPointPolicyAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<PutAccessPointPolicyForObjectLambdaResult> putAccessPointPolicyForObjectLambdaAsync(PutAccessPointPolicyForObjectLambdaRequest request)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Creates or replaces resource policy for an Object Lambda Access Point. For an example policy, see Creating Object Lambda Access Points in the Amazon S3 User Guide.
The following actions are related to PutAccessPointPolicyForObjectLambda:
putAccessPointPolicyForObjectLambdaAsync in interface AWSS3ControlAsyncpublic Future<PutAccessPointPolicyForObjectLambdaResult> putAccessPointPolicyForObjectLambdaAsync(PutAccessPointPolicyForObjectLambdaRequest request, AsyncHandler<PutAccessPointPolicyForObjectLambdaRequest,PutAccessPointPolicyForObjectLambdaResult> asyncHandler)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Creates or replaces resource policy for an Object Lambda Access Point. For an example policy, see Creating Object Lambda Access Points in the Amazon S3 User Guide.
The following actions are related to PutAccessPointPolicyForObjectLambda:
putAccessPointPolicyForObjectLambdaAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<PutBucketLifecycleConfigurationResult> putBucketLifecycleConfigurationAsync(PutBucketLifecycleConfigurationRequest request)
AWSS3ControlAsyncThis action puts a lifecycle configuration to an Amazon S3 on Outposts bucket. To put a lifecycle configuration to an S3 bucket, see PutBucketLifecycleConfiguration in the Amazon S3 API Reference.
Creates a new lifecycle configuration for the S3 on Outposts bucket or replaces an existing lifecycle configuration. Outposts buckets only support lifecycle configurations that delete/expire objects after a certain period of time and abort incomplete multipart uploads.
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
The following actions are related to PutBucketLifecycleConfiguration:
putBucketLifecycleConfigurationAsync in interface AWSS3ControlAsyncpublic Future<PutBucketLifecycleConfigurationResult> putBucketLifecycleConfigurationAsync(PutBucketLifecycleConfigurationRequest request, AsyncHandler<PutBucketLifecycleConfigurationRequest,PutBucketLifecycleConfigurationResult> asyncHandler)
AWSS3ControlAsyncThis action puts a lifecycle configuration to an Amazon S3 on Outposts bucket. To put a lifecycle configuration to an S3 bucket, see PutBucketLifecycleConfiguration in the Amazon S3 API Reference.
Creates a new lifecycle configuration for the S3 on Outposts bucket or replaces an existing lifecycle configuration. Outposts buckets only support lifecycle configurations that delete/expire objects after a certain period of time and abort incomplete multipart uploads.
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
The following actions are related to PutBucketLifecycleConfiguration:
putBucketLifecycleConfigurationAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<PutBucketPolicyResult> putBucketPolicyAsync(PutBucketPolicyRequest request)
AWSS3ControlAsyncThis action puts a bucket policy to an Amazon S3 on Outposts bucket. To put a policy on an S3 bucket, see PutBucketPolicy in the Amazon S3 API Reference.
Applies an Amazon S3 bucket policy to an Outposts bucket. For more information, see Using Amazon S3 on Outposts in the Amazon S3 User Guide.
If you are using an identity other than the root user of the Amazon Web Services account that owns the Outposts
bucket, the calling identity must have the PutBucketPolicy permissions on the specified Outposts
bucket and belong to the bucket owner's account in order to use this action.
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 Amazon Web Services account that owns a bucket can always use this action, 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.
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
The following actions are related to PutBucketPolicy:
putBucketPolicyAsync in interface AWSS3ControlAsyncpublic Future<PutBucketPolicyResult> putBucketPolicyAsync(PutBucketPolicyRequest request, AsyncHandler<PutBucketPolicyRequest,PutBucketPolicyResult> asyncHandler)
AWSS3ControlAsyncThis action puts a bucket policy to an Amazon S3 on Outposts bucket. To put a policy on an S3 bucket, see PutBucketPolicy in the Amazon S3 API Reference.
Applies an Amazon S3 bucket policy to an Outposts bucket. For more information, see Using Amazon S3 on Outposts in the Amazon S3 User Guide.
If you are using an identity other than the root user of the Amazon Web Services account that owns the Outposts
bucket, the calling identity must have the PutBucketPolicy permissions on the specified Outposts
bucket and belong to the bucket owner's account in order to use this action.
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 Amazon Web Services account that owns a bucket can always use this action, 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.
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
The following actions are related to PutBucketPolicy:
putBucketPolicyAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<PutBucketReplicationResult> putBucketReplicationAsync(PutBucketReplicationRequest request)
AWSS3ControlAsyncThis action creates an Amazon S3 on Outposts bucket's replication configuration. To create an S3 bucket's replication configuration, see PutBucketReplication in the Amazon S3 API Reference.
Creates a replication configuration or replaces an existing one. For information about S3 replication on Outposts configuration, see Replicating objects for S3 on Outposts in the Amazon S3 User Guide.
It can take a while to propagate PUT or DELETE requests for a replication configuration
to all S3 on Outposts systems. Therefore, the replication configuration that's returned by a GET
request soon after a PUT or DELETE request might return a more recent result than
what's on the Outpost. If an Outpost is offline, the delay in updating the replication configuration on that
Outpost can be significant.
Specify the replication configuration in the request body. In the replication configuration, you provide the following information:
The name of the destination bucket or buckets where you want S3 on Outposts to replicate objects
The Identity and Access Management (IAM) role that S3 on Outposts can assume to replicate objects on your behalf
Other relevant information, such as replication rules
A replication configuration must include at least one rule and can contain a maximum of 100. Each rule identifies a subset of objects to replicate by filtering the objects in the source Outposts bucket. To choose additional subsets of objects to replicate, add a rule for each subset.
To specify a subset of the objects in the source Outposts 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.
Using PutBucketReplication on Outposts requires that both the source and destination buckets must
have versioning enabled. For information about enabling versioning on a bucket, see Managing S3
Versioning for your S3 on Outposts bucket.
For information about S3 on Outposts replication failure reasons, see Replication failure reasons in the Amazon S3 User Guide.
Handling Replication of Encrypted Objects
Outposts buckets are encrypted at all times. All the objects in the source Outposts bucket are encrypted and can be replicated. Also, all the replicas in the destination Outposts bucket are encrypted with the same encryption key as the objects in the source Outposts bucket.
Permissions
To create a PutBucketReplication request, you must have
s3-outposts:PutReplicationConfiguration permissions for the bucket. The Outposts bucket owner has
this permission by default and can grant it to others. For more information about permissions, see Setting up IAM with S3 on
Outposts and Managing access to S3 on
Outposts buckets.
To perform this operation, the user or role must also have the iam:CreateRole and
iam:PassRole permissions. For more information, see Granting a user permissions to
pass a role to an Amazon Web Services service.
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
The following operations are related to PutBucketReplication:
putBucketReplicationAsync in interface AWSS3ControlAsyncpublic Future<PutBucketReplicationResult> putBucketReplicationAsync(PutBucketReplicationRequest request, AsyncHandler<PutBucketReplicationRequest,PutBucketReplicationResult> asyncHandler)
AWSS3ControlAsyncThis action creates an Amazon S3 on Outposts bucket's replication configuration. To create an S3 bucket's replication configuration, see PutBucketReplication in the Amazon S3 API Reference.
Creates a replication configuration or replaces an existing one. For information about S3 replication on Outposts configuration, see Replicating objects for S3 on Outposts in the Amazon S3 User Guide.
It can take a while to propagate PUT or DELETE requests for a replication configuration
to all S3 on Outposts systems. Therefore, the replication configuration that's returned by a GET
request soon after a PUT or DELETE request might return a more recent result than
what's on the Outpost. If an Outpost is offline, the delay in updating the replication configuration on that
Outpost can be significant.
Specify the replication configuration in the request body. In the replication configuration, you provide the following information:
The name of the destination bucket or buckets where you want S3 on Outposts to replicate objects
The Identity and Access Management (IAM) role that S3 on Outposts can assume to replicate objects on your behalf
Other relevant information, such as replication rules
A replication configuration must include at least one rule and can contain a maximum of 100. Each rule identifies a subset of objects to replicate by filtering the objects in the source Outposts bucket. To choose additional subsets of objects to replicate, add a rule for each subset.
To specify a subset of the objects in the source Outposts 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.
Using PutBucketReplication on Outposts requires that both the source and destination buckets must
have versioning enabled. For information about enabling versioning on a bucket, see Managing S3
Versioning for your S3 on Outposts bucket.
For information about S3 on Outposts replication failure reasons, see Replication failure reasons in the Amazon S3 User Guide.
Handling Replication of Encrypted Objects
Outposts buckets are encrypted at all times. All the objects in the source Outposts bucket are encrypted and can be replicated. Also, all the replicas in the destination Outposts bucket are encrypted with the same encryption key as the objects in the source Outposts bucket.
Permissions
To create a PutBucketReplication request, you must have
s3-outposts:PutReplicationConfiguration permissions for the bucket. The Outposts bucket owner has
this permission by default and can grant it to others. For more information about permissions, see Setting up IAM with S3 on
Outposts and Managing access to S3 on
Outposts buckets.
To perform this operation, the user or role must also have the iam:CreateRole and
iam:PassRole permissions. For more information, see Granting a user permissions to
pass a role to an Amazon Web Services service.
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
The following operations are related to PutBucketReplication:
putBucketReplicationAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<PutBucketTaggingResult> putBucketTaggingAsync(PutBucketTaggingRequest request)
AWSS3ControlAsyncThis action puts tags on an Amazon S3 on Outposts bucket. To put tags on an S3 bucket, see PutBucketTagging in the Amazon S3 API Reference.
Sets the tags for an S3 on Outposts bucket. For more information, see Using Amazon S3 on Outposts in the Amazon S3 User Guide.
Use tags to organize your Amazon Web Services bill to reflect your own cost structure. To do this, sign up to get your Amazon Web Services 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 action, you must have permissions to perform the s3-outposts:PutBucketTagging action.
The Outposts 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 Amazon Web Services-Generated Cost Allocation Tag Restrictions.
Error code: MalformedXMLError
Description: The XML provided does not match the schema.
Error code: OperationAbortedError
Description: A conflicting conditional action is currently in progress against this resource. Try again.
Error code: InternalError
Description: The service was unable to apply the provided tag to the bucket.
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
The following actions are related to PutBucketTagging:
putBucketTaggingAsync in interface AWSS3ControlAsyncpublic Future<PutBucketTaggingResult> putBucketTaggingAsync(PutBucketTaggingRequest request, AsyncHandler<PutBucketTaggingRequest,PutBucketTaggingResult> asyncHandler)
AWSS3ControlAsyncThis action puts tags on an Amazon S3 on Outposts bucket. To put tags on an S3 bucket, see PutBucketTagging in the Amazon S3 API Reference.
Sets the tags for an S3 on Outposts bucket. For more information, see Using Amazon S3 on Outposts in the Amazon S3 User Guide.
Use tags to organize your Amazon Web Services bill to reflect your own cost structure. To do this, sign up to get your Amazon Web Services 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 action, you must have permissions to perform the s3-outposts:PutBucketTagging action.
The Outposts 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 Amazon Web Services-Generated Cost Allocation Tag Restrictions.
Error code: MalformedXMLError
Description: The XML provided does not match the schema.
Error code: OperationAbortedError
Description: A conflicting conditional action is currently in progress against this resource. Try again.
Error code: InternalError
Description: The service was unable to apply the provided tag to the bucket.
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
The following actions are related to PutBucketTagging:
putBucketTaggingAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<PutBucketVersioningResult> putBucketVersioningAsync(PutBucketVersioningRequest request)
AWSS3ControlAsyncThis operation sets the versioning state for S3 on Outposts buckets only. To set the versioning state for an S3 bucket, see PutBucketVersioning in the Amazon S3 API Reference.
Sets the versioning state for an S3 on Outposts bucket. With S3 Versioning, you can save multiple distinct copies of your objects and recover from unintended user actions and application failures.
You can set the versioning state to one of the following:
Enabled - Enables versioning for the objects in the bucket. All objects added to the bucket receive a unique version ID.
Suspended - Suspends versioning for the objects in the bucket. All objects added to the bucket receive the
version ID null.
If you've never set versioning on your bucket, it has no versioning state. In that case, a GetBucketVersioning request does not return a versioning state value.
When you enable S3 Versioning, for each object in your bucket, you have a current version and zero or more noncurrent versions. You can configure your bucket S3 Lifecycle rules to expire noncurrent versions after a specified time period. For more information, see Creating and managing a lifecycle configuration for your S3 on Outposts bucket in the Amazon S3 User Guide.
If you have an object expiration lifecycle configuration 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 configuration will manage the deletes of the noncurrent object versions in the version-enabled bucket. For more information, see Versioning in the Amazon S3 User Guide.
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
The following operations are related to PutBucketVersioning for S3 on Outposts.
putBucketVersioningAsync in interface AWSS3ControlAsyncpublic Future<PutBucketVersioningResult> putBucketVersioningAsync(PutBucketVersioningRequest request, AsyncHandler<PutBucketVersioningRequest,PutBucketVersioningResult> asyncHandler)
AWSS3ControlAsyncThis operation sets the versioning state for S3 on Outposts buckets only. To set the versioning state for an S3 bucket, see PutBucketVersioning in the Amazon S3 API Reference.
Sets the versioning state for an S3 on Outposts bucket. With S3 Versioning, you can save multiple distinct copies of your objects and recover from unintended user actions and application failures.
You can set the versioning state to one of the following:
Enabled - Enables versioning for the objects in the bucket. All objects added to the bucket receive a unique version ID.
Suspended - Suspends versioning for the objects in the bucket. All objects added to the bucket receive the
version ID null.
If you've never set versioning on your bucket, it has no versioning state. In that case, a GetBucketVersioning request does not return a versioning state value.
When you enable S3 Versioning, for each object in your bucket, you have a current version and zero or more noncurrent versions. You can configure your bucket S3 Lifecycle rules to expire noncurrent versions after a specified time period. For more information, see Creating and managing a lifecycle configuration for your S3 on Outposts bucket in the Amazon S3 User Guide.
If you have an object expiration lifecycle configuration 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 configuration will manage the deletes of the noncurrent object versions in the version-enabled bucket. For more information, see Versioning in the Amazon S3 User Guide.
All Amazon S3 on Outposts REST API requests for this action require an additional parameter of
x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint
hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on
Outposts that uses the S3 on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by
using the access point ARN, see the Examples section.
The following operations are related to PutBucketVersioning for S3 on Outposts.
putBucketVersioningAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<PutJobTaggingResult> putJobTaggingAsync(PutJobTaggingRequest request)
AWSS3ControlAsyncSets the supplied tag-set on an S3 Batch Operations job.
A tag is a key-value pair. You can associate S3 Batch Operations tags with any job by sending a PUT request against the tagging subresource that is associated with the job. To modify the existing tag set, you can either replace the existing tag set entirely, or make changes within the existing tag set by retrieving the existing tag set using GetJobTagging, modify that tag set, and use this operation to replace the tag set with the one you modified. For more information, see Controlling access and labeling jobs using tags in the Amazon S3 User Guide.
If you send this request with an empty tag set, Amazon S3 deletes the existing tag set on the Batch Operations job. If you use this method, you are charged for a Tier 1 Request (PUT). For more information, see Amazon S3 pricing.
For deleting existing tags for your Batch Operations job, a DeleteJobTagging request is preferred because it achieves the same result without incurring charges.
A few things to consider about using tags:
Amazon S3 limits the maximum number of tags to 50 tags per job.
You can associate up to 50 tags with a job as long as they have unique tag keys.
A tag key can be up to 128 Unicode characters in length, and tag values can be up to 256 Unicode characters in length.
The key and values are case sensitive.
For tagging-related restrictions related to characters and encodings, see User-Defined Tag Restrictions in the Billing and Cost Management User Guide.
To use the PutJobTagging operation, you must have permission to perform the
s3:PutJobTagging action.
Related actions include:
putJobTaggingAsync in interface AWSS3ControlAsyncpublic Future<PutJobTaggingResult> putJobTaggingAsync(PutJobTaggingRequest request, AsyncHandler<PutJobTaggingRequest,PutJobTaggingResult> asyncHandler)
AWSS3ControlAsyncSets the supplied tag-set on an S3 Batch Operations job.
A tag is a key-value pair. You can associate S3 Batch Operations tags with any job by sending a PUT request against the tagging subresource that is associated with the job. To modify the existing tag set, you can either replace the existing tag set entirely, or make changes within the existing tag set by retrieving the existing tag set using GetJobTagging, modify that tag set, and use this operation to replace the tag set with the one you modified. For more information, see Controlling access and labeling jobs using tags in the Amazon S3 User Guide.
If you send this request with an empty tag set, Amazon S3 deletes the existing tag set on the Batch Operations job. If you use this method, you are charged for a Tier 1 Request (PUT). For more information, see Amazon S3 pricing.
For deleting existing tags for your Batch Operations job, a DeleteJobTagging request is preferred because it achieves the same result without incurring charges.
A few things to consider about using tags:
Amazon S3 limits the maximum number of tags to 50 tags per job.
You can associate up to 50 tags with a job as long as they have unique tag keys.
A tag key can be up to 128 Unicode characters in length, and tag values can be up to 256 Unicode characters in length.
The key and values are case sensitive.
For tagging-related restrictions related to characters and encodings, see User-Defined Tag Restrictions in the Billing and Cost Management User Guide.
To use the PutJobTagging operation, you must have permission to perform the
s3:PutJobTagging action.
Related actions include:
putJobTaggingAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<PutMultiRegionAccessPointPolicyResult> putMultiRegionAccessPointPolicyAsync(PutMultiRegionAccessPointPolicyRequest request)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Associates an access control policy with the specified Multi-Region Access Point. Each Multi-Region Access Point can have only one policy, so a request made to this action replaces any existing policy that is associated with the specified Multi-Region Access Point.
This action will always be routed to the US West (Oregon) Region. For more information about the restrictions around working with Multi-Region Access Points, see Multi-Region Access Point restrictions and limitations in the Amazon S3 User Guide.
The following actions are related to PutMultiRegionAccessPointPolicy:
putMultiRegionAccessPointPolicyAsync in interface AWSS3ControlAsyncpublic Future<PutMultiRegionAccessPointPolicyResult> putMultiRegionAccessPointPolicyAsync(PutMultiRegionAccessPointPolicyRequest request, AsyncHandler<PutMultiRegionAccessPointPolicyRequest,PutMultiRegionAccessPointPolicyResult> asyncHandler)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Associates an access control policy with the specified Multi-Region Access Point. Each Multi-Region Access Point can have only one policy, so a request made to this action replaces any existing policy that is associated with the specified Multi-Region Access Point.
This action will always be routed to the US West (Oregon) Region. For more information about the restrictions around working with Multi-Region Access Points, see Multi-Region Access Point restrictions and limitations in the Amazon S3 User Guide.
The following actions are related to PutMultiRegionAccessPointPolicy:
putMultiRegionAccessPointPolicyAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<PutPublicAccessBlockResult> putPublicAccessBlockAsync(PutPublicAccessBlockRequest request)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Creates or modifies the PublicAccessBlock configuration for an Amazon Web Services account. For this
operation, users must have the s3:PutAccountPublicAccessBlock permission. For more information, see
Using Amazon
S3 block public access.
Related actions include:
putPublicAccessBlockAsync in interface AWSS3ControlAsyncpublic Future<PutPublicAccessBlockResult> putPublicAccessBlockAsync(PutPublicAccessBlockRequest request, AsyncHandler<PutPublicAccessBlockRequest,PutPublicAccessBlockResult> asyncHandler)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Creates or modifies the PublicAccessBlock configuration for an Amazon Web Services account. For this
operation, users must have the s3:PutAccountPublicAccessBlock permission. For more information, see
Using Amazon
S3 block public access.
Related actions include:
putPublicAccessBlockAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<PutStorageLensConfigurationResult> putStorageLensConfigurationAsync(PutStorageLensConfigurationRequest request)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Puts an Amazon S3 Storage Lens configuration. For more information about S3 Storage Lens, see Working with Amazon S3 Storage Lens in the Amazon S3 User Guide. For a complete list of S3 Storage Lens metrics, see S3 Storage Lens metrics glossary in the Amazon S3 User Guide.
To use this action, you must have permission to perform the s3:PutStorageLensConfiguration action.
For more information, see Setting permissions to
use Amazon S3 Storage Lens in the Amazon S3 User Guide.
putStorageLensConfigurationAsync in interface AWSS3ControlAsyncpublic Future<PutStorageLensConfigurationResult> putStorageLensConfigurationAsync(PutStorageLensConfigurationRequest request, AsyncHandler<PutStorageLensConfigurationRequest,PutStorageLensConfigurationResult> asyncHandler)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Puts an Amazon S3 Storage Lens configuration. For more information about S3 Storage Lens, see Working with Amazon S3 Storage Lens in the Amazon S3 User Guide. For a complete list of S3 Storage Lens metrics, see S3 Storage Lens metrics glossary in the Amazon S3 User Guide.
To use this action, you must have permission to perform the s3:PutStorageLensConfiguration action.
For more information, see Setting permissions to
use Amazon S3 Storage Lens in the Amazon S3 User Guide.
putStorageLensConfigurationAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<PutStorageLensConfigurationTaggingResult> putStorageLensConfigurationTaggingAsync(PutStorageLensConfigurationTaggingRequest request)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Put or replace tags on an existing Amazon S3 Storage Lens configuration. For more information about S3 Storage Lens, see Assessing your storage activity and usage with Amazon S3 Storage Lens in the Amazon S3 User Guide.
To use this action, you must have permission to perform the s3:PutStorageLensConfigurationTagging
action. For more information, see Setting permissions to
use Amazon S3 Storage Lens in the Amazon S3 User Guide.
putStorageLensConfigurationTaggingAsync in interface AWSS3ControlAsyncpublic Future<PutStorageLensConfigurationTaggingResult> putStorageLensConfigurationTaggingAsync(PutStorageLensConfigurationTaggingRequest request, AsyncHandler<PutStorageLensConfigurationTaggingRequest,PutStorageLensConfigurationTaggingResult> asyncHandler)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Put or replace tags on an existing Amazon S3 Storage Lens configuration. For more information about S3 Storage Lens, see Assessing your storage activity and usage with Amazon S3 Storage Lens in the Amazon S3 User Guide.
To use this action, you must have permission to perform the s3:PutStorageLensConfigurationTagging
action. For more information, see Setting permissions to
use Amazon S3 Storage Lens in the Amazon S3 User Guide.
putStorageLensConfigurationTaggingAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<SubmitMultiRegionAccessPointRoutesResult> submitMultiRegionAccessPointRoutesAsync(SubmitMultiRegionAccessPointRoutesRequest request)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Submits an updated route configuration for a Multi-Region Access Point. This API operation updates the routing
status for the specified Regions from active to passive, or from passive to active. A value of 0
indicates a passive status, which means that traffic won't be routed to the specified Region. A value of
100 indicates an active status, which means that traffic will be routed to the specified Region. At
least one Region must be active at all times.
When the routing configuration is changed, any in-progress operations (uploads, copies, deletes, and so on) to formerly active Regions will continue to run to their final completion state (success or failure). The routing configurations of any Regions that aren’t specified remain unchanged.
Updated routing configurations might not be immediately applied. It can take up to 2 minutes for your changes to take effect.
To submit routing control changes and failover requests, use the Amazon S3 failover control infrastructure endpoints in these five Amazon Web Services Regions:
us-east-1
us-west-2
ap-southeast-2
ap-northeast-1
eu-west-1
submitMultiRegionAccessPointRoutesAsync in interface AWSS3ControlAsyncpublic Future<SubmitMultiRegionAccessPointRoutesResult> submitMultiRegionAccessPointRoutesAsync(SubmitMultiRegionAccessPointRoutesRequest request, AsyncHandler<SubmitMultiRegionAccessPointRoutesRequest,SubmitMultiRegionAccessPointRoutesResult> asyncHandler)
AWSS3ControlAsyncThis operation is not supported by directory buckets.
Submits an updated route configuration for a Multi-Region Access Point. This API operation updates the routing
status for the specified Regions from active to passive, or from passive to active. A value of 0
indicates a passive status, which means that traffic won't be routed to the specified Region. A value of
100 indicates an active status, which means that traffic will be routed to the specified Region. At
least one Region must be active at all times.
When the routing configuration is changed, any in-progress operations (uploads, copies, deletes, and so on) to formerly active Regions will continue to run to their final completion state (success or failure). The routing configurations of any Regions that aren’t specified remain unchanged.
Updated routing configurations might not be immediately applied. It can take up to 2 minutes for your changes to take effect.
To submit routing control changes and failover requests, use the Amazon S3 failover control infrastructure endpoints in these five Amazon Web Services Regions:
us-east-1
us-west-2
ap-southeast-2
ap-northeast-1
eu-west-1
submitMultiRegionAccessPointRoutesAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<TagResourceResult> tagResourceAsync(TagResourceRequest request)
AWSS3ControlAsyncCreates a new Amazon Web Services resource tag or updates an existing resource tag. Each tag is a label consisting of a user-defined key and value. Tags can help you manage, identify, organize, search for, and filter resources. You can add up to 50 Amazon Web Services resource tags for each S3 resource.
This operation is only supported for S3 Storage Lens groups and for S3 Access Grants. The tagged resource can be an S3 Storage Lens group or S3 Access Grants instance, registered location, or grant.
You must have the s3:TagResource permission to use this operation.
For more information about the required Storage Lens Groups permissions, see Setting account permissions to use S3 Storage Lens groups.
For information about S3 Tagging errors, see List of Amazon S3 Tagging error codes.
tagResourceAsync in interface AWSS3ControlAsyncpublic Future<TagResourceResult> tagResourceAsync(TagResourceRequest request, AsyncHandler<TagResourceRequest,TagResourceResult> asyncHandler)
AWSS3ControlAsyncCreates a new Amazon Web Services resource tag or updates an existing resource tag. Each tag is a label consisting of a user-defined key and value. Tags can help you manage, identify, organize, search for, and filter resources. You can add up to 50 Amazon Web Services resource tags for each S3 resource.
This operation is only supported for S3 Storage Lens groups and for S3 Access Grants. The tagged resource can be an S3 Storage Lens group or S3 Access Grants instance, registered location, or grant.
You must have the s3:TagResource permission to use this operation.
For more information about the required Storage Lens Groups permissions, see Setting account permissions to use S3 Storage Lens groups.
For information about S3 Tagging errors, see List of Amazon S3 Tagging error codes.
tagResourceAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<UntagResourceResult> untagResourceAsync(UntagResourceRequest request)
AWSS3ControlAsyncThis operation removes the specified Amazon Web Services resource tags from an S3 resource. Each tag is a label consisting of a user-defined key and value. Tags can help you manage, identify, organize, search for, and filter resources.
This operation is only supported for S3 Storage Lens groups and for S3 Access Grants. The tagged resource can be an S3 Storage Lens group or S3 Access Grants instance, registered location, or grant.
You must have the s3:UntagResource permission to use this operation.
For more information about the required Storage Lens Groups permissions, see Setting account permissions to use S3 Storage Lens groups.
For information about S3 Tagging errors, see List of Amazon S3 Tagging error codes.
untagResourceAsync in interface AWSS3ControlAsyncpublic Future<UntagResourceResult> untagResourceAsync(UntagResourceRequest request, AsyncHandler<UntagResourceRequest,UntagResourceResult> asyncHandler)
AWSS3ControlAsyncThis operation removes the specified Amazon Web Services resource tags from an S3 resource. Each tag is a label consisting of a user-defined key and value. Tags can help you manage, identify, organize, search for, and filter resources.
This operation is only supported for S3 Storage Lens groups and for S3 Access Grants. The tagged resource can be an S3 Storage Lens group or S3 Access Grants instance, registered location, or grant.
You must have the s3:UntagResource permission to use this operation.
For more information about the required Storage Lens Groups permissions, see Setting account permissions to use S3 Storage Lens groups.
For information about S3 Tagging errors, see List of Amazon S3 Tagging error codes.
untagResourceAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<UpdateAccessGrantsLocationResult> updateAccessGrantsLocationAsync(UpdateAccessGrantsLocationRequest request)
AWSS3ControlAsyncUpdates the IAM role of a registered location in your S3 Access Grants instance.
You must have the s3:UpdateAccessGrantsLocation permission to use this operation.
You must also have the following permission: iam:PassRole
updateAccessGrantsLocationAsync in interface AWSS3ControlAsyncpublic Future<UpdateAccessGrantsLocationResult> updateAccessGrantsLocationAsync(UpdateAccessGrantsLocationRequest request, AsyncHandler<UpdateAccessGrantsLocationRequest,UpdateAccessGrantsLocationResult> asyncHandler)
AWSS3ControlAsyncUpdates the IAM role of a registered location in your S3 Access Grants instance.
You must have the s3:UpdateAccessGrantsLocation permission to use this operation.
You must also have the following permission: iam:PassRole
updateAccessGrantsLocationAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<UpdateJobPriorityResult> updateJobPriorityAsync(UpdateJobPriorityRequest request)
AWSS3ControlAsyncUpdates an existing S3 Batch Operations job's priority. For more information, see S3 Batch Operations in the Amazon S3 User Guide.
To use the UpdateJobPriority operation, you must have permission to perform the
s3:UpdateJobPriority action.
Related actions include:
updateJobPriorityAsync in interface AWSS3ControlAsyncpublic Future<UpdateJobPriorityResult> updateJobPriorityAsync(UpdateJobPriorityRequest request, AsyncHandler<UpdateJobPriorityRequest,UpdateJobPriorityResult> asyncHandler)
AWSS3ControlAsyncUpdates an existing S3 Batch Operations job's priority. For more information, see S3 Batch Operations in the Amazon S3 User Guide.
To use the UpdateJobPriority operation, you must have permission to perform the
s3:UpdateJobPriority action.
Related actions include:
updateJobPriorityAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<UpdateJobStatusResult> updateJobStatusAsync(UpdateJobStatusRequest request)
AWSS3ControlAsyncUpdates the status for the specified job. Use this operation to confirm that you want to run a job or to cancel an existing job. For more information, see S3 Batch Operations in the Amazon S3 User Guide.
To use the UpdateJobStatus operation, you must have permission to perform the
s3:UpdateJobStatus action.
Related actions include:
updateJobStatusAsync in interface AWSS3ControlAsyncpublic Future<UpdateJobStatusResult> updateJobStatusAsync(UpdateJobStatusRequest request, AsyncHandler<UpdateJobStatusRequest,UpdateJobStatusResult> asyncHandler)
AWSS3ControlAsyncUpdates the status for the specified job. Use this operation to confirm that you want to run a job or to cancel an existing job. For more information, see S3 Batch Operations in the Amazon S3 User Guide.
To use the UpdateJobStatus operation, you must have permission to perform the
s3:UpdateJobStatus action.
Related actions include:
updateJobStatusAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.public Future<UpdateStorageLensGroupResult> updateStorageLensGroupAsync(UpdateStorageLensGroupRequest request)
AWSS3ControlAsyncUpdates the existing Storage Lens group.
To use this operation, you must have the permission to perform the s3:UpdateStorageLensGroup action.
For more information about the required Storage Lens Groups permissions, see Setting account permissions to use S3 Storage Lens groups.
For information about Storage Lens groups errors, see List of Amazon S3 Storage Lens error codes.
updateStorageLensGroupAsync in interface AWSS3ControlAsyncpublic Future<UpdateStorageLensGroupResult> updateStorageLensGroupAsync(UpdateStorageLensGroupRequest request, AsyncHandler<UpdateStorageLensGroupRequest,UpdateStorageLensGroupResult> asyncHandler)
AWSS3ControlAsyncUpdates the existing Storage Lens group.
To use this operation, you must have the permission to perform the s3:UpdateStorageLensGroup action.
For more information about the required Storage Lens Groups permissions, see Setting account permissions to use S3 Storage Lens groups.
For information about Storage Lens groups errors, see List of Amazon S3 Storage Lens error codes.
updateStorageLensGroupAsync in interface AWSS3ControlAsyncasyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.