[werner]

Nope, we have built a new scheduler for you that will allow placement over multiple AZ's, replace failed containers, allow them to connect to ELB's, etc.

[2461001642]

Thanks for responding! Can you say how you deal with the significant latencies over multiple AZs?

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?

[werner]

Can you elaborate on the intra- inter-* latencies your are seeing? for AZ independent services this should single digits.

[2461001642]

When I'm balancing a single deployment across multiple AZs (e.g. US-East -> US-West), the latencies between the containers seem far higher than just the 200-300ms predicted by speed of light. Am I doing something wrong?

[werner]

No mesos under the hood. You can bring mesos as your own scheduler.

[2461001642]

Thanks again - this is really helpful. I had talked to someone who had left Amazon but knew the internal workings who said ECS was Mesos just privately branded like Chef -> OpsWorks, but I guess I must have misunderstood.

Thanks for clarifying!

[samstave]

Thanks - All my info is from the containerization pop-up you guys held last week in SF... The presenters did not seem to know about this.

[nogox]

check out hyper.sh, this is the future of public CaaS. After all, you don't need EC2 to host your containers, if you can run them directly with a hypervisor.