Container application workflows and support
AWS Copilot CLI simplified the deployment and operation of containerized applications on Amazon ECS and AWS App Runner.
How it works
- Initialize an application and create a service. A service is the application component to deploy.
- Define its configuration in a manifestA configuration file that describes a service's desired settings., a file describing the desired service settings.
- Deploy the service to an environmentA set of resources shared by the services deployed to it.. The environment contains resources shared by its services.
- Copilot uses AWS CloudFormation stacksA collection of AWS resources managed as a single unit. to create application and service resources. A stack is a collection of resources managed as a unit. Copilot can also set up a CodePipeline deployment pipelineA workflow that describes how software changes move through a release process., a workflow that releases changes pushed to a Git repository.
Copilot offered these workload patterns:
| Pattern | Use |
|---|---|
| Load Balanced Web Service | Internet-facing ECS Fargate application with an Application Load Balancer. |
| Request-Driven Web Service | Web application on App Runner. |
| Backend Service | Internal service inside a virtual private cloudA logically isolated virtual network for AWS resources. (VPC), an isolated virtual network, without a public endpoint. |
| Worker Service | Processes messages from Amazon SQS queues, which hold messages for consumers. |
| Scheduled Job | Runs containerized tasks on a schedule. |
| Static Site | Hosts a static website using CloudFront and an S3 bucket. |
Exam cues
- If the question says a team needs a legacy CLI workflow for container applications, think AWS Copilot, because it simplified deployment on ECS and App Runner.
- If the question says an existing Copilot application needs a supported deployment path, think ECS Express Mode or AWS CDK, because AWS describes both as migration options.
- If the question says a team wants to manage existing Copilot infrastructure directly, think CloudFormation templates and stacks, because the team can adopt the generated resources.
Remember
- AWS support for Copilot CLI ended on June 12, 2026. AWS no longer provides updates, security patches or technical support.
- Existing deployments continue to function without ongoing maintenance.
- As of November 2026, App Runner is closed to new customers; existing customers can continue using it.
Trap: End of support does not mean existing deployments immediately stop working.
From the AWS docs (20)
- AWS Copilot CLI simplified building, releasing and operating containerized applications on Amazon ECS and AWS App Runner.
- A typical Copilot deployment initializes an application, creates a service and deploys to an environment using a manifest.
- A Copilot environment contains resources shared by the services deployed to it.
- Copilot uses AWS CloudFormation stacks to create application and service resources.
- A CloudFormation stack is a collection of AWS resources managed as a single unit.
- A pipeline describes how software changes go through a release process.
- A virtual private cloud is a logically isolated virtual network for AWS resources.
- An Amazon SQS queue stores messages sent by producers for consumers to receive.
- The Copilot Load Balanced Web Service pattern runs internet-facing applications on ECS Fargate with an Application Load Balancer.
- The Copilot Request-Driven Web Service pattern runs web applications on AWS App Runner.
- The Copilot Backend Service pattern runs internal services in a VPC without public endpoints.
- The Copilot Worker Service pattern processes messages from Amazon SQS queues.
- Copilot scheduled jobs run containerized tasks on a schedule.
- The Copilot Static Site pattern hosts a static website using a CloudFront distribution and an S3 bucket.
- AWS App Runner is closed to new customers; existing customers can continue to use it.
- Copilot can set up CodePipeline deployment pipelines that build code when changes are pushed to a Git repository.
- AWS Copilot CLI reached end of support on June 12, 2026; AWS no longer provides updates, security patches or technical support.
- Existing Copilot deployments continue to function after end of support without ongoing maintenance.
- AWS describes Amazon ECS Express Mode and AWS CDK as migration options for Copilot applications.
- Teams can adopt and manage the CloudFormation templates and stacks generated by Copilot.
Flashcards
Nothing to review here right now. Pick other topics or another filter.
·
All 7 cards as a list
Which CLI helped developers deploy containerized applications to Amazon ECS?
AWS Copilot CLI. AWS support ended on June 12, 2026.
What resources do services in an AWS Copilot environment share?
The environment contains resources shared by its deployed services.
A team needs to deploy an internet-facing container application to Amazon ECS using AWS Copilot. Which service pattern fits?
The Load Balanced Web Service pattern runs the application on ECS Fargate with an Application Load Balancer.
A team wants to move away from AWS Copilot after support ended. Which deployment options does AWS describe?
Amazon ECS Express Mode and AWS CDK. Teams can also manage Copilot-generated CloudFormation stacks.
What are the main steps in an AWS Copilot container application deployment?
Initialize an application, create a service, and deploy it to an environment using a manifest.
Which AWS Copilot pattern processes messages from Amazon SQS queues?
Worker Service.
A team used AWS Copilot for an internal service without a public endpoint. Which pattern fits?
Backend Service. It runs inside a VPC without a public endpoint.