kubernetesPractitioner

Navigating the End of AWS Copilot CLI Support: What Comes Next?

5 min read AWS Containers BlogMar 6, 2026Reviewed for accuracy

Practitioner — Hands-on experience recommended

AWS Copilot CLI has been a valuable tool for simplifying the deployment of containerized applications on Amazon ECS and AWS App Runner. However, with its end of support set for June 12, 2026, it’s crucial to understand how this impacts your current workflows and what alternatives are available. The Copilot CLI streamlined the process of initializing applications, creating services, and deploying them using a declarative manifest file, which made it easier to manage environments and resources.

In a typical Copilot deployment, you would initialize an application and create a service, specifying parameters such as the application name, service name, and service type—be it a Load Balanced Web Service or a Request-Driven Web Service. For instance, you might run a command like copilot init to set up a load-balanced web service, defining the Dockerfile and port. This ease of use is what made Copilot appealing, but as support wanes, you need to pivot to alternatives like Amazon ECS Express Mode or AWS Cloud Development Kit (CDK) Layer 3 for ongoing projects.

As you transition away from Copilot, keep in mind that the shift requires careful planning. Ensure you understand the architecture of your existing services and how to replicate them in the new frameworks. This is not just about moving code; it’s about rethinking how you deploy and manage your applications in a production environment. The end of support for AWS Copilot CLI is a significant change, and it’s essential to adapt your strategies accordingly.

Key takeaways

→Plan your migration to alternatives like Amazon ECS Express Mode or AWS CDK Layer 3.
→Use `copilot init` to set up load-balanced web services before transitioning.
→Understand the implications of the end of support date: June 12, 2026.
→Reassess your deployment strategies as you move away from Copilot.
→Familiarize yourself with the parameters and behaviors of the new tools.

Why it matters

The end of support for AWS Copilot CLI means you must transition to alternatives to avoid disruptions in your deployment processes. This shift impacts how you manage containerized applications, which are critical for modern cloud architectures.

Code examples

Bash

1# Initialize the application and create a load-balanced web service
2
3copilot init \ 
4--app my-app \ 
5--name loadbalanced-svc \ 
6--type "Load Balanced Web Service" \ 
7--dockerfile ./Dockerfile \ 
8--port 80

Bash

1# Create a Request-driven web service in the same app
2
3copilot svc init \ 
4--name request-driven-svc \ 
5--app my-app \ 
6--svc-type "Request-Driven Web Service" \ 
7--ingress-type "Internet" \ 
8--dockerfile "./Dockerfile"

YAML

1name: loadbalanced-svc
2 type: Load Balanced Web Service
3
4image:
5  build: Dockerfile
6  port: 80
7
8cpu: 256
9memory: 512
10count: 1
11
12http:
13  path: '/'
14
15variables:
16  LOG_LEVEL: info