AWS Copilot CLI End-of-Support and Future Alternatives
In a previous article, “Accelerating Prototyping with AI Coding Tools Using AWS Copilot CLI,” I introduced the convenience of AWS Copilot CLI. However, Copilot CLI’s end-of-support is now underway.
This article covers the timeline of events leading to end-of-support, the current status, and the migration options being discussed in the community.
What Happened
In November 2024, changes appeared in the AWS Copilot CLI GitHub repository.
PR #5974 added a maintenance mode disclaimer to the README, but just hours later, PR #5975 reverted that change. Around the same time, an AWS blog post announcing “end of support for AWS Copilot CLI, effective February 3, 2025” was discovered in the commit history, but this post was also deleted after publication.
This series of events caused confusion in the community. Official announcements appeared and disappeared, and questions like “Is it really deprecated?” flooded the GitHub Discussions.
Current Status
AWS team member iamhopaul123 stated the following in GitHub Discussion #5925:
We are not actively developing any new features for Copilot but we still do maintenance work.
Here are the facts that can be confirmed at this point:
- New feature development has stopped, and the project has transitioned to maintenance mode
- There are reports that AWS representatives confirmed the end-of-support at an AWS Summit
- The GitHub repository has not been archived and remains accessible
- AWS official documentation still references Copilot
History of ECS Deployment Tool Deprecations
The deprecation of Copilot CLI is the third instance of AWS deprecating an ECS deployment tool.
| Tool | Repository | Status |
|---|---|---|
| fargate-cli | awslabs/fargatecli | Archived. Recommends migrating to Copilot CLI |
| amazon-ecs-cli | aws/amazon-ecs-cli | Archived. Recommends migrating to Copilot CLI |
| copilot-cli | aws/copilot-cli | Maintenance mode. No new feature development |
Both fargate-cli and amazon-ecs-cli direct users to “use Copilot CLI,” yet Copilot CLI itself is now heading toward end-of-support.
Additionally, AWS Proton, which has been mentioned as a potential alternative, is also scheduled for end-of-support on October 7, 2026.
Migration Options Discussed in the Community
Various migration paths are being discussed in GitHub Discussions and on Reddit.
Reusing CloudFormation Templates Directly
This approach reuses the CloudFormation templates that Copilot generated as-is.
| Tool | Features | Caveats |
|---|---|---|
| Sceptre | Multi-stack orchestration, dependency management, CI/CD friendly | Learning curve for configuration structure |
| AWS Rain | Lightweight. Deploy CloudFormation templates directly with rain deploy | Reports that the maintainer has left AWS. No native multi-stack orchestration |
Migrating to IaC Tools
| Tool | Features |
|---|---|
| AWS CDK | AWS-native. Define infrastructure in TypeScript, Python, etc. |
| Terraform / OpenTofu | Multi-cloud support. Can import CloudFormation stacks |
| SST | TypeScript-based. Focused on developer experience |
| Pulumi | Define infrastructure in general-purpose programming languages |
Some have raised concerns about Terraform’s pricing model, but others point out that costs can be kept low by using GitHub Actions + S3 for state storage instead of Terraform Cloud’s hosted state management. OpenTofu is an open-source fork of Terraform that can be used without licensing concerns.
Impact on Prototyping Use Cases
Regarding the “AI coding tools + Copilot CLI” prototyping workflow introduced in the previous article, here’s how things stand:
It can still be used for now. Copilot CLI continues to work in environments where it’s already installed, and the copilot init → copilot app delete cycle still functions. Since prototypes are built to be short-lived and disposable, the long-term maintenance risk is low, making this the use case least affected by end-of-support.
However, if there are breaking changes on the AWS service side that Copilot depends on, fixes may not be provided. Whether to adopt Copilot for new projects requires careful consideration of this risk.
Summary
AWS Copilot CLI was a tool that dramatically simplified deployments to ECS/Fargate. However, new feature development has stopped and it is heading toward end-of-support. The back-and-forth of official announcements caused confusion, but the maintenance mode status itself has been acknowledged by an AWS team member.
Teams using Copilot in production should start considering migration plans. If you want to keep using your CloudFormation templates as-is, Sceptre is a strong option. If you’re migrating to an IaC tool, CDK and Terraform / OpenTofu are leading candidates.
That’s all from the Gemba, where I summarized the future of AWS Copilot CLI.