AWS Fargate – Run Containers Without Managing Infrastructure

Re:AWS Fargate – Run Containers Without Managing Infrastructure by NathanKP on Wednesday November 29, 2017 @12:12PM (#15808572)

AWS employee here. You would deploy to Fargate because you don't want to have to manage the underlying EC2 instances. You can use Fargate with both ECS and EKS (in 2018).

ECS and EKS are just two different schedulers for orchestrating the containerized services that you want to run. Fargate is the engine behind them that executes the containers for you without you needing to worry about servers.

ECS as a scheduler will always integrate much better with other AWS services. EKS will give you the advantage of being able to run the same scheduler on an on premise or on another cloud.

[ Parent | on HN ]

Re:AWS Fargate – Run Containers Without Managing Infrastructure by chkal on Wednesday November 29, 2017 @02:31PM (#15810042)

Thanks a lot for the explanation.

[ Parent | on HN ]

Re:AWS Fargate – Run Containers Without Managing Infrastructure by mgalgs on Wednesday November 29, 2017 @12:59PM (#15809128)

I thought EKS was managed? Do you still have to manage the underlying instances in EKS?

[ Parent | on HN ]

Re:AWS Fargate – Run Containers Without Managing Infrastructure by kainosnoema on Wednesday November 29, 2017 @06:08PM (#15811758)

Yes, EKS is just managed K8s, which is the orchestration layer. You still need to have EC2 instances for the EKS tasks to be scheduled on. Unless you run your EKS tasks on Fargate, which is coming in 2018.

[ Parent | on HN ]

Re:AWS Fargate – Run Containers Without Managing Infrastructure by avgkol on Wednesday November 29, 2017 @10:55PM (#15813353)

So if I do "kubectl get nodes" while using Fargate, what do I see in response?

[ Parent | on HN ]