Skip to main content

Elastic Beanstalk Intelligence, Simple CLI tool for ElasticBeanstalk with Docker.

  • Deploying apps more intuitively

    • Without git integration

    • Switch-able Dockerrun.aws.json

    • Switch-able docker-compose.yml

    • Switch-able .ebextensions/

Install

pip install ebi

Requires Python2.7 or 3.5

Usage

deploy

To deploy app, just type it on project root:

$ ebi deploy <app_name> <env_name>

This will

  1. Create zip file including Dockerrun.aws.json and .ebextensions or docker-compose.yml and .ebextensions

  2. Uploading zip to S3 as same directory as awsebcli.

  3. Deploying app (by calling eb deploy with uploaded –version)

options:

  • --version: version label for app. default is timestamp.

  • --prefix: version prefix for app. It is added to timestamp.

  • --description: description for this version.

  • --dockerrun: File path used as Dockerrun.aws.json.

  • --docker-compose: File path used as docker-compose.yml.

  • --ebext: Directory path used as .ebextensions/

  • --profile: Configured profile for AWS.

  • --region: region for AWS.

create

To create app, just type it on project root:

$ ebi create <app_name> <env_name> <cname_prefix>

This will

  1. Create zip file including Dockerrun.aws.json and .ebextensions or docker-compose.yml and .ebextensions

  2. Uploading zip to S3 as same directory as awsebcli.

  3. Creating app (by calling eb create with uploaded –version)

options:

  • --version: version label for app. default is timestamp.

  • --prefix: version prefix for app. It is added to timestamp.

  • --description: description for this version.

  • --dockerrun: File path used as Dockerrun.aws.json.

  • --docker-compose: File path used as docker-compose.yml.

  • --ebext: Directory path used as .ebextensions/

  • --profile: Configured profile for AWS.

  • --region: region for AWS.

  • --cfg: Configuration template to use.

bgdeploy

To Blue-Green deploye app, just type it on project root:

$ ebi bgdeploy <app_name> <blue_env_name> <green_env_name> <primary_env_cname>

This will

  1. Create zip file including Dockerrun.aws.json and .ebextensions or docker-compose.yml and .ebextensions

  2. Uploading zip to S3 as same directory as awsebcli.

  3. Deploy new version to secondary environment which doen’t have primary_env_cname (by calling eb deploy with uploaded –version)

  4. Apply primary cname for deployed (secondary) environment

+-------+              +------+
| green |              | blue |
+-------+              +------+
 pri.elastic...com      sec.elastic...com
                          ^
                          |
                      3. deploy!

options:

  • --noswap: Skip swapping to just deploy secondary environment.

  • --version: version label for app. default is timestamp.

  • --prefix: version prefix for app. It is added to timestamp.

  • --description: description for this version.

  • --dockerrun: File path used as Dockerrun.aws.json.

  • --docker-compose: File path used as docker-compose.yml.

  • --ebext: Directory path used as .ebextensions/

  • --profile: Configured profile for AWS.

  • --region: region for AWS.

  • --capacity: Increase the number of desired instances, the minimum size, and the maximum size of the standby environment to the same as the primary environment.

clonedeploy

To deploy app with cloning, just type it on project root:

$ ebi clonedeploy <app_name> <env_name> <green_env_name> <cname_prefix>

This will

  1. Create clone of master environment for next version environment.

  2. Create zip file including Dockerrun.aws.json and .ebextensions or docker-compose.yml and .ebextensions

  3. Uploading zip to S3 as same directory as awsebcli.

  4. Deploy new version to next version (by calling eb deploy with uploaded –version)

  5. Apply master cname for deployed (next version) environment

+--------+              +----------+
| master |  =1.Clone=>  | next ver |
+--------+              +----------+
 master.elastic...com     master-<timestamp>.elastic...com
                          ^
                          |
                      4. deploy!
  • --noswap: Skip swapping to just deploy secondary environment.

  • --version: version label for app. default is timestamp.

  • --prefix: version prefix for app. It is added to timestamp.

  • --description: description for this version.

  • --dockerrun: File path used as Dockerrun.aws.json.

  • --docker-compose: File path used as docker-compose.yml.

  • --ebext: Directory path used as .ebextensions/

  • --profile: Configured profile for AWS.

  • --region: region for AWS.

Metadata

Release files for ebi 0.12.0

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

Source distribution (sdist)

Source distribution for ebi 0.12.0
File Size Uploaded Provenance Actions
ebi-0.12.0.tar.gz 8.9 kB Without provenance Details for ebi-0.12.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for ebi 0.12.0
File Interpreter ABI Platform Actions
ebi-0.12.0-py3-none-any.whl Python 3 none any Details for ebi-0.12.0-py3-none-any.whl

Total release size: 20.9 kB

Release files / ebi-0.12.0.tar.gz

Download URL ebi-0.12.0.tar.gz
Size 8.9 kB
Tags Source
SHA-256 checksum
How to use checksums
1f259aad316094d95b851b4ccb922bebcbcc883ad4f1c10eecf7a3985f2c80aa
BLAKE2b-256 checksum
How to use checksums
bc68b9724efa8170feffd0a12bc47e3bdd46444c0fe56652a13486efb52e89e7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.4.1 importlib_metadata/4.0.1 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.8.9

Release files / ebi-0.12.0-py3-none-any.whl

Download URL ebi-0.12.0-py3-none-any.whl
Size 12.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
47f8b30eb577521c04659adfb869120086d3aa384edfd43c226c6b0e86b6c9bd
BLAKE2b-256 checksum
How to use checksums
aa1127afbd9eab76801fca39fe78509bb86fb812bf62940470ce93b363797909
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.4.1 importlib_metadata/4.0.1 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.8.9

Security for ebi 0.12.0

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

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page