aws-plugin-bucket-policy
AWS CLI plugin - bucket policy admin tool
Installation
-
Dependencies: python3-minimal python3-pip mandoc groff-base optionally: python3-venv
-
Optionally start virtualenv:
python3 -m venv venv; . venv/bin/activate -
pip install --upgrade pip setuptools awscli aws-plugin-bucket-policy
Configuration
- aws config
.aws/config:
[plugins]
s3bucket-policy = aws_plugin_bucket_policy
- S3 credentials:
.aws/credentials:
[default]
aws_access_key_id = ***
aws_secret_access_key = ***
or using environment variables: AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY
Help
- For help run
aws s3bucket-policy helporaws s3bucket-policy SUBCOMMAND help - Plugin subcommands manual on GitHub
Examples:
aws s3bucket-policy --profile PROFILE_NAME get-policy --bucket BUCKET_NAME
aws s3bucket-policy --profile PROFILE_NAME new-policy --bucket BUCKET_NAME --newpol-type share-w-user --newpol-spec tenant=TENANT_NAME,user=USER_NAME,action=rw
aws s3bucket-policy --profile PROFILE_NAME new-policy --bucket BUCKET_NAME --newpol-type share-w-tenant --newpol-spec tenant=TENANT_NAME,action=ro
aws s3bucket-policy --profile PROFILE_NAME new-policy --bucket BUCKET_NAME --newpol-type ro-public
aws s3bucket-policy --profile PROFILE_NAME put-policy --bucket BUCKET_NAME --policy POLICY_FILE.json
aws s3bucket-policy --profile PROFILE_NAME delete-policy --bucket BUCKET_NAME
Docker way:
Dockerfilebased on ubuntu:jammy- S3 credentials should be defined in
S3_envas AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables: (seeS3_env.templatefile)
AWS_ACCESS_KEY_ID=***
AWS_SECRET_ACCESS_KEY=***
- Usage examples:
docker build -t s3bucket-policy .
docker run -it --rm -u awscli --env-file=S3_env --name s3bucket-policy s3bucket-policy --endpoint ENDPOINT_URL get-policy --bucket BUCKET_NAME
docker run -it --rm -u awscli --env-file=S3_env --name s3bucket-policy s3bucket-policy --endpoint ENDPOINT_URL help
docker run -it --rm -u awscli --env-file=S3_env --name s3bucket-policy s3bucket-policy --endpoint ENDPOINT_URL new-policy help
docker run -it --rm -u awscli --env-file=S3_env --name s3bucket-policy s3bucket-policy --endpoint ENDPOINT_URL new-policy --bucket BUCKET_NAME --newpol-type share-w-tenant --newpol-spec tenant=TENANT_NAME,action=ro
Metadata
Release files for aws-plugin-bucket-policy 1.0.3
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 |
|---|---|---|---|---|
| aws_plugin_bucket_policy-1.0.3.tar.gz | 9.2 kB | Without provenance | Details for aws_plugin_bucket_policy-1.0.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| aws_plugin_bucket_policy-1.0.3-py3-none-any.whl | Python 3 | none | any | Details for aws_plugin_bucket_policy-1.0.3-py3-none-any.whl |
Total release size: 20.0 kB
Release files / aws_plugin_bucket_policy-1.0.3.tar.gz
| Download URL | aws_plugin_bucket_policy-1.0.3.tar.gz |
|---|---|
| Size | 9.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b6f60a2937e710fc1cfd6499552ec978751ddd1616196faa266eb13b910bf7c2
|
|
BLAKE2b-256 checksum How to use checksums |
c944403e4b9bb4604fb56ac0e8dd72238567eb3e06f1f9c5f753d67900728b5d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Release files / aws_plugin_bucket_policy-1.0.3-py3-none-any.whl
| Download URL | aws_plugin_bucket_policy-1.0.3-py3-none-any.whl |
|---|---|
| Size | 10.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e3a0585e8d4d42696ef5cc01b4adf6261a3151f58f7b86cb4820eff3077d4743
|
|
BLAKE2b-256 checksum How to use checksums |
fe1a5cdbe527b3108b0d5b0f64c010b803122e64ff696d98921cc83367522e18
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Security for aws-plugin-bucket-policy 1.0.3
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.