TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Under the Hood of the Amazon EC2 Container Service

90 pointsby signalerover 9 years ago

5 comments

Tomdarknessover 9 years ago
We&#x27;ve been using EC2 Container Service for a few months now and at first glance it appears great but we&#x27;ve ran into quite a few problems using it:<p>- 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&#x27;t take advantage of automatically generated port numbers on the host (So you basically can only have 1 HTTP(s) server on a host)<p>- 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&#x27;t tell ECS to drain connections from the ELB and move the containers off the host<p>- Unable to specify rules for which hosts services should run on. For example you can&#x27;t say that the service needs to make sure it has instances in X AZs or don&#x27;t run multiple instances of the same service on the same host.<p>- No easy way to implement any kind of service discovery, you have to roll this yourself or set up loads of internal ELBs as a sort of service discovery.<p>- Worst of all the ecs-agent is very buggy. It has releases where it just keeps crashing [1] and leaving untracked running containers just hanging around to an issue where they released a new version with a newer docker library that changed how it handled certain parameters causing our entire cluster to fail until they hot fixed it with a change to how their API sent data to the client.<p>We&#x27;re currently looking at alternatives for our docker infrastructure.<p>[1]: <a href="https:&#x2F;&#x2F;github.com&#x2F;aws&#x2F;amazon-ecs-agent&#x2F;issues&#x2F;156" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;aws&#x2F;amazon-ecs-agent&#x2F;issues&#x2F;156</a>
评论 #10173818 未加载
评论 #10174577 未加载
评论 #10173648 未加载
评论 #10173101 未加载
评论 #10173487 未加载
评论 #10174754 未加载
gtaylorover 9 years ago
I&#x27;ve been doing a lot of playing with Google Container Engine (hosted Kubernetes) on Google Cloud, and have been very impressed so far. Can anyone who has worked with both offer some thoughts on how the two compare?<p>I don&#x27;t know if Amazon&#x27;s Container Service has substantial parts that have been open sourced, but I&#x27;ve been super happy with how Kubernetes is being developed in the open. It&#x27;s also nice that it runs just about everywhere (in theory). It&#x27;s pretty rough to set up manually right now, but I assume that will improve with time.
评论 #10172387 未加载
评论 #10172412 未加载
devyover 9 years ago
So this Amazon EC2 Container Service Agent[1] is the AWS&#x27;s own equivalent of Google Cloud Platform&#x27;s Kubernetes? (Granted, Kubernetes is platform agnostic.)<p>[1]:<a href="https:&#x2F;&#x2F;github.com&#x2F;aws&#x2F;amazon-ecs-agent" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;aws&#x2F;amazon-ecs-agent</a>
samkoneover 9 years ago
This looks a lot like Mesos. But of course they will never admit that. Amazon and open source, a long history.
评论 #10173168 未加载
ageek123over 9 years ago
This was already posted to HN about a month ago... <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=9917339" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=9917339</a>