summaryrefslogtreecommitdiff
path: root/python/boto/README.boto
diff options
context:
space:
mode:
authorLarry Hajali <larryhaja[at]gmail[dot]com>2012-05-13 09:09:25 -0400
committerdsomero <xgizzmo@slackbuilds.org>2012-05-13 09:09:25 -0400
commitdf58a6966ae98a47f3ccfd2399daa91593c4fbc6 (patch)
treeb04983f7e7e7863d4f0386bbdb0dcf21468efed2 /python/boto/README.boto
parent5f16d5268af69fcdab8d3e08991502deafd7f431 (diff)
downloadslackbuilds-df58a6966ae98a47f3ccfd2399daa91593c4fbc6.tar.gz
python/boto: Added (Interface to Amazon Web Services)
Signed-off-by: dsomero <xgizzmo@slackbuilds.org>
Diffstat (limited to 'python/boto/README.boto')
-rw-r--r--python/boto/README.boto26
1 files changed, 26 insertions, 0 deletions
diff --git a/python/boto/README.boto b/python/boto/README.boto
new file mode 100644
index 0000000000..8eb3041c15
--- /dev/null
+++ b/python/boto/README.boto
@@ -0,0 +1,26 @@
+In order for boto to access an s3 resource it must be able to get the
+access key and secret key for an s3 account. The 3 ways that boto can
+obtain the keys are in the following order of precedence.
+
+1) Credentials passed into Connection class constructor
+2) Credentials specified by environment variables
+3) Credentials specified as options in a config file
+
+The easiest way for boto to read proper s3 credentials are from a
+global config file in /etc/boto.cfg or on a user basis in
+~/.boto.
+
+An example config file looks like the following:
+
+[Credentials]
+aws_access_key_id = <your access key>
+aws_secret_access_key = <your secret key>
+
+[Boto]
+debug = 0
+num_retries = 10
+
+proxy = myproxy.com
+proxy_port = 8080
+proxy_user = foo
+proxy_pass = bar