Public Repository

Last pushed: 2 years ago
Short Description
Consul image that runs on AWS ECS
Full Description

Consul ECS

This image is based on It solves the problem of setting up consul servers on ECS which is a bit tricky with the AWS task definition.


  • You will need AWS CLI installed or alternatively register the definitions manually.
  • You will need to set up an internal load balancer in AWS


The image and task definition are constructed in a way it's easy to modify the parameters using env variables.

There are two task definitions, bootstrap and server which are used to set up the environment. Bootstrap has an extra variable (CONSUL_PARAMS) that sets the consul in bootstrap mode. Server task definition uses the same environmental variable to pass the information about the internal load balancer.

Load Balancer is required so that we know to which node we can connect initially. It needs to listen on ports 8301 and 8500. Replace INTERNALELB in consul-server-definition.json with the hostname of your internal load balancer

There are to extra env variables that are defined when container starts. JIP sets the ip of the host machine that will be advertised, JNODE is used to set the name of the node.

Task definitions include dns server ip. Make sure it's correct for your environment. You can check that using ifconfig and comparing the ip in docker0 section on one of your ECS instances.

You can check if the nodes are registered using dig.

dig @ -p 53 INSTANCEHOSTNAME.node.consul

Docker Pull Command