Also, would you mind answering my other question about whether or not I can run Marathon or Chronos against ECS since it runs Mesos under the hood?
Thanks for clarifying!
You have to manually scale the AutoScalingGroup, you say? :-)
More seriously, what's the barrier to configuring the ASG to grow and shrink automatically?
There is a workaround, apparently, which is to create a custom metric but aws says this has not been tested to their knowledge... So any asg will be "static" implicitly...
With ecs I can imagine a metric that keeps track of the number of tasks and hosts, or ports used or something. I think asg is the perfect tool to use to auto scale ecs clusters.
Also - all my information is only from the one day container session I attended at the pop-up last week... so I am certainly not an SME on ECS.
In the task definition - it would be MUCH better if you could select the EC2 instance type you want, collect them in an ASG and have the task slicing scale the ASG accordingly.
Right now - you have to manually determine the slice size for each container-to-EC2 and manually scale the ASG.
Further, it was noted that ECS is actually NOT AZ aware and it will spread load over EC2 instances in the pool -- but it wont also balance the tasks across AZs....
So, its a fantastic version one... but these are some resiliency and scaling features that should have already been included.