AWS Fargate

17 engineers on Hacker News describe using AWS Fargate first-hand: 4 endorse it, 7 regret it, 2 are mixed.

40%trust
17first-hand users
15in production
endorse 4mixed 2regret 7uses, no opinion

“we switched from fargate to EC2 auto scaling group ... we went from a ~3 minute startup in fargate to ~30 seconds”

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

“Our team is smaller than 20FTE, so we use AWS/Fargate now. Works like a charm.”

endorse · production · cies · 2024-11-27 · source ↗ · wrong label?

“running a container on Fargate is significantly more work than Azure Container Apps”

regret · production · maccard · 2024-02-10 · source ↗ · wrong label?

“Fargate Spot on Graviton is still not available, so if you want to run Spot in non-production environments, you're facing with running different architectures”

regret · production · beaviskhan · 2022-11-30 · source ↗ · wrong label?

“We run all of our workloads on fargate, and it's really annoying when you're trying to iterate on something”

regret · production · easton · 2022-09-02 · source ↗ · wrong label?

“I do currently enjoy not having to manage anything myself and I like that there's no internal abstractions”

endorse · production · politelemon · 2022-08-01 · source ↗ · wrong label?

“we ran into all sorts of SRE-issues. Turns out AWS sets all those “sane limits” that our own folks never did. Still hunting ghosts from the rollout”

regret · production · sk8serboi · 2022-06-01 · source ↗ · wrong label?

“we've moved to Kubernetes running on Fargate and we don't have downtime anymore.”

endorse · production · throwaway7865 · 2022-06-01 · source ↗ · wrong label?

“After trying to set up Fargate and it only sending my logs to cloudwatch 25% of the time”

regret · personal · dkersten · 2021-11-08 · source ↗ · wrong label?

“we switched to Fargate tasks, which have a much larger size limit but take 30s or minutes to boot up”

mixed · production · throwaway894345 · 2020-08-13 · source ↗ · wrong label?

“Fargate wasn't worth it due to the price difference, and just how rigidly they enforce cpu and memory quantization.”

regret · personal · roadofbones · 2019-09-15 · source ↗ · wrong label?

“it has been a pure improvement. ... I would recommend to anyone currently on ECS to give Fargate a try”

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

“I work on a team where our products are all in Fargate containers... half the time when we're debugging an issue in prod... we'll say, "wouldn't this be easier if we could just exec into the container"”

mixed · production · KZeillmann · 2019-04-04 · 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?

“ECS/Fargate (Serverless Docker cluster)”

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

“We switched most our workloads from k8s to ECS (mix of EC2/Fargate launch types)”

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

“Having run a service on Fargate in prod before I can almost guarantee that the errors he was seeing were 504s”

neutral · production · vanrysss · 2019-02-23 · source ↗ · wrong label?