Fargate looks really expensive compared to just running an EC2 instance. A 1 vCPU container with 2GB of RAM will run you $55/month. An m3.medium with 1 vCPU and 3.75GB of RAM is $49. The prices seen to get uncomfortably worse from there, though I haven't priced them out the whole way, but a 4 vCPU container with 8GB of RAM is price-competitive ($222 for the container, $227 monthly for the machine) with a freaking i3.xlarge, with 4 vCPUs and 30.5GB, and the i3.xlarge also has 10Gbit networking. Topping Fargate out at 4 vCPUs and 30GB of RAM puts it right between an r4.2xlarge and an i3.2xlarge, both with 8 vCPUs and 61GB of RAM (the i3 is more expensive because it's also got 1.9TB of local SSD).<p>Enough people are still trying to make fetch happen, where fetch is container orchestration, that I expect that fetch will indeed eventually happen, but this is a large vig for getting around not-a-lot-of-management-work (because the competition isn't Kubernetes, which is the bin packing problem returned to eat your wallet, it's EC2 instances, and there is a little management work but not much and it scales).<p>If you have decided that you want to undertake the bin packing problem, AWS's ECS or the new Elastic Kubernetes Service makes some sense; you're paying EC2 prices, plus a small management fee (I think). I don't understand Fargate at all.
(Azure Container Instance engineer here)<p>This looks very similar to what we launched with Azure Container Instances last summer.<p>The Azure Container Instances kubernetes connector is open source and available here:<p><a href="https://github.com/Azure/aci-connector-k8s" rel="nofollow">https://github.com/Azure/aci-connector-k8s</a>
I think I have AWS fatigue. I have a few certifications and a few years of experience working with AWS, but it's getting difficult to even keep track of all the services.
Notably, this appears to confirm a Kubernetes offering (EKS)!<p><pre><code> I will tell you that we plan to support launching containers on Fargate using Amazon EKS in 2018
</code></pre>
[Edit] Looks like that just got announced too: <a href="https://aws.amazon.com/eks/" rel="nofollow">https://aws.amazon.com/eks/</a>.
I love AWS and their pace of innovation, but some areas are really lagging behind.<p>Two new container services announced but São Paulo still doesn't even have ECS which was announced in 2014.
Is "Fargate" an Aqua Teen Hunger Force reference?
<a href="https://youtu.be/uOd7HQoKxcU?t=38" rel="nofollow">https://youtu.be/uOd7HQoKxcU?t=38</a>
I am getting lost with all the ways to run containers on AWS. Is this the equivalent of google compute engines beta option to boot from a docker container?
I'm not 100% sure about the relationship between EKS, ECS and Fargate.<p>Why would I deploy to Fargate over EKS? I assume it's because with Fargate I don't have to write a k8s deployment spec?<p>Why would I deploy to Fargate over ECS?<p>Legitimately curious, and looking for clarification/correction.
After reading lots of negative comments about pricing, I think that many people don't get it - AWS Fargate is not a replacement of EC2 nor ECS. It's a sort of lambda with containers and lots of features (HA, autoscaling, etc.) implemented + pay-per second - which is absolutely great! This way you could run short and long running jobs which are container-based (a django-admin job that performs migrations? dunno... just saying...), and also your "normal" services without taking care of scaling up/down, HA, etc.<p>It's not for everyone, it's not a "one solution fits all", it's very specific and what it does, it does it great (only tested, of course we have to see long-term...), because you don't need anymore to manage a cluster, which is really expensive especially because you don't want to shutdown your machines when you go home and restart them when you come back to the office (for example, in case you don't have a smart autoscaling in place).<p>Thanks AWS for providing this service!
This is going to be really <i>great</i> for batch jobs which need isolated environments. I have been waiting for something like this for a long time. Amazon is really doing work. I'll be definitely be using this.
Fargate is a very logical step, I agree Kubernetes is really nice but very complex for simplistic setups, looking forward to use it, too bad it's only in N. Virginia
Ive been using hyper.sh i really like it. Especially i dont want a web interface i can pull a container and start up a container from my command line in 3 seconds. I can pull from docker repo attach ips and storage all in terminal. How does this compare i want to stay out of a web mgmt interface.
If I understand this correctly, Fargate is similar to Elastic Container Service, without having to worry about EC2's instances? But you also can manage the EC2 instances with Fargate as well? Seems like AWS has lots of products that overlap and it is confusing to end users.<p>I'd say this is exactly why Google Cloud is superior (in my opinion). AWS lacks user experience and KISS philosophy. Just feels like AWS keeps on bolting things on.
I wonder how they handle isolation. Linux container technologies don't normally provide sufficient isolation for multi-tenant environments, which is why most of the cloud container orchestrators require you to pre-provision VMs (ECS, GKE).<p>Azure Container Instances uses Windows Hyper-V Isolation that boots a highly optimized VM per container, so containers have VM isolation.<p>Has AWS built a highly optimized VM for running container?
It would be interesting to see how fast the startup time of the docker containers will be. If its for faster than EC2, this could be used for some super elastic job processing. Somewhere between EC2 and lambda. I doubt the startup time would be faster, since the docker image download would hit the startup timing.<p>If the startup time is fast, and it can run of GPU, a killer Deep learning platform could run on this.
Everyone at Zapier was hoping for AWS managed Kubernetes.<p>Edit: Maybe we'll get it! <a href="https://twitter.com/AWSreInvent/status/935909627224506368" rel="nofollow">https://twitter.com/AWSreInvent/status/935909627224506368</a>
I haven't had a chance to dig through the documentation yet. Can we deploy a POD instead of just a container? One of the things we are struggling with is all the side services that have to go with a container deployment (i.e. a secure or oauth proxy).
For low utilization low cost continuous applications (think a web socket listener with not much to do) this lowers the entry level cost below a t2.nano it looks like. That’s a win in my book.
It has nothing to so with that movie, or the syndicates series based on zeh movie...<p>A part of me really hopes the pm named it this as an aquateen reference
looking at the number of Amazon products on the front-page, it's mind-blowing. Amazon (will) probably have a monopoly on developer mindshare in the future.
sigh, amazon is taking over hacker news. They need to chill on posting. They posted 15 posts to the front page and thats 50% of the headlines... all amazon.<p>Hope everyone loves amazon!
A third of the front page of Amazon; what's going on? Did they release a dozen products in one go? Interesting release strategy to bulk everything as opposed to spacing it out..