ECS vs EKS for teams without cloud experience
Using EKS saddles teams with heavy management overhead like babysitting clusters and configuring non-app tools like Cilium and FluxCD. For teams lacking cloud or Infrastructure as Code experience, this operational burden gets in the way, whereas ECS offers a simpler alternative with almost no additional abstractions beyond basic AWS primitives.
What people tried
Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.
- 1Using ECS Fargate to avoid server management and lower operational overhead
- 2Relying on consultants for architectural recommendations
In their words
Unedited, most upvoted first, each linked to the thread it came from.
“My gut is telling me ECS is the better choice for this team - simpler, no operational maintenance, almost no additional abstractions beyond the AWS primitives people will need to learn anyway.”source ↗
“The reason was the "management" overhead of babysitting the cluster and it's non-app deployment like cilium, fluxcd etc.”source ↗
Where this came up
People with this problem also raised
- 18Should customer support live inside our CRM?
- 9Why are cloud bills so unexpectedly high?
- 2How to pack a moving container so stuff doesn't break
- 2Should I use Intel VROC or a hardware RAID controller?
- 6Should I use WordPress or Wix for a new business website?
- 26How to find a cheaper CRM when HubSpot gets too expensive