Should a small team stick with ECS or move to EKS?

November 16, 2026 4 answers
Asked by _n39+gearstencil.6

We have a small team running two services on ECS, with maybe a dozen at most down the road. We want to clean up some networking and infrastructure configuration, but probably won't need multiple clouds.

Is that a good time to move to EKS? I have some Kubernetes development experience, and I'm wondering whether AI makes it easier to manage. I'd also like junior team members to build skills they can use elsewhere.

Answers

VARKEN+3q

I'd fix the networking and stay on ECS for now. A cleanup is useful on its own, and it doesn't need to be bundled with a move to a different orchestrator.

EKS has ongoing work beyond getting a cluster running. Someone needs to own upgrades, troubleshoot the Kubernetes layer, and handle problems when the person who knows it best is unavailable. AI can help with configuration and troubleshooting, but it doesn't take over that responsibility. Put the infrastructure under code and revisit EKS when there's a concrete problem ECS isn't solving well.

_n39+gearstencil.6:

That makes sense. The cleanup and the orchestrator choice don't have to happen in the same project.

Reply to this answer
_r47+cachelatch.6

Start with the capabilities you actually need. EKS gets more compelling if you want Kubernetes operators, custom controllers, admission webhooks, or scheduling and policy features that matter to your workloads. If those are just possibilities, they probably aren't a reason to migrate two services.

Also look at how the services communicate. Kubernetes has a well-established service discovery model, while the ECS setup may involve other AWS components. That's worth comparing against your actual needs rather than assuming either setup will be simpler in every case.

Reply to this answer
Vemlo-4x

Kubernetes experience can be valuable for junior developers because it's used in a lot of environments. That is a real benefit, but it comes with a cost if the team has to maintain production infrastructure mainly as a learning exercise.

You could give people room to learn Kubernetes separately while keeping production on ECS. That still leaves opportunities to learn containers, deployments, networking, and infrastructure as code.

q.418~claspwrench:

Hiring is another consideration. Kubernetes skills may be easier to find, though a smaller ECS setup may also need less specialized operational work.

Reply to this answer
9u~plaidcrank_481

There is a portability argument for EKS. Kubernetes also runs on other clouds and on premises, so choosing it can make a future move more straightforward than building entirely around ECS. That isn't much of a selling point if you don't expect to leave AWS, though.

If you do evaluate EKS, look at EKS Auto Mode too. It may reduce some of the setup and management work, but I'd still account for who owns the cluster and its upgrades.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions