-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
S3Path
: support for using access points
#228
Comments
a workaround is to use a bucket-style alias for the access point |
S3Path
: add support for using access pointsS3Path
: add support for using access point ARNs?
S3Path
: add support for using access point ARNs?S3Path
: support for using access points
If we decide not to support the access point ARN and instead require the use of a bucket-style alias, then i think this issue can be resolved by just adding documentation about using ARNs with |
Based upon the documentation I've read so far I think supporting access points would use the julia> S3Path("s3://arn:aws:s3:us-west-2:123456789012:accesspoint/test", "object")
p"s3://arn:aws:s3:us-west-2:123456789012:accesspoint/test/object"
julia> S3Path("s3://arn:aws:s3:us-west-2:123456789012:accesspoint/test/object")
p"s3://arn/test/object" I think to better support access points we should error when an ARN is provided via the URI constructor and not display an access point in the URI format as it cannot be parsed that way. I'm also reminded of #226 here as this is another example of S3 paths being different from a file system path |
i would like to start accessing an S3 bucket via an "access point"
e.g. instead of
s3://bucket/object
usearn:aws:s3:us-west-2:123456789012:accesspoint/test/object
My code currently uses
S3Paths
, so i hoped it'd be as simple as changingS3Path("s3://bucket/object")
->S3Path("s3://arn:aws:s3:us-west-2:123456789012:accesspoint/test/object")
, but it seemsS3Path
isn't able to handle access points being used in place of buckets; currently it mangles the "bucket" name:The text was updated successfully, but these errors were encountered: