title: AWS Fargate startup time
body: <p>Currently I'm researching on how our dockerised microservices could be orchestrated on AWS.
  The Fargate option of ECS looks promising eliminating the need of managing EC2 instances. </p>
  
  <p>Although it's a surprisingly long time needed to start a "task" in Fargate, even for a simple one-container setup. A 60 seconds to 90 seconds are typical for our Docker app images. And I heard it may take even more time like minutes or so. </p>
  
  <p>So the question is: while Docker containers typically may start in say seconds what is exactly a reason for such an overhead in Fargate case?</p>
  
  <p>P.S. The search on related questions returns such options:</p>
  
  <ol>
  <li>Docker image load/extract time </li>
  <li>Load Balancer influence -
  registering, healthchecks grace period etc</li>
  </ol>
  
  <p>But even in simplest possible config with no Load Balancer deployed and assuming the Docker image is not cached in ECS, it is still at least ~2 times slower to start task with single Docker image in Fargate (~ 60 sec) than launch the same Docker image on bare EC2 instance (25 sec)</p>