# Install ecs-deploy with Homebrew

CLI tool to simplify Amazon ECS deployments, rollbacks & scaling. Version 1.16.3 via Homebrew; verified 2026-06-09.

## Install

```sh
sudo av install brew:ecs-deploy
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install ecs-deploy
```

  Evidence: local Homebrew formula metadata

## Package facts

- **Package key:** brew:ecs-deploy
- **Package manager:** Homebrew
- **Version:** 1.16.3
- **Source summary:** CLI tool to simplify Amazon ECS deployments, rollbacks & scaling
- **Homepage:** <https://github.com/fabfuel/ecs-deploy>
- **Last updated:** 2026-06-09T13:14:27Z
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- ecs (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 1.16.3
## Project history and usage

ecs-deploy is a Python CLI for common Amazon ECS service operations: deploy, redeploy, scale, run one-off tasks, update task definitions, and update scheduled tasks. Its history is mostly a pragmatic DevOps story rather than a large ecosystem story.

### Project history

The GitHub repository was created in February 2016, during the early period when teams were standardizing Docker deployments on Amazon ECS and needed repeatable command-line workflows around task definitions and services. The README describes the project as a convenience CLI for complex ECS actions that are executed often.

The release history shows steady feature accretion around real deployment needs: Docker Hub images, task-wide CPU and memory limits, environment files, Docker tags, and multi-account usage.

### Adoption history

The README documents installation through PyPI with `pip install ecs-deploy`, Homebrew with `brew install ecs-deploy`, and Docker images beginning with version 1.7.1. That multi-channel distribution is the clearest primary evidence of adoption beyond a source checkout.

The project remains active in 2026 according to repository metadata, but official sources do not provide enough evidence to make broad adoption claims beyond its AWS ECS deployment niche.

### How it is used

Typical use is operational: `ecs deploy` updates or redeploys a service, `ecs scale` changes desired task count, `ecs run` starts one-off tasks, `ecs update` creates revised task definitions, and `ecs cron` updates scheduled tasks.

Configuration follows boto3 and AWS CLI conventions. The README points users to AWS credential configuration, `aws configure`, explicit access-key options, or named AWS profiles.

### Why package nerds care

ecs-deploy is the kind of small package-manager tool that exists because cloud CLIs are too general for one repeated deployment workflow. It wraps AWS ECS primitives into a narrower, scriptable surface for release automation.

It is also a useful packaging example for Python DevOps CLIs: PyPI is the upstream install path, Homebrew serves workstation users, and Docker images serve users who do not want a local Python environment.

### Timeline

- 2016-02: GitHub repository created.
- 2020-08: Release 1.10.2 used in README Docker examples.
- 2021-08: Release 1.12.0 adds environment-file, Docker tag, and flag-related features.
- 2022-04: Release 1.13.0 covers task-wide CPU and memory limits and Docker Hub images.
- 2022-11: Release 1.14.0 adds multi-account usage.

### Related projects

- Amazon ECS is the managed container service ecs-deploy automates.
- boto3 is the AWS Python library that supplies its credential and configuration behavior.
- AWS CLI configuration files are reused for credentials and profiles.

### Sources

- <https://raw.githubusercontent.com/fabfuel/ecs-deploy/develop/README.rst>
- <https://api.github.com/repos/fabfuel/ecs-deploy>
- <https://api.github.com/repos/fabfuel/ecs-deploy/releases>


## Security Notes

No matching local secret-handling manifest was found for ecs-deploy. Nucleus package metadata is still published here so future coverage has a stable package URL.



## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Unix: ~/.aws/config

## Credential files

- Unix: ~/.aws/credentials

## Combined YAML source

View the package source record on GitHub. [combined/ecs-deploy.yml](https://github.com/mxcl/pkgdb/blob/main/combined/ecs-deploy.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph