(AWS employee here) First of all I can assure you that Amazon is 100% committed to containers. Amazon's compute strategy is aimed at three levels of abstractio

(AWS employee here) First of all I can assure you that Amazon is 100% committed to containers. Amazon's compute strategy is aimed at three levels of abstraction: instances, containers, lambda. All three are equally important to Amazon. With regard to ECS feature set relative to K8, the thing to understand is that AWS follows a startup-like strategy of launching an MVP and then letting customer feedback drive roadmap from there. AWS is definitely not half hearted about ECS. Rather AWS is constantly working with customers to define a roadmap for further development on ECS. To me the most exciting thing about ECS is the open source work being done around ECS, for Blox (a framework for building out custom container scheduling logic), and the ECS agent itself: https://github.com/blox/blox https://github.com/blox/blox https://github.com/aws/amazon-ecs-agent https://github.com/aws/amazon-ecs-agent With these ECS components you can open issues or even PR's just like any other open source project. Additionally another cool thing we are doing is sharing feature proposals for public comment. You can check out an Amazon employee's public fork of the ECS agent to see a preview of coming roadmap, and we are actively soliciting feedback on proposals such as this one: https://github.com/aaithal/amazon-ecs-agent/blob/f4d80440db06a29a497f74b17e6e9797a7b1367d/proposals/eni.md https://github.com/aaithal/amazon-ecs-agent/blob/f4d80440db0... If you have any questions about ECS, feedback, or concerns feel free to reach out to me directly (peckn@amazon.com) and I'd be happy to chat!