· 8 years ago · Jan 05, 2018, 04:10 PM
1SYNOPSIS
2 s3put [-a/--access_key <access_key>] [-s/--secret_key <secret_key>]
3 -b/--bucket <bucket_name> [-c/--callback <num_cb>]
4 [-d/--debug <debug_level>] [-i/--ignore <ignore_dirs>]
5 [-n/--no_op] [-p/--prefix <prefix>] [-q/--quiet]
6 [-g/--grant grant] [-w/--no_overwrite] path
7
8 Where
9 access_key - Your AWS Access Key ID. If not supplied, boto will
10 use the value of the environment variable
11 AWS_ACCESS_KEY_ID
12 secret_key - Your AWS Secret Access Key. If not supplied, boto
13 will use the value of the environment variable
14 AWS_SECRET_ACCESS_KEY
15 bucket_name - The name of the S3 bucket the file(s) should be
16 copied to.
17 path - A path to a directory or file that represents the items
18 to be uploaded. If the path points to an individual file,
19 that file will be uploaded to the specified bucket. If the
20 path points to a directory, s3_it will recursively traverse
21 the directory and upload all files to the specified bucket.
22 debug_level - 0 means no debug output (default), 1 means normal
23 debug output from boto, and 2 means boto debug output
24 plus request/response output from httplib
25 ignore_dirs - a comma-separated list of directory names that will
26 be ignored and not uploaded to S3.
27 num_cb - The number of progress callbacks to display. The default
28 is zero which means no callbacks. If you supplied a value
29 of "-c 10" for example, the progress callback would be
30 called 10 times for each file transferred.
31 prefix - A file path prefix that will be stripped from the full
32 path of the file when determining the key name in S3.
33 For example, if the full path of a file is:
34 /home/foo/bar/fie.baz
35 and the prefix is specified as "-p /home/foo/" the
36 resulting key name in S3 will be:
37 /bar/fie.baz
38 The prefix must end in a trailing separator and if it
39 does not then one will be added.
40 grant - A canned ACL policy that will be granted on each file
41 transferred to S3. The value of provided must be one
42 of the "canned" ACL policies supported by S3:
43 private|public-read|public-read-write|authenticated-read
44 no_overwrite - No files will be overwritten on S3, if the file/key
45 exists on s3 it will be kept. This is useful for
46 resuming interrupted transfers. Note this is not a
47 sync, even if the file has been updated locally if
48 the key exists on s3 the file on s3 will not be
49 updated.
50
51 If the -n option is provided, no files will be transferred to S3 but
52 informational messages will be printed about what would happen.