News for hackers. Stuff that matters.

A comment on AWS Fargate – Run Containers Without Managing Infrastructure. Parent comment

Re:AWS Fargate – Run Containers Without Managing Infrastructure by tbrock on Wednesday November 29, 2017 @06:47PM (#15812006)
I’m your target for this service as a large consumer of ECS that hates dealing with the underlying resources. Despite fargate being very compelling it’s priced too damn high (even without the mistake).

I’d be willing to pay a premium but this is just not cost effective.

[ Parent | on HN ]
Re:AWS Fargate – Run Containers Without Managing Infrastructure by heisnotanalien on Thursday November 30, 2017 @04:57AM (#15814636)
You hate starting an AMI and having a simple script to connect to an ECS cluster?
[ Parent | on HN ]
Re:AWS Fargate – Run Containers Without Managing Infrastructure by tbrock on Thursday November 30, 2017 @08:24AM (#15815490)
No, that’s the easy part. I strongly dislike that auto scaling groups do not communicate with ECS (service scaling) and that updating your nodes to run a new ECS optimized ami is tedious and error prone.

Want to scale up/down when you have high or low load? Cool, configure it at the ECS service level AND at the auto scaling group level. Will the auto scaling group take instances away before they’ve been drained of connections or randomly? Who knows the systems don’t talk to one another to coordinate: Fail

What about just removing a node from the cluster when it fails? Decrease service count min temporarily -> Drain connections elb -> remove from target group -> kill instance. This is a 5-10 minutes process to do correctly that should be 1 click. Same problem, stuff doesn’t talk.

Want to update to a new ECS optimied AMI to get updates and patches but ensure a minimum of core services keep running while you scale down after you’ve scaled up? Good luck!

[ Parent | on HN ]
Re:AWS Fargate – Run Containers Without Managing Infrastructure by rem7 on Tuesday December 05, 2017 @07:33AM (#15851323)
Also, last time I checked IAM roles sucked on ECS. Not every container in the cluster should have the same role. I wonder if fargate fixes this.
[ Parent | on HN ]