=============
This awscli plugin allows usage of proxy for S3 service stored in profile configuration.
------------
Installation
------------
The easiest way to install awscli-plugin-s3-proxy is to use `pip`:
$ pip install awscli-plugin-s3-proxy
You can also install the latest package from GitHub source which can contain changes not yet pushed to PyPI:
$ pip install git+https://github.com/nowak-ninja/awscli-plugin-s3-proxy.git
or, if you install `awscli` via Homebrew, which bundles its own python, install as following:
$ /usr/local/opt/awscli/libexec/bin/pip install awscli-plugin-s3-proxy
---------------
Getting Started
---------------
Before using awscli-plugin-s3-proxy plugin, you need to [configure awscli](http://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html) first.
**MUST**: Once that's done, to enable `awscli-plugin-s3-proxy` plugin, you can run:
$ aws configure set plugins.s3-proxy awscli_plugin_s3_proxy
The above command adds below section to your aws config file. You can also directly edit your `~/.aws/config` with below configuration.
[plugins]
s3-proxy = awscli_plugin_s3_proxy
To add proxy configure to a profile (assuming you have a **test** profile), you can run:
$ aws configure --profile test set s3.proxy http://proxy-host.com:8080
The above command adds below section to your profile:
[profile test]
s3 =
proxy = http://proxy-host.com:8080
Now you can access S3 using proxy with profile:
$ aws s3 ls --profile test
If You want to use profile without passing it every time as parameter, use environment variable, ex:
export AWS_PROFILE=test
Alternative (classic) method
------------------
You can follow the [guide by AWS](https://docs.aws.amazon.com/cli/latest/userguide/cli-http-proxy.html) which describes how to use proxy using system environment variables. Here is the example:
export http_proxy=http://proxy-host.com:8080
export https_proxy=http://proxy-host.com:8080
export HTTP_PROXY=http://proxy-host.com:8080
export HTTPS_PROXY=http://proxy-host.com:8080
Remember that after setting these variables, `ALL` awscli requests will be going through proxy!
Additionally, if You are using awscli on EC2 host, add `NO_PROXY` variable to allow awscli communicate with metadata endpoint:
NO_PROXY=169.254.169.254
Metadata
Release files for awscli-plugin-s3-proxy 0.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| awscli-plugin-s3-proxy-0.5.tar.gz | 2.5 kB | Without provenance | Details for awscli-plugin-s3-proxy-0.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| awscli_plugin_s3_proxy-0.5-py2-none-any.whl | Python 2 | none | any | Details for awscli_plugin_s3_proxy-0.5-py2-none-any.whl |
Total release size: 5.3 kB
Release files / awscli-plugin-s3-proxy-0.5.tar.gz
| Download URL | awscli-plugin-s3-proxy-0.5.tar.gz |
|---|---|
| Size | 2.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
294dffc7c0821a599593943d510d95d018cf488aa1432ab39b80f264c8609fc7
|
|
BLAKE2b-256 checksum How to use checksums |
ba52534ce8d63b06c6a637c9674571d49c8af11a4c62843344112a1e58e7ca90
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / awscli_plugin_s3_proxy-0.5-py2-none-any.whl
| Download URL | awscli_plugin_s3_proxy-0.5-py2-none-any.whl |
|---|---|
| Size | 2.8 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
b7774ef7bee8acffcdfcd7cf8eca3ab10f16b893c4fb2edd9089a99bddbe1b5d
|
|
BLAKE2b-256 checksum How to use checksums |
685538b808b650972f388c64d59d76f89bd914f4c84b772cac30a3cec66312b2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for awscli-plugin-s3-proxy 0.5
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.