diff options
author | Joey Hess <joeyh@joeyh.name> | 2015-06-05 16:23:35 -0400 |
---|---|---|
committer | Joey Hess <joeyh@joeyh.name> | 2015-06-05 16:23:35 -0400 |
commit | bc5a042b5bfb1999f8450657d5b0721235fbb84c (patch) | |
tree | 3a1af4e743ad048045ca53a4a59d4eb8b6f3bd61 /doc/todo/credentials-less_access_to_s3 | |
parent | e9ab4e21fd215048e63f37d458e69f3f848ed5cb (diff) |
S3: Publically accessible buckets can be used without creds.
Diffstat (limited to 'doc/todo/credentials-less_access_to_s3')
2 files changed, 10 insertions, 11 deletions
diff --git a/doc/todo/credentials-less_access_to_s3/comment_3_26de94e8e3fefc9b47d1510bfb2dac9b._comment b/doc/todo/credentials-less_access_to_s3/comment_3_26de94e8e3fefc9b47d1510bfb2dac9b._comment new file mode 100644 index 000000000..8a9ff4db2 --- /dev/null +++ b/doc/todo/credentials-less_access_to_s3/comment_3_26de94e8e3fefc9b47d1510bfb2dac9b._comment @@ -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. +"""]] diff --git a/doc/todo/credentials-less_access_to_s3/comment_3_96c8bcb545578280dc02c00d82978f77._comment b/doc/todo/credentials-less_access_to_s3/comment_3_96c8bcb545578280dc02c00d82978f77._comment deleted file mode 100644 index 52802de2a..000000000 --- a/doc/todo/credentials-less_access_to_s3/comment_3_96c8bcb545578280dc02c00d82978f77._comment +++ /dev/null @@ -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. -"""]] |