s3control_create_access_point: This operation is not supported by directory buckets
In paws.storage: 'Amazon Web Services' Storage Services

s3control_create_access_point

R Documentation

This operation is not supported by directory buckets

Description

This operation is not supported by directory buckets.

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

Usage

s3control_create_access_point(
  AccountId,
  Name,
  Bucket,
  VpcConfiguration = NULL,
  PublicAccessBlockConfiguration = NULL,
  BucketAccountId = NULL
)

Arguments

`AccountId`	[required] The Amazon Web Services account ID for the account that owns the specified access point.
`Name`	[required] The name you want to assign to this access point.
`Bucket`	[required] The name of the bucket that you want to associate this access point with. For using this parameter with Amazon S3 on Outposts with the REST API, you must specify the name and the x-amz-outpost-id as well. For using this parameter with S3 on Outposts with the Amazon Web Services SDK and CLI, you must specify the ARN of the bucket accessed in the format `⁠arn:aws:s3-outposts:<Region>:<account-id>:outpost/<outpost-id>/bucket/<my-bucket-name>⁠`. For example, to access the bucket `reports` through Outpost `my-outpost` owned by account `123456789012` in Region `us-west-2`, use the URL encoding of `arn:aws:s3-outposts:us-west-2:123456789012:outpost/my-outpost/bucket/reports`. The value must be URL encoded.
`VpcConfiguration`	If you include this field, Amazon S3 restricts access to this access point to requests from the specified virtual private cloud (VPC). This is required for creating an access point for Amazon S3 on Outposts buckets.
`PublicAccessBlockConfiguration`	The `PublicAccessBlock` configuration that you want to apply to the access point.
`BucketAccountId`	The Amazon Web Services account ID associated with the S3 bucket associated with this access point. For same account access point when your bucket and access point belong to the same account owner, the `BucketAccountId` is not required. For cross-account access point when your bucket and access point are not in the same account, the `BucketAccountId` is required.