2022/09/21 - AWS S3 Control - 2 new api methods
Changes S3 on Outposts launches support for object versioning for Outposts buckets. With S3 Versioning, you can preserve, retrieve, and restore every version of every object stored in your buckets. You can recover from both unintended user actions and application failures.
Note
This operation sets the versioning state only for S3 on Outposts buckets. 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 versioning, you can save multiple distinct copies of your data 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 policy in your non-versioned bucket and you want to maintain the same permanent delete behavior when you enable versioning, you must add a noncurrent expiration policy. The noncurrent expiration lifecycle policy will manage the deletes of the noncurrent object versions in the version-enabled bucket. 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.
See also: AWS API Documentation
Request Syntax
client.put_bucket_versioning( AccountId='string', Bucket='string', MFA='string', VersioningConfiguration={ 'MFADelete': 'Enabled'|'Disabled', 'Status': 'Enabled'|'Suspended' } )
string
[REQUIRED]
The Amazon Web Services account ID of the S3 on Outposts bucket.
string
[REQUIRED]
The S3 on Outposts bucket to set the versioning state for.
string
The concatenation of the authentication device's serial number, a space, and the value that is displayed on your authentication device.
dict
[REQUIRED]
The root-level tag for the VersioningConfiguration parameters.
MFADelete (string) --
Specifies whether MFA delete is enabled or disabled in the bucket versioning configuration for the S3 on Outposts bucket.
Status (string) --
Sets the versioning state of the S3 on Outposts bucket.
None
Note
This operation returns the versioning state only for S3 on Outposts buckets. 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 versioning, you can save multiple distinct copies of your data 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.
See also: AWS API Documentation
Request Syntax
client.get_bucket_versioning( AccountId='string', Bucket='string' )
string
[REQUIRED]
The Amazon Web Services account ID of the S3 on Outposts bucket.
string
[REQUIRED]
The S3 on Outposts bucket to return the versioning state for.
dict
Response Syntax
{ 'Status': 'Enabled'|'Suspended', 'MFADelete': 'Enabled'|'Disabled' }
Response Structure
(dict) --
Status (string) --
The versioning state of the S3 on Outposts bucket.
MFADelete (string) --
Specifies whether MFA delete is enabled in the bucket versioning configuration. This element is returned only if the bucket has been configured with MFA delete. If MFA delete has never been configured for the bucket, this element is not returned.