This operation is not supported for directory buckets¶
Description¶
This operation is not supported for directory buckets.
Places an Object Lock configuration on the specified bucket. The rule specified in the Object Lock configuration will be applied by default to every new object placed in the specified bucket. For more information, see Locking Objects.
- The
DefaultRetentionsettings require both a mode and a period. - The
DefaultRetentionperiod can be eitherDaysorYearsbut you must select one. You cannot specifyDaysandYearsat the same time. - You can enable Object Lock for new or existing buckets. For more information, see Configuring Object Lock.
You must URL encode any signed header values that contain spaces. For example, if your header value is my file.txt, containing two spaces after my, you must URL encode this value to my%20%20file.txt.
Usage¶
s3_put_object_lock_configuration(Bucket, ObjectLockConfiguration,
RequestPayer, Token, ContentMD5, ChecksumAlgorithm, ExpectedBucketOwner)
Arguments¶
-
Bucket[required] The bucket whose Object Lock configuration you want to create or replace.
-
ObjectLockConfigurationThe Object Lock configuration that you want to apply to the specified bucket.
-
RequestPayerConfirms that the requester knows that they will be charged for the request. Bucket owners need not specify this parameter in their requests. If either the source or destination S3 bucket has Requester Pays enabled, the requester will pay for the corresponding charges. For information about downloading objects from Requester Pays buckets, see Downloading Objects in Requester Pays Buckets in the Amazon S3 User Guide.
This functionality is not supported for directory buckets.
-
TokenA token to allow Object Lock to be enabled for an existing bucket.
-
ContentMD5The MD5 hash for the request body.
For requests made using the Amazon Web Services Command Line Interface (CLI) or Amazon Web Services SDKs, this field is calculated automatically.
-
ChecksumAlgorithmIndicates the algorithm used to create the checksum for the object when you use the SDK. This header will not provide any additional functionality if you don't use the SDK. When you send this header, there must be a corresponding
x-amz-checksumorx-amz-trailerheader sent. Otherwise, Amazon S3 fails the request with the HTTP status code400 Bad Request. For more information, see Checking object integrity in the Amazon S3 User Guide.If you provide an individual checksum, Amazon S3 ignores any provided
ChecksumAlgorithmparameter. -
ExpectedBucketOwnerThe account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code
403 Forbidden(access denied).
Value¶
A list with the following syntax:
Request syntax¶
svc$put_object_lock_configuration(
Bucket = "string",
ObjectLockConfiguration = list(
ObjectLockEnabled = "Enabled",
Rule = list(
DefaultRetention = list(
Mode = "GOVERNANCE"|"COMPLIANCE",
Days = 123,
Years = 123,
DefaultEventHold = list(
Days = 123,
Years = 123
)
)
)
),
RequestPayer = "requester",
Token = "string",
ContentMD5 = "string",
ChecksumAlgorithm = "CRC32"|"CRC32C"|"SHA1"|"SHA256"|"CRC64NVME"|"SHA512"|"MD5"|"XXHASH64"|"XXHASH3"|"XXHASH128",
ExpectedBucketOwner = "string"
)