aeropress is a CLI program for deploying Docker images to AWS ECS. It receives a folder path that includes ECS task and service definitions and then does the jobs respectively;
Register ECS task definitions
Create Cloudwatch metrics for scaling policies
Create or update scaling policies for ECS services
Create or update alarms on Cloudwatch
Create or update ECS services
Installation
aeropress works with Python3.
pip3 install aeropress
Usage
$ aeropress --help
usage: cli.py [-h] [--logging-level {debug,info,warning,error}] [--version]
{deploy,clean} ...
aeropress AWS ECS deployment helper
positional arguments:
{deploy,clean} sub-command help
deploy Deploy docker image to ECS.
clean Clean commands for stale entitites on AWS.
optional arguments:
-h, --help show this help message and exit
--logging-level {debug,info,warning,error}
Print debug logs
--version show program's version number and exit
Example
You must have defined an ECS cluster first. Then, you can define ECS tasks and services in a yaml file and run aeropress with required arguments.
aeropress deploy --path 'example/foo.yaml' --image-url 'registry.hub.docker.com/library/python' --service-name service-foo
Release files for aeropress 0.0.51
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 | |
|---|---|---|---|---|
| aeropress-0.0.51.tar.gz | 12.9 kB | Without provenance | Details |
Release files / aeropress-0.0.51.tar.gz
| Download URL | aeropress-0.0.51.tar.gz |
|---|---|
| Size | 12.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
017bfc4daa1b559740c018311b8f1e48d0f74db5bb3d6e1f151396ecf97e965a
|
|
BLAKE2b-256 checksum How to use checksums |
4f853634a1b8c66ed1ab2be6dfe5b3859b89d7679430d2ba9aa1e755fdf24dea
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.14
|
Security for aeropress 0.0.51
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.
