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/tips/using_Amazon_S3.mdwn | |
| parent | e9ab4e21fd215048e63f37d458e69f3f848ed5cb (diff) | |
S3: Publically accessible buckets can be used without creds.
Diffstat (limited to 'doc/tips/using_Amazon_S3.mdwn')
| -rw-r--r-- | doc/tips/using_Amazon_S3.mdwn | 15 |
1 files changed, 8 insertions, 7 deletions
diff --git a/doc/tips/using_Amazon_S3.mdwn b/doc/tips/using_Amazon_S3.mdwn index d6f621786..85d5bc958 100644 --- a/doc/tips/using_Amazon_S3.mdwn +++ b/doc/tips/using_Amazon_S3.mdwn @@ -22,16 +22,17 @@ Next, create the S3 remote, and describe it. The configuration for the S3 remote is stored in git. So to make another repository use the same S3 remote is easy: - # cd /media/usb/annex + # export AWS_ACCESS_KEY_ID="08TJMT99S3511WOZEP91" + # export AWS_SECRET_ACCESS_KEY="s3kr1t" # git pull laptop # git annex enableremote cloud enableremote cloud (gpg) (checking bucket) ok -Now the remote can be used like any other remote. +Notice that to enable an existing S3 remote, you have to provide the Amazon +AWS credentials because they were not stored in the repository. (It is +possible to configure git-annex to do that, but not the default.) - # git annex copy my_cool_big_file --to cloud - copy my_cool_big_file (gpg) (checking cloud...) (to cloud...) ok - # git annex move video/hackity_hack_and_kaxxt.mov --to cloud - move video/hackity_hack_and_kaxxt.mov (checking cloud...) (to cloud...) ok +See [[public_Amazon_S3_remote]] for how to set up a Amazon S3 remote that +can be used by the public, without them needing AWS credentials. -See [[special_remotes/S3]] for details. +See [[special_remotes/S3]] for details about configuring S3 remotes. |