amazon-ecs-agent

We've been using EC2 Container Service for a few months now and at first glance it appears great but we've ran into quite a few problems using it: - You can only bind 1 port and 1 ELB to a service. This means, for example, if you have nginx listening on port 80 and 443 you need to manually configure the ELB and can't take advantage of automatically generated port numbers on the host (So you basically can only have 1 HTTP(s) server on a host) - There is no way to cleanly decommission a host from a cluster. Say if you want to reboot or replace a server in the cluster you can't tell ECS to drain connections from the ELB and move the containers off the host - Unable to specify rules for which hosts services should run on. For example you can't say that the service needs to make sure it has instances in X AZs or don't run multiple instances of

So this Amazon EC2 Container Service Agent[1] is the AWS's own equivalent of Google Cloud Platform's Kubernetes? (Granted, Kubernetes is platform agnostic.) [1]:https://github.com/aws/amazon-ecs-agent

Amazon EC2 Container Service - Full time, Seattle, WA We are hiring for a number of positions on the EC2 Container Service [1] team including software development managers [2], software development engineers [3], and web development engineers [4]. To date our focus has primarily been on building out a highly scalable set of backend services and distributed systems to manage and expose container and cluster state and for task scheduling. We are now looking to add engineers with a strong systems background, particularly around OS virtualization and networking. We are a growing team of (mostly) experienced engineers that likes to iterate quickly. We value scalability, operability, and security and expect everyone on the team to have a say in feature design and prioritization. We also have some fun open source projects [5]. If you are in