TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Building blocks of Amazon ECS

116 点作者 ifcologne超过 7 年前

10 条评论

ajsharp超过 7 年前
&quot;Let&#x27;s begin with an analogy&quot;<p>[4 paragraphs of fantasy explorer game references]<p>All I&#x27;ve learned is my brain hurts.
评论 #16227408 未加载
评论 #16228107 未加载
评论 #16229310 未加载
评论 #16228887 未加载
评论 #16236734 未加载
评论 #16229939 未加载
dionian超过 7 年前
Even if i skipped the spaceship whole analogy section (I did), all in all really glad to see more easily accessible explanations for AWS technology than the main documentation. I love how approachable this is, and the diagrams help.
nikkwong超过 7 年前
What this post doesn&#x27;t explain well is the benefit of using ECS rather than just uploading a docker image to an EC2 instance and running it.
评论 #16231665 未加载
评论 #16229551 未加载
turdnagel超过 7 年前
I&#x27;ve had a lot of good experiences with ECS so far, except for their scheduled tasks system. With cron, you check &#x2F;var&#x2F;mail. When a scheduled task doesn&#x27;t run on ECS... you&#x27;re SOL.
评论 #16231913 未加载
评论 #16230480 未加载
评论 #16228258 未加载
评论 #16229272 未加载
评论 #16227743 未加载
drewjaja超过 7 年前
For those looking for a more in-depth explanation of Amazon ECS, I highly recommend the videos here <a href="https:&#x2F;&#x2F;awsdevops.io&#x2F;p&#x2F;hitchhikers-video-guide-aws-docker" rel="nofollow">https:&#x2F;&#x2F;awsdevops.io&#x2F;p&#x2F;hitchhikers-video-guide-aws-docker</a>
hardwaresofton超过 7 年前
Why even use ECS when you can just start an Elastic Beanstalk docker-based cluster, and get superior, more focused web UI (at least the UI for EB is superior at present) along with much easier configuration?<p>If I sound bitter, it&#x27;s because I am -- I recently spent about 2 days straight trying to build an ECS cluster reliably with CloudFormation, and while I must admit I was newer than normal to CloudFormation templates, the amount of errors I ran into (and incredibly slow provision&#x2F;creation&#x2F;update time), along with the broken edge cases (try and make an existing EC2 bucket with CloudFormation) was infuriating. Don&#x27;t read any further if you don&#x27;t want to read a rant.<p>While ECS is great in theory (or if you set it up by clicking tons of buttons on AWS&#x27;s UI), it&#x27;s significantly harder to automatically deploy than BeanStalk is, from where I&#x27;m standing. All I have to do is get a container with the eb command line tool installed, do a bunch of configuration finangling (which honestly is ridiculous as well, just let me give you a file with all my configuration in it, or read it from ENV, and stop trying to provide interactive CLIs for everything, for fucks sake) and I can run `eb deploy` and push a zip file with nothing but a docker container (muilti container setups are also allowed) specified up to the cloud. Later I&#x27;m going to look into using CloudFormation to set up EB, but I know even that will be simpler, because I won&#x27;t have to try and make any ECS::Service objects or ES::TaskDefinitions.<p>Trying to use ECS made me so glad that Kubernetes exists. Unfortunately in my work I can&#x27;t use it currently because that would mean the rest of the team stopping to learn it, but Cloudformation + ECS is a super shitty version of setting up a kubernetes cluster and using a kubernetes resource config file. I think the best part about kubernetes is that if the community keeps going the way it&#x27;s going, cloud providers will finally be reduced to the status of hardware vendors -- all I&#x27;ll need from EC2 is an (overpriced) machine, network access, and an IP, not to try and keep up with it&#x27;s sometimes asinine contraptions and processes, or be locked in to their ecosystem.
评论 #16230517 未加载
评论 #16230567 未加载
评论 #16230300 未加载
评论 #16231880 未加载
ravenstine超过 7 年前
ECS is pretty nice. I wish they did what Rancher did by allowing docker-compose.yml and an extra YML file for Rancher-specific setup.
评论 #16227664 未加载
评论 #16227834 未加载
fapjacks超过 7 年前
So many things are janky in ECS that it ends up costing too much time and energy to get anything done. I&#x27;ve posted at length before about all the specific problems I hit while building on ECS, but lately I&#x27;ve just been telling people that it&#x27;s like that janky toolbox in the funny old &quot;PHP is a fractal of bad design&quot; blog post [0]. Of all the AWS services I ever used, I find ECS <i>by far</i> the most terrible. Even worse than Amazon&#x27;s documentation. So this really stunted and awkward spaceship analogy is pretty hilarious, given that it&#x27;s about ECS.<p>[0] <a href="https:&#x2F;&#x2F;eev.ee&#x2F;blog&#x2F;2012&#x2F;04&#x2F;09&#x2F;php-a-fractal-of-bad-design&#x2F;" rel="nofollow">https:&#x2F;&#x2F;eev.ee&#x2F;blog&#x2F;2012&#x2F;04&#x2F;09&#x2F;php-a-fractal-of-bad-design&#x2F;</a>
评论 #16230659 未加载
dkobran超过 7 年前
This makes me want to die
cagenut超过 7 年前
I happen to be working on this and since there&#x27;s a thread why not ask...<p>Has anyone gotten &quot;multi-tenant&quot; (default-restricted) overlay network(s) working on ECS in a way that they like?