--- title: Why ECS Outlives Every Convenience Layer AWS Builds On... description: AWS has repeatedly built convenience layers on top of ECS—ECS CLI, Fargate CLI, Copilot, Proton, and App Runner (now in maintenance mode)—and nearly all of... canonical: https://daily.dev/posts/why-ecs-outlives-every-convenience-layer-aws-builds-on-top-of-it-4xnkl9er4 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Why ECS Outlives Every Convenience Layer AWS Builds On Top Of It | daily.dev og:description: AWS has repeatedly built convenience layers on top of ECS—ECS CLI, Fargate CLI, Copilot, Proton, and App Runner (now in maintenance mode)—and nearly all of... og:url: https://daily.dev/posts/why-ecs-outlives-every-convenience-layer-aws-builds-on-top-of-it-4xnkl9er4 og:image: https://api.daily.dev/og/posts/4xnkL9er4.png og:image:alt: Why ECS Outlives Every Convenience Layer AWS Builds On Top Of It og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Why ECS Outlives Every Convenience Layer AWS Builds On Top Of It **[AWS Fundamentals](https://daily.dev/sources/awsfundamentals)** · 9 min read · 21 upvotes · 1 comments ## Summary AWS has repeatedly built convenience layers on top of ECS—ECS CLI, Fargate CLI, Copilot, Proton, and App Runner (now in maintenance mode)—and nearly all of them have been retired or are being sunset, while ECS's core API has remained stable since 2014. The piece argues this happens because these wrappers were growth bets rather than infrastructure other services depend on, contrasting them with survivors like Elastic Beanstalk and Lightsail, which settled into serving existing customer bases instead of chasing new ones. Two tests are proposed for deciding what to build on: whether you can still run the underlying resources if the wrapper disappears, and whether AWS still treats the layer as a growth bet. ECS Express Mode, AWS's newest convenience layer, is flagged as unproven, with early reviews calling it disappointing and opaque compared to CloudFormation-based predecessors. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Is AWS Copilot CLI being deprecated? Yes, AWS announced the end of support for the AWS Copilot CLI, with the sundown scheduled for June 2026. Copilot launched in July 2020 as a deployment wrapper over ECS that generated readable CloudFormation, but AWS is retiring it after it failed to gain the adoption needed to justify continued investment. _Anyone planning ECS deployments around Copilot should track migration guidance on daily.dev before support ends._ ### When does AWS Proton reach end of support? AWS Proton reaches end of support in October 2026. It launched in June 2021 as a managed deployment workflow built on top of ECS primitives, but like other convenience layers in that category it did not gain enough ongoing usage to survive, and the underlying ECS task definitions and services continue running unaffected. _Teams weighing managed AWS deployment tools can follow sunset timelines like this on daily.dev before committing._ ### Has the ECS API changed since Fargate launched in 2017? No, Fargate added a new capacity mode when it launched in 2017 but did not introduce a new API; task definitions and services are still described the same way they were before Fargate existed. ECS itself launched in 2014 and its core API has remained stable since, which is why services built directly against it have avoided the deprecations hitting wrapper tools like Copilot and Proton. _Developers deciding what to build container workloads on can weigh primitive stability like this via daily.dev._ ## Community discussion Top comments from developers on daily.dev. **@ahmetozel** · 0 upvotes > The exit test is the part I would make operational. Owning generated configuration helps, but I would also want a documented path for updating the running service, rotating secrets and rolling back a failed deployment after the wrapper is unavailable. Those are the dependencies that can remain hidden even when the containers keep running. > > For a generated CloudFormation stack, that rehearsal should include stack ownership and drift, rather than assuming an exported template is immediately interchangeable with Terraform or a direct ECS update. A small recovery exercise can reveal which... ## Similar posts on daily.dev - [AWS Launches ECS Express Mode to Simplify Containerised Application Deployment](https://daily.dev/posts/aws-launches-ecs-express-mode-to-simplify-containerised-application-deployment-kcvvkbiqr) · InfoQ · 1 upvotes · 0 comments - [Build production-ready applications without infrastructure complexity using Amazon ECS Express Mode](https://daily.dev/posts/build-production-ready-applications-without-infrastructure-complexity-using-amazon-ecs-express-mode-pqeilpn6q) · AWS · 25 upvotes · 1 comments - [EC2, Lambda, ECS, EKS, and Fargate: How I Learned to Pick the Right AWS Compute Service](https://daily.dev/posts/ec2-lambda-ecs-eks-and-fargate-how-i-learned-to-pick-the-right-aws-compute-service-cpqonz8gj) · Medium · 0 upvotes · 0 comments - [Elastic Beanstalk Cluster Mode: First Look](https://daily.dev/posts/elastic-beanstalk-cluster-mode-first-look-6cn2dmu42) · AWS Fundamentals · 4 upvotes · 0 comments - [Your container runs. Everything around it shouldn’t be your problem.](https://daily.dev/posts/your-container-runs-everything-around-it-shouldn-t-be-your-problem--ogniwsgsz) · The New Stack · 0 upvotes · 0 comments --- Tags: [#cloud](https://daily.dev/tags/cloud), [#aws](https://daily.dev/tags/aws), [#iac](https://daily.dev/tags/iac) [View this post on daily.dev](https://daily.dev/posts/why-ecs-outlives-every-convenience-layer-aws-builds-on-top-of-it-4xnkl9er4) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Why ECS Outlives Every Convenience Layer AWS Builds On Top Of It","url":"https://daily.dev/posts/why-ecs-outlives-every-convenience-layer-aws-builds-on-top-of-it-4xnkl9er4","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/why-ecs-outlives-every-convenience-layer-aws-builds-on-top-of-it-4xnkl9er4"},"datePublished":"2026-09-29T09:25:35.127Z","dateModified":"2026-09-29T09:26:01.739Z","description":"AWS has repeatedly built convenience layers on top of ECS—ECS CLI, Fargate CLI, Copilot, Proton, and App Runner (now in maintenance mode)—and nearly all of...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/05e0d97f12b67218d22d5d712e19bd0d?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/05e0d97f12b67218d22d5d712e19bd0d?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"AWS Fundamentals","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"AWS Fundamentals","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/be6417f59fd84e61a0f596223f09d2d7","url":"https://daily.dev/sources/awsfundamentals"},"commentCount":1,"discussionUrl":"https://daily.dev/posts/why-ecs-outlives-every-convenience-layer-aws-builds-on-top-of-it-4xnkl9er4","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":21},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":1}],"keywords":"cloud,aws,iac","timeRequired":"PT9M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"AWS Fundamentals","item":"https://daily.dev/sources/awsfundamentals"},{"@type":"ListItem","position":3,"name":"Why ECS Outlives Every Convenience Layer AWS Builds On Top Of It"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/why-ecs-outlives-every-convenience-layer-aws-builds-on-top-of-it-4xnkl9er4","comment":[{"@type":"Comment","text":"The exit test is the part I would make operational. Owning generated configuration helps, but I would also want a documented path for updating the running service, rotating secrets and rolling back a failed deployment after the wrapper is unavailable. Those are the dependencies that can remain hidden even when the containers keep running.\nFor a generated CloudFormation stack, that rehearsal should include stack ownership and drift, rather than assuming an exported template is immediately interchangeable with Terraform or a direct ECS update. A small recovery exercise can reveal which resources and deployment assumptions the convenience layer still controls. That makes the primitive-versus-wrapper distinction actionable without needing to predict which product survives.","datePublished":"2026-10-06T18:29:19.658Z","url":"https://daily.dev/posts/4xnkL9er4#c-Ja1NPLmAC","author":{"@type":"Person","name":"Ahmet Özel","url":"https://daily.dev/ahmetozel","image":"https://avatars.githubusercontent.com/u/70992231?v=4"}}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/why-ecs-outlives-every-convenience-layer-aws-builds-on-top-of-it-4xnkl9er4#faq","mainEntity":[{"@type":"Question","name":"Is AWS Copilot CLI being deprecated?","acceptedAnswer":{"@type":"Answer","text":"Yes, AWS announced the end of support for the AWS Copilot CLI, with the sundown scheduled for June 2026. Copilot launched in July 2020 as a deployment wrapper over ECS that generated readable CloudFormation, but AWS is retiring it after it failed to gain the adoption needed to justify continued investment. Anyone planning ECS deployments around Copilot should track migration guidance on daily.dev before support ends."}},{"@type":"Question","name":"When does AWS Proton reach end of support?","acceptedAnswer":{"@type":"Answer","text":"AWS Proton reaches end of support in October 2026. It launched in June 2021 as a managed deployment workflow built on top of ECS primitives, but like other convenience layers in that category it did not gain enough ongoing usage to survive, and the underlying ECS task definitions and services continue running unaffected. Teams weighing managed AWS deployment tools can follow sunset timelines like this on daily.dev before committing."}},{"@type":"Question","name":"Has the ECS API changed since Fargate launched in 2017?","acceptedAnswer":{"@type":"Answer","text":"No, Fargate added a new capacity mode when it launched in 2017 but did not introduce a new API; task definitions and services are still described the same way they were before Fargate existed. ECS itself launched in 2014 and its core API has remained stable since, which is why services built directly against it have avoided the deprecations hitting wrapper tools like Copilot and Proton. Developers deciding what to build container workloads on can weigh primitive stability like this via daily.dev."}}]} ```