           _____
 _   _ ___|___ /
| | | / __| |_ \
| |_| \__ \___) |
 \__,_|___/____/

us3 helps you to manage files on AWS S3 or S3 compatible API like Ceph or Cleversafe. Usefull with Continuous Integreation pipelines :)

Installation

pip install us3

For Docker check bottom

Usage

us3 (upload|download) [options] -s <src>
us3 delete [options] -s <src>

Options

-h --help                                   Show this screen.
--version                                   Show version.
-a <access> --access=<access>               Access key.
-x <secret> --secret=<secret>               Secret key.
-e <endpoint> --endpoint=<endpoint>         Host to connect to. Default
                                            is s3.amazonaws.com. You can check all AWS host/region on
                                            http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region
-i <is_secure> --is_secure=<is_secure>      Use secure connection (https)
                                            or not (http). Default is True.
-k <clg> --calling_format=<clg>             Choose how to call the S3 API.
                                            Allowed:
                                            - SubdomainCallingFormat (default)
                                            - VHostCallingFormat
                                            - OrdinaryCallingFormat
                                            - ProtocolIndependentOrdinaryCallingFormat.
-b <bucket> --bucket=<bucket>               Bucket name.
-s <src> --source=<src>                     File to download/upload.
-d <dest> --destination=<dest>               Destination folder path.
-c <config.yml> --config=<config.yml>       Config file path.

Thoses values are overrided by environment variables.

Config file

You could use a config file in YAML format to reduce options in CLI.

By default, us3 will look at /etc/default/us3.yaml or to the custom path with --config <pathtoconf>.

Thoses values are overrided by the CLI and environment variables.

Example:

$ cat /etc/default/us3.yaml
---
host:  mycustomhost
access: myaccesskey
secret: mysecurekey
calling_format: OrdinaryCallingFormat
is_secure: False

Environment variables

Environment variables had priority on config values and CLI values. To export a value, prepend variable name uppered with US3_.

Example:

export US3_HOST= myexporthost
export US3_ACCESS=myaccesskey
export US3_SECRET=mysecurekey

Docker

Image size ~70MB

docker pull ahmet2mir/us3

And use environment variables. By default, files are stored in /data

docker run --rm \
    -e "US3_ENDPOINT=s3-eu-west-1.amazonaws.com" \
    -e 'US3_BUCKET=xxxx' \
    -e 'US3_ACCESS=yyyy' \
    -e 'US3_SECRET=zzzz+' \
    -v /tmp/docker:/data \
    ahmet2mir/us3 download -s myfile

Licence

Licensed under the Apache License, Version 2.0 (the “License”); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Metadata

Release files for us3 0.0.7

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for us3 0.0.7
File	Size	Uploaded	Provenance	Actions
us3-0.0.7.tar.gz	5.8 kB	Mar 15, 2016	Without provenance	Details for us3-0.0.7.tar.gz

Release files / us3-0.0.7.tar.gz

Download URL	us3-0.0.7.tar.gz
Size	5.8 kB
Tags	Source
SHA-256 checksum How to use checksums	`aa4a1e4029f7dbcf9741369a2972e05eadcd3e0803a5940d3c157fc4fbe1dc33`
BLAKE2b-256 checksum How to use checksums	`4b8494d2389a7697d2679d04fe5124c2b9cf1fa34e26739a75d6f68c3665cd30`
Upload date	Mar 15, 2016
Uploaded using Trusted Publishing? What is trusted publishing?	No

Security for us3 0.0.7

Report project as malware

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.0.7 This release

Mar 15, 2016 1 release file No provenance

us3 0.0.7