We experienced a ton of memory load on the one healthy EC2 host while we worked out how to deploy container service tasks to the other box (which had originally gone zombie when its root volume filled up).
I temporarily set the Number of tasks in the ECS console to "0" for this service, since we know it gets allocated 2 GB.
This can be re-enabled once the API container deployment starts to stabilize.
We experienced a ton of memory load on the one healthy EC2 host while we worked out how to deploy container service tasks to the other box (which had originally gone zombie when its root volume filled up).
I temporarily set the Number of tasks in the ECS console to "0" for this service, since we know it gets allocated 2 GB.
This can be re-enabled once the API container deployment starts to stabilize.