- Exposes an HTTP endpoint for a given S3 bucket and prefix.
Supports exposing private S3 keys through an IAM key/secret. Transparently serves index.html for URLs ending in / and will generate an index when no index.html is found.
Originally meant as a way to serve a private pypi repository on an S3 bucket.
Metadata
Release files for s3proxy 0.5.1
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 |
|---|---|---|---|---|
| s3proxy-0.5.1.tar.gz | 3.1 kB | Without provenance | Details for s3proxy-0.5.1.tar.gz |
Release files / s3proxy-0.5.1.tar.gz
| Download URL | s3proxy-0.5.1.tar.gz |
|---|---|
| Size | 3.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
de7e2bf14b266c9db142382010e0696404894e28ea4d4e526b8d9289e7426649
|
|
BLAKE2b-256 checksum How to use checksums |
0a4be44c723fb90824509445965da4839dc724dd443a2608b0a862c4bcc25f8c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for s3proxy 0.5.1
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.