S3: Publically accessible buckets can be used without creds.
This commit is contained in:
parent
4acd28bf21
commit
5f0f063a7a
8 changed files with 115 additions and 61 deletions
|
@ -0,0 +1,10 @@
|
|||
[[!comment format=mdwn
|
||||
username="joey"
|
||||
subject="""comment 3"""
|
||||
date="2015-06-05T20:17:38Z"
|
||||
content="""
|
||||
The remote can indeed fallback when there are no creds.
|
||||
|
||||
Also, git-annex can set an ACL on files it uploads, if the remote is
|
||||
configured with public=yes, so no manual ACL setting will be needed.
|
||||
"""]]
|
|
@ -1,11 +0,0 @@
|
|||
[[!comment format=mdwn
|
||||
username="joey"
|
||||
subject="""comment 3"""
|
||||
date="2015-06-05T17:28:52Z"
|
||||
content="""
|
||||
Based on
|
||||
<http://docs.aws.amazon.com/AmazonS3/latest/dev/WebsiteEndpoints.html>
|
||||
and my testing, S3 does not default to allowing public access to buckets. So,
|
||||
this seems like something that it makes sense for the user to
|
||||
manually configure when setting up a s3 remote.
|
||||
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue