ECS to EKS,
without rebuilding your pipeline.
Qovery runs EKS in the AWS account you already own. Your task definitions become Kubernetes services, your CI keeps pushing to ECR, and only the deploy step changes.
“Within a few days, we had something running that replicates our previous setup but with multiple environments, greater control, best practices in place, extensibility, and future-proof capabilities.”
“We liked the ease of a managed platform, and we knew AWS meant skills and effort we did not have spare - that is why we kept putting the migration off. We do not regret doing it with Qovery. Deployments that took me over two hours now take 30 minutes.”
ECS is a good orchestrator. It just isn’t Kubernetes.
Nobody leaves ECS because it broke. They leave when the roadmap needs something only Kubernetes has, and nobody on the team wants to become the person who runs it.
The ecosystem assumes Kubernetes
Vendor Helm charts, operators, KEDA, Argo CD, policy engines and most observability agents ship for Kubernetes first and ECS rarely or never. On ECS each of those becomes a rebuild, a sidecar or a decision not to adopt the tool at all.
On Qovery, running in the AWS account you already own:
A standard EKS cluster that takes Helm charts and Terraform services next to your applications, with Karpenter, autoscaling and core add-ons already managed.
Task definitions only run on AWS
A task definition is an AWS artifact. The day a customer asks for a deployment in their own cloud, or a second provider lands on the roadmap, nothing you wrote for ECS travels with you.
On Qovery, running in the AWS account you already own:
The same services and the same deployment workflow on EKS today, and on GCP, Azure, Scaleway or an existing cluster when you need them.
Fargate draws a hard line on some workloads
Fargate has no GPUs, no privileged containers and no host networking, so inference, agents with system access and some security tooling end up on EC2 capacity you manage yourself, with a second operating model next to the first.
On Qovery, running in the AWS account you already own:
GPU node pools per service and EC2 node pools sized by Karpenter, on one cluster and one workflow.
Environments are something you script
ECS has no notion of an environment. A staging copy or a preview per pull request is Terraform someone writes and maintains, and non-production keeps running all night unless someone remembers to stop it.
On Qovery, running in the AWS account you already own:
An environment per pull request created on open and removed on merge, cloneable environments, and non-production that stops on a schedule.
Four steps, and ECS keeps serving the whole time.
Nothing here touches your ECS services. You move one service, shift its traffic, and repeat.
- 01
A CloudFormation stack gives Qovery a role it can use to provision an EKS cluster in your own account, in the same VPC as your ECS services or a peered one, so RDS, ElastiCache and security groups keep working. About twenty minutes. Already run EKS? Install Qovery on that cluster instead. Talk to a migration engineer before you connect anything.
- 02
One command teaches your coding agent how to describe a deployment in Qovery’s own terms. Nothing is deployed at this point.
- 03
The agent reads your Dockerfiles and the task definitions or Terraform already in your repository, then proposes one Qovery service per ECS service: image, CPU and memory, ports, variables, secrets, health checks and scheduled tasks. Your databases stay where they are. You approve the plan before a single resource is created.
- 04
Your CI keeps building, testing and pushing to Amazon ECR. The last step changes from aws ecs update-service to a Qovery deploy of the same image tag, or you let a git push trigger it. Then shift traffic with weighted Route 53 records and keep ECS as the rollback until you trust the new path.
- 05Optional
Take this first or last. A Qovery staff solution engineer reviews the cluster and environment layout with your team, and the things that bite ECS teams on Kubernetes: CPU and memory requests, pod IP planning in the VPC, static egress IPs your partners allowlist, and which services to move last.
- network
- same VPC as ECS, or peered
- cluster
- EKS, Kubernetes up to 1.35
- access
- a role scoped to Qovery
Works with any coding agent that reads skills. Nothing is deployed at this point.
api Dockerfile 1 vCPU / 2 GB from task def worker Dockerfile 0.5 vCPU / 1 GB from task def scheduler cron 2 scheduled tasks database PostgreSQL 16 Amazon RDS, connected as is
Nothing has been created yet. You approve the plan first.
Replaces aws ecs update-service. Build, test and the ECR push stay as they are.
- cluster
- node pools, Spot policy, pod IPs
- workload
- requests and limits, probes, cron
- network
- egress IPs, VPC peering, DNS cutover
to a cluster in your AWS account. From there each service comes up on EKS next to its ECS twin, only the deploy line of your CI changes, and ECS keeps serving traffic until you move it.
The AWS bill barely moves. The hours are what change.
ECS charges nothing for orchestration. EKS adds $0.10 per cluster per hour, about $73 a month, and $0.60 per hour if a cluster falls behind into extended support, which Qovery avoids by keeping clusters upgraded. Fargate and EC2 compute cost the same on both. What moves is everything around it: Karpenter packs pods across instance types, interruptible pools run on Spot, and non-production environments stop when nobody uses them.
EKS list prices from aws.amazon.com/eks/pricing, checked November 2026. Your bill depends on cluster count, node shapes, Spot share and region, and a migration engineer will model it against your current ECS spend before you commit to anything.
Four things ECS does not give you, without a platform team to run them.
Moving to EKS is only worth it for what Kubernetes adds. These are the four that ECS teams ask for most, and none of them needs someone on your team to become the cluster owner.
Bin-packing across instance types
ECS capacity providers scale groups of instances you picked in advance. On EKS, Karpenter looks at the pods waiting to run and picks the instance types that fit them, then consolidates nodes when load drops. Qovery runs Karpenter for you and keeps web services on on-demand capacity while interruptible pools use Spot.
An environment per pull request
On ECS a preview environment is Terraform someone has to write and keep working. With Qovery each pull request gets its own environment, cloned from a blueprint, and it is removed when the pull request closes.
The Kubernetes ecosystem
Helm charts and Terraform modules deploy next to your services in the same environment, and the tools your vendors ship for Kubernetes work as documented instead of being adapted for ECS.
The same workflow beyond AWS
The services you define for EKS deploy the same way to GCP, Azure, Scaleway or a cluster you already run. You do not need that on day one, but it means the next cloud is a cluster to connect, not a second migration.
Our control plane. Your AWS account, your bill.
Qovery sits above the infrastructure and never owns it. The EKS cluster, the node pools and every database stay in the AWS account you already hold, under your IAM and your Savings Plans, and AWS invoices you directly.
- We do not take a cut of your AWS spend. A flat subscription, whether your bill is $2k or $200k.
- Idle nodes, oversized requests and preview environments left running get flagged so you stop paying for them.
- You already own the AWS account. What changes is that the orchestrator becomes standard Kubernetes, and someone other than your team keeps it upgraded.
Not sure which AWS services fit your workload? A solution engineer will map it with you.
Stop paying Qovery and the cluster keeps running - it is standard EKS in your account.
Your first service on EKS,
with the pipeline you already have.
Same AWS account, same VPC, same ECR images. Nothing you do here touches your ECS services until you decide to shift their traffic, and you can shift it back.
Qovery is an AWS ISV Accelerate partner, available on AWS Marketplace. Spend transacts through your existing AWS agreement and counts toward an Enterprise Discount Program commitment.
View on AWS Marketplace →ECS to EKS
Something not covered here? Talk to a migration engineer.
How long does an ECS to EKS migration take?
Does Qovery convert our ECS task definitions automatically?
Do we have to rebuild our CI/CD pipeline?
Will migrating disrupt our running ECS services?
Which Kubernetes version will we run?
Is EKS more expensive than ECS?
What happens if we stop using Qovery?
Can we buy Qovery through AWS Marketplace?
Will Qovery deploy into our existing VPC?
How does every ECS primitive map to EKS?
Watch the move
Other migration paths
Before you decide
- Migrate from ECS to EKS without rebuilding your deployment pipeline
- ECS vs EKS in 2026: cost and operational overhead for a 10-person team
- The ECS limits AWS won’t raise, and when they matter
- Migrating from ECS to EKS: a complete guide
- AWS Fargate vs Kubernetes (EKS): cost, limits and when to switch
- AWS ECS vs EKS vs Elastic Beanstalk