Skip to contents

This operation is not supported for directory buckets

Source: R/s3_operations.R
s3_put_object_lock_configuration.Rd

This operation is not supported for directory buckets.

See https://www.paws-r-sdk.com/docs/s3_put_object_lock_configuration/ for full documentation.

Usage

s3_put_object_lock_configuration(
  Bucket,
  ObjectLockConfiguration = NULL,
  RequestPayer = NULL,
  Token = NULL,
  ContentMD5 = NULL,
  ChecksumAlgorithm = NULL,
  ExpectedBucketOwner = NULL
)

Arguments

Bucket

[required] The bucket whose Object Lock configuration you want to create or replace.

ObjectLockConfiguration

The Object Lock configuration that you want to apply to the specified bucket.

RequestPayer

Confirms 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.

Token

A token to allow Object Lock to be enabled for an existing bucket.

ContentMD5

The 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.

ChecksumAlgorithm

Indicates 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-checksum or x-amz-trailer header sent. Otherwise, Amazon S3 fails the request with the HTTP status code 400 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 ChecksumAlgorithm parameter.

ExpectedBucketOwner

The 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).