{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/396c154e4fe644a88ce8975444cdb426\" frameborder=\"0\" width=\"1920\" height=\"1440\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1440,"width":1920,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1440,"thumbnail_width":1920,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/396c154e4fe644a88ce8975444cdb426-a30128c676774b41.gif","duration":3188.800333,"title":"Migrating ECS to EKS Without Freezing Roadmaps","description":"This Loom explains how to migrate workloads from AWS ECS to AWS EKS without freezing the roadmap, using Covree to support a zero downtime approach. The speaker compares ECS and EKS primitives, costs, AWS integration, and Kubernetes ecosystem advantages, then covers when to move off ECS, noting ECS quotas such as 100 target groups per load balancer and a 10 containers per task limit. They describe migration strategies including risky full rewrites, long parallel runs, and a recommended phased preview approach with a cutover window measured in weeks, using AI to generate new EKS Terraform while validating results because AI is not deterministic. A live demo is shown: an ECS hosted app switches load balancer traffic to a new EKS cluster while keeping the same external IP, backed by a prepared plan derived from analyzing the existing ECS Terraform in Covree."}