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
{{ message }}
This repository was archived by the owner on Feb 26, 2025. It is now read-only.
Any bucket with a DNS-compatible name can be referenced as follows: http://[BucketName].s3.amazonaws.com/[Filename], for example, http://images.johnsmith.net.s3.amazonaws.com/mydog.jpg. By using CNAME, you can map images.johnsmith.net to an Amazon S3 host name so that the previous URL could become http://images.johnsmith.net/mydog.jpg.
The above URI does not work as there is NOT a bucket name after the endpoint. I have tried the following as well with no success.
There is a call to ListAllMyBuckets within the S3FS library that forces permissions to be able to ListAllMyBuckets to the following resource "s3.amazonaws.com" in the above example. I would not like to have to do that but allow the use of the original sample at the top
s3://[email protected]/folder/folder/ { The bucket is in the endpoint..virtual hosting}
This would then only require the AWS user to have permissions to ListAllMyBuckets to the resource which is "my.bucket.name.com"
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Having an issue where the file path does not have a bucket name in it as we would like to use the following:
s3://[email protected]/folder/folder/
where my.bucket.name.com CNAME is my.bucket.name.com.s3.amazonaws.com
The documentation on this feature is here:
http://docs.aws.amazon.com/AmazonS3/latest/dev/VirtualHosting.html
Any bucket with a DNS-compatible name can be referenced as follows: http://[BucketName].s3.amazonaws.com/[Filename], for example, http://images.johnsmith.net.s3.amazonaws.com/mydog.jpg. By using CNAME, you can map images.johnsmith.net to an Amazon S3 host name so that the previous URL could become http://images.johnsmith.net/mydog.jpg.
The above URI does not work as there is NOT a bucket name after the endpoint. I have tried the following as well with no success.
s3://[email protected]//folder/folder/ {empty bucket}
The following will work:
s3://[email protected]/my.bucket.name.com/folder/folder/
There is a call to ListAllMyBuckets within the S3FS library that forces permissions to be able to ListAllMyBuckets to the following resource "s3.amazonaws.com" in the above example. I would not like to have to do that but allow the use of the original sample at the top
s3://[email protected]/folder/folder/ { The bucket is in the endpoint..virtual hosting}
This would then only require the AWS user to have permissions to ListAllMyBuckets to the resource which is "my.bucket.name.com"
The text was updated successfully, but these errors were encountered: