You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AWS S3 Access Points are unique hostnames attached to an S3 bucket, each with dedicated access policies. This allows large scale access control to be delegated to multiple APs, each dedicated to providing access to one user, rather than combining all access control in one large bucket policy. Larger scale users are increasingly using APs to simplify bucket access control.
S3 Access Points ARNs may be used by the AWS CLI and SDK in place of a bucket name; once an S3 AP is defined to a bucket mybucket, the following are equivalent:
Thanks for reporting this and congratulations on having raised our first feature request!
We have recently upgraded to AWS SDK v2 and are currently doing some follow up work in this regard. As we're also working on adding MinIO support, we will most-likely have to look into this. We'll need to investigate how this can be done. If you're interested in helping out and proposing a pull request, we would be more than happy to review it (together with our contacts from Amazon) and evaluate and merge the pull request.
Task Description
AWS S3 Access Points are unique hostnames attached to an S3 bucket, each with dedicated access policies. This allows large scale access control to be delegated to multiple APs, each dedicated to providing access to one user, rather than combining all access control in one large bucket policy. Larger scale users are increasingly using APs to simplify bucket access control.
S3 Access Points ARNs may be used by the AWS CLI and SDK in place of a bucket name; once an S3 AP is defined to a bucket
mybucket
, the following are equivalent:s3://mybucket/
s3://arn:aws:s3:<region>:<account-id>:accesspoint/<ap-name>/
Task Relationships
This task:
Help
The text was updated successfully, but these errors were encountered: