From docker-compose to AWS ECS

This module is responsible to understanding the docker compose file as a whole and then more specifically putting together the settings of the services defined.


The services are defined in YAML under the services section. Each service then has its own set of properties that can be defined.


In order to introduce a feature allowing to map together two services in docker-compose within a single ECS Task Definition, via deploy labels, you can now create a “family” which identifies the group throughout, for permissions and otherwise.


Head to labels to define your services families


A service without a family is its own family, re-using the same name.


To enable further configuration and customization in an easy consumable format, still ignored by docker-compose natively, you can define x-configs into the services definitions.

Features that ECS ComposeX takes care of for you, if you needed to:

  • Register services into Service Discovery using AWS Cloud Map

  • Adds X-Ray side car when you need distributed tracing

  • Calculates the compute requirements based on the docker-compose v3 declaration

  • Supports to add IAM permission boundary for extended security precautions.

  • Support for AWS Secrets Manager secrets usage.

  • Supports for scaling definitions
    • SQS based step scaling

    • Target Tracking scaling for CPU/RAM



ECS Cluster configuration

x-cluster allows you to configure the ECS Cluster as you wish to, instead of my own defaults. If you do not specify your own settings, the default settings will be applied.

Default settings:

As you know, I am going for Fargate first and only as the default deployment mechanism.

  • FARGATE_SPOT, Weight=4, Base=1

  • FARGATE, Weight=1

Setting the Properties accordingly to AWS CloudFormation Reference for ECS Cluster will allow you to override the default settings with your own.


Head to x-cluster for more details on how to use x-cluster.