title: How to scale tasks / containers in AWS ECS
body: <p><a href="https://aws.amazon.com/getting-started/tutorials/deploy-docker-containers/" rel="nofollow noreferrer">This</a> is an introductory guide by AWS on how to deploy microservices - based applications on <code>ECS</code></p>
  
  <p>Apparently (as also becomes evident from the documentation), a so called task definition should encompass <strong>all</strong> of your containers that make up you stack.</p>
  
  <p>i.e. if your corresponding <code>docker-compose.yml</code> file was made of 5 <code>services</code> (in the docker compose context), these should all end up in the <strong>same</strong> ECS Task Definition (?).</p>
  
  <p>From what I understand, this also serves the purpose of automated service discovery among the containers (as is the default behavior in <code>docker-compose</code> and <code>docker swarm</code>);</p>
  
  <p>The problem lies in the fact that the scaling possibility when it comes to ECS is (besides <code>EC2</code> instance) per <code>ECS</code> Service.</p>
  
  <p>Does this mean that you cannot have container-level scaling ?</p>
  
  <p>If I want a service scale, I would have to scale <strong>all</strong> of my containers within my so called stack?</p>