Amazon EC2 Container Service
Developer Guide (API Version 2014-11-13)

ecs-cli down


Deletes the CloudFormation stack that was created by ecs-cli up and the associated resources. The --force option is required.


The ECS CLI can only manage tasks, services, and container instances that were created with the ECS CLI. To manage tasks, services, and container instances that were not created by the ECS CLI, use the AWS Command Line Interface or the AWS Management Console.

The ecs-cli down command attempts to delete the cluster specified in ~/.ecs/config. However, if there are any active services (even with a desired count of 0) or registered container instances in your cluster that were not created by ecs-cli up (for example, if you used an existing ECS cluster with registered container instances, such as the default cluster), the cluster is not deleted and the services and pre-existing container instances remain active.

If you have remaining services or container instances in your cluster that you would like to remove, you can follow the procedures in Cleaning Up your Amazon ECS Resources to remove them and then delete your cluster.


ecs-cli down --force [--help]


Name Description

--force, -f

Acknowledges that this command permanently deletes resources.

Required: Yes

--help, -h

Show the help text for the specified command.

Required: No



This example deletes a cluster.

$ ecs-cli down --force INFO[0001] Waiting for your cluster resources to be deleted INFO[0001] Cloudformation stack status stackStatus=DELETE_IN_PROGRESS INFO[0062] Cloudformation stack status stackStatus=DELETE_IN_PROGRESS INFO[0123] Cloudformation stack status stackStatus=DELETE_IN_PROGRESS INFO[0154] Deleted cluster