Amazon ECS

43 engineers on Hacker News describe using Amazon ECS first-hand: 12 endorse it, 5 regret it, 3 are mixed.

67%trust
43first-hand users
41in production
endorse 12mixed 3regret 5uses, no opinion

“I use ECS in prod and its incredibly cheap and efficient.”

endorse · production · infecto · 2024-11-14 · source ↗ · wrong label?

“I will never use AWS again after running up a $100 bill trying to get an app deployed to ECS.”

regret · personal · dkersten · 2024-11-14 · source ↗ · wrong label?

“I have no need to run something any more robust than ECS in AWS for my workload.”

endorse · production · therealfiona · 2024-11-13 · source ↗ · wrong label?

“now I know and am comfortable with ECS where we had solved the issues we had with it with more complex setups”

endorse · production · grogenaut · 2024-06-16 · source ↗ · wrong label?

“We switched from AWS ECS deployment to Vercel after tiring of figuring out how to support Next features”

regret · production · jitl · 2023-10-28 · source ↗ · wrong label?

“those services (cloudfront and ECS being large ones) worked so poorly that caching/reconciliation layers were added”

regret · production · dijit · 2022-04-07 · source ↗ · wrong label?

“We moved all our apps to AWS ECS. Developers happy.”

endorse · production · nuker · 2022-01-27 · source ↗ · wrong label?

“now we're 100% ECS. ... Our deploys on ECS take like 15 minutes.”

endorse · production · jitl · 2021-07-29 · source ↗ · wrong label?

“ecs is simpler and better integrated with the rest of AWS and our build tools.”

endorse · production · grogenaut · 2021-04-25 · source ↗ · wrong label?

“Now everything is visible in Console and we now have tech support down to the ECS Task level.”

endorse · production · nuker · 2020-08-20 · source ↗ · wrong label?

“ECS solves 90% of our problems AND integrates with everything else we're using already.”

endorse · production · whatsmyusername · 2020-06-20 · source ↗ · wrong label?

“My favorite part about using ECS was never being able to deploy because our nodes had jacked up ecs agents on them.”

regret · production · mpmpmpmp · 2019-07-28 · source ↗ · wrong label?

“ECS to GCP Kubernetes recently and our architecture became much more powerful & easy to maintain.”

regret · production · buremba · 2019-04-16 · source ↗ · wrong label?

“We've been using ECS for a while together with Terraform for managing the whole infrastructure in immutable and declarative way, and it has been great so far.”

endorse · production · adambyrtek · 2017-12-31 · source ↗ · wrong label?

“We migrated to AWS ECS and all was well.”

endorse · production · CoffeeDregs · 2017-09-06 · source ↗ · wrong label?

“we rely heavily on ECS, RDS and other managed services... twice a year, we deploy a new version of ecs-agent to our staging cluster and need to revert it”

mixed · production · ekidd · 2016-11-11 · source ↗ · wrong label?

“ECS has its issues, but is still much more manageable than anything else (on AWS).”

mixed · production · arikfr · 2016-11-11 · source ↗ · wrong label?

“At Button we switched from baking AMIs to deploying containers on ECS and it's had a pretty amazing effect on deploys”

endorse · production · Hovertruck · 2016-03-09 · source ↗ · wrong label?

“failure modes get taken care of by ECS managing desired state well.”

endorse · production · ejholmes · 2015-08-02 · source ↗ · wrong label?

“we've been using the fresh-out-of-beta ECS, and running into a lot of limits there”

mixed · production · NathanKP · 2015-07-09 · source ↗ · wrong label?

“we just run simple ProcessWorkers for our regular needs and ECS worker for heavier ML tasks.”

neutral · production · tecoholic · 2026-01-28 · source ↗ · wrong label?

“mostly I deploy Docker containers to various managed services on AWS - Lambda, ECS, etc.”

neutral · production · raw_anon_1111 · 2025-12-04 · source ↗ · wrong label?

“each prefect flow launches in a discrete ECS task so the waiting added up.”

neutral · production · leetrout · 2025-11-17 · source ↗ · wrong label?

“I've used both ECS+Fargate and Kubernetes, but these days, I prefer Kubernetes”

neutral · production · Ramiro · 2024-08-09 · source ↗ · wrong label?

“I have used a number of orchestrator platforms in production, including AWS ECS (Docker + custom orchestration)”

neutral · production · ekidd · 2023-12-18 · source ↗ · wrong label?

“figuring out the ECS run-task api syntax and some other things I'd rather forget about”

neutral · production · efxhoy · 2023-05-26 · source ↗ · wrong label?

“xdebug works fine, I even got it working recently in ECS.”

neutral · production · user3939382 · 2022-08-16 · source ↗ · wrong label?

“Main rails containers, nginx, sidekiq and almost everything in ECS.”

neutral · production · efxhoy · 2022-08-01 · source ↗ · wrong label?

“ECS/Fargate (Serverless Docker cluster)”

neutral · production · scarface74 · 2020-12-20 · source ↗ · wrong label?

“since we run ECS on Spot instances it would just be a massive increase in cost to switch to FG”

neutral · production · l33tman · 2020-07-23 · source ↗ · wrong label?

“We run 60+ microservices, each of which has multiple processes that run, each of which is autoscaled (we use ECS).”

neutral · production · phamilton · 2019-12-19 · source ↗ · wrong label?

“We were affected with one of our marketing pages that we migrated to ECS in a non-HA configuration”

neutral · production · Roritharr · 2019-11-12 · source ↗ · wrong label?

“we run a bunch of standard up ECS clusters, and it'd be nice to not have to provision and maintain servers.”

neutral · production · roadofbones · 2019-09-15 · source ↗ · wrong label?

“we switched from ECS without Fargate (managing our own EC2 instanced) to ECS with Fargate”

neutral · production · jacobkg · 2019-04-14 · source ↗ · wrong label?

“We're having performance issues on AWS, trying to run on ECS with an EFS Filesystem underneath”

neutral · production · Roritharr · 2019-01-22 · source ↗ · wrong label?

“All of our services run on AWS ECS and CI is done through CircleCI.”

neutral · production · dmlittle · 2018-12-31 · source ↗ · wrong label?

“We have clients using Kubernetes on AWS and bare metal, using just Docker Compose (no Swarm) on virtualized and bare metal machines, and using ECS.”

neutral · production · spectre256 · 2018-11-28 · source ↗ · wrong label?

“a recent Docker/AWS/ECR/ECS system I worked on, much of which seemed like a whole lot of useless work”

neutral · production · lkrubner · 2018-11-28 · source ↗ · wrong label?

“we're starting a trial of ECS for the organization's first formal foray into containers.”

neutral · personal · yebyen · 2017-12-11 · source ↗ · wrong label?

“Now we run Kafka through ECS and wrote some tooling to manage rolling the cluster and replacing brokers.”

neutral · production · TheHydroImpulse · 2017-05-31 · source ↗ · wrong label?

“would have easily taken me 5 or 6 weeks to do in Amazon ECS, which is what we currently use in production.”

neutral · production · andrewstuart2 · 2016-12-26 · source ↗ · wrong label?

“In production we run in AWS ECS Service clusters with 9 containers per cluster.”

neutral · production · trcollinson · 2016-12-09 · source ↗ · wrong label?

“I use docker in production right now with ec2 container services and automated deployment from gitlab-ci.”

neutral · production · trcollinson · 2016-11-20 · source ↗ · wrong label?