title: Does ECS update-service command marks the container instance state to draining when use with the --force-new-deployment option?
body: <p>The command:</p>
  
  <pre><code>aws ecs update-service --service my-http-service --task-definition amazon-ecs-sample --force-new-deployment
  </code></pre>
  
  <p>As per AWS docs: You can use this option (--force-new-deployment) to trigger a new deployment with no service definition changes. For example, you can update a service's tasks to use a newer Docker image with the same image/tag combination (my_image:latest ) or to roll Fargate tasks onto a newer platform version.</p>
  
  <p>My question, if I use '--force-new-deployment' (as I will use the exisiting tag or definition), will the underline 'ECS Instance' automatically set to DRAINING state, so that any new task (if any) will not start in the EXISTING ecs-instance that is suppose to go away during rolling-update deployment strategy (or deployment controller) ?</p>
  
  <p>In other words, will there be any chance:</p>
  
  <ol>
  <li><p>For a new task to be created on the existing/old container instance, that is suppose to go away during rolling update.</p></li>
  <li><p>Also, what would happen with the ongoing task that is running on this  existing/old container instance, that is suppose to go away during rolling update.</p></li>
  </ol>
  
  <p>Ref: <a href="https://docs.aws.amazon.com/cli/latest/reference/ecs/update-service.html" rel="nofollow noreferrer">https://docs.aws.amazon.com/cli/latest/reference/ecs/update-service.html</a></p>