Consul ECS

Consul ECS is a Docker image that installs and runs HashiCorp Consul inside Amazon Elastic Container Service (ECS), giving containerized workloads service…

  • Infrastructure
  • Tools & Utilities
Consul ECS is a Docker image that installs and runs HashiCorp Consul inside Amazon Elastic Container Service (ECS), giving containerized workloads service discovery, configuration, health checks, and secure communication without manual mesh setup.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

69/100 Good

Maintained
100last commit 16 days ago
Popular
3031 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
No data
Security check
100no serious findings, CI, tests

Based on 4 of 5 factors.

GitHub stars
31
Open issues
10
Last commit
2026-11-05
Latest release
v0.11.0
License
MPL-2.0
Activity
rising

Checked 15 days ago - source: GitHub (hashicorp/consul-ecs)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Install helper tools before apt setup On Ubuntu/Debian, use apt-get to install wget, gpg (a tool for checking package signatures), and coreutils before adding the HashiCorp package repository. Without them, the repository setup can fail and the Consul packages may not install. source
  • Prepare OpenShift Local first If you are using OpenShift Local (a local Kubernetes-like cluster for testing), run crc setup before starting it to verify system requirements and prepare the environment. Without this step, the local cluster may fail to start, leaving you with no place to install or test Consul. source
  • Check Consul on Kubernetes after install After installing Consul in Kubernetes (a system for running containers), run the consul-k8s status command to see a health summary of the servers, clients, and deployment settings. If you skip it, a small install mistake can look like a broken app later. source
  • Install Consul on ECS Use the hashicorp/consul-ecs Docker image in Amazon ECS and follow HashiCorp’s Consul ECS documentation to configure Consul server and client tasks. source

Fetched 41 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What containers should be included in each ECS task for Consul service mesh?

Each ECS task runs an application container, a Consul client agent, and an Envoy proxy.

Why might a Consul ECS mesh-init task stay pending?

It can get stuck pending when it cannot connect to Consul servers due to ACL token problems.

Is the basic ECS Consul cluster example a complete guide?

It is only an example of how to get a Consul cluster up and running in ECS, and it does not tell the whole story.

Answers sourced from developer.hashicorp.com, discuss.hashicorp.com, www.reddit.com

Community

Collected 48 days ago - public community threads