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.
Found another way around this?
Share your steps and trade-offs so fellow engineers don't have to reinvent the wheel. No account required.
- 1Using ECS Fargate to avoid server management and lower operational overheadDid this help you?
- 2Relying on consultants for architectural recommendationsDid this help you?
In their words
Unedited, grouped by where they were said, most upvoted first within each place, 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
- 3Why is infrastructure automation so hard to maintain?
- 4Where can I practice Microsoft 365 admin center for free?
- 13Why does a cloud outage feel like total chaos internally?
- 2Transitioning from cloud to on-premises AD and server admin
- 2What kind of joint brokerage account should we get for bills and savings?
- 33Should customer support live inside our CRM?