Amazon ECS Express Mode turns a container image into a deployable web service: provide the image and two IAM roles, and AWS provisions an ECS service and supporting infrastructure, then gives you a service URL. You can start in the ECS console or with the AWS CLI; the right route depends on whether you prefer guided setup or a repeatable command-line workflow.
What you need before you start
- A container image: Store it in Amazon ECR or a private registry. For a private registry, configure a Secrets Manager secret so AWS can access it.
- An AWS account and permissions: Your identity must be allowed to create the service and supporting resources.
- Two IAM roles: The task execution role lets ECS perform startup tasks such as pulling the image and writing logs. The infrastructure role lets ECS provision and manage the supporting resources. The console’s first-run flow can help create roles if suitable ones are not already available. IAM changes can take time to propagate, so an assume-role error immediately after creating a role may be temporary.
- Networking: The CLI tutorial’s default setup expects a VPC with public subnets in the target Region. You can instead supply your own network settings. Confirm that ECS and Fargate are supported in the Region you plan to use.
- AWS CLI, if using the command line: Install and configure it for the intended account and Region.
See AWS’s CLI getting-started guide for the role examples, prerequisites, and current command syntax.
As an Amazon Associate I earn from qualifying purchases.
Choose the console or CLI
Create a service in the ECS console
- Open the Amazon ECS console and choose Express mode.
- Provide or select your container image.
- Select the task execution role and infrastructure role, or use the console’s role-creation option if offered.
- Review any settings you need to change, then choose Create.
- Open the service’s Resources tab to watch provisioning. When deployment completes, find the Application URL.
AWS’s console walkthrough shows the current flow and configurable settings.
Create a service with the AWS CLI
The CLI route is useful when you want the setup represented as a command or incorporated into a workflow. AWS’s tutorial creates the roles first, then calls aws ecs create-express-gateway-service with the primary container image and role ARNs. Its minimal example uses a public NGINX image and the --monitor-resources option.
#1 Best Overall
Follow the official CLI tutorial for the role policies and exact command arguments. The CLI reference cited here showed AWS CLI 2.37.9; verify the current command reference before relying on syntax, since the CLI and service can change.
Understand what the defaults create
The documented CLI example uses 1 vCPU and 2 GB of memory, port 80 for HTTPS traffic, CPU-based autoscaling, and an internet-facing Application Load Balancer in the default VPC’s public subnets. Its URL follows this pattern: https://<service-name>.ecs.<region>.on.aws/. The console walkthrough also lists 1 vCPU and 2 GB, X86_64 architecture, a 60% scaling target, and minimum and maximum task counts of 1 and 20. These are tutorial and console defaults, not sizing advice for every application; inspect the configuration in the path you use and adjust it for your workload.
Express Mode can create an ECS default cluster if needed, Fargate capacity providers, a task definition, and an ECS service with canary deployment and autoscaling. Supporting resources can include an Application Load Balancer and HTTPS listener, target groups, security groups, service-linked roles, an autoscaling target and policy, a service log group, a deployment-failure metric alarm, and an ACM certificate. The resources remain visible and accessible in your AWS account through the console and APIs. AWS documents the full list in Resources created by Express Mode services.
Customize the service for your application
Before creating the service, consider whether the defaults fit your app. The console and API offer settings for:
- Service and cluster names; container port and health-check path.
- Environment variables, secrets, and a custom container command.
- Task role, CPU and memory, and CPU architecture.
- Scaling metric and task-count limits.
- Network configuration, CloudWatch log group and stream prefix, and tags.
- A custom task definition.
If the application calls other AWS services, give it an application task role with only the permissions it needs. This is separate from the task execution role, which handles startup operations such as image pulls and log delivery.
Requirements for a supplied task definition
A task definition used with this flow must include a container named Main, one TCP port mapping with a container port and port name, and FARGATE compatibility. When you supply a task definition, some values are derived from it and cannot also be supplied in the same create call. Check the CLI tutorial for the current constraints before building a custom definition.
Wait for readiness and verify the URL
Provisioning is not complete just because the create request was accepted. In the console, follow progress in the service’s Resources tab. In the CLI, use --monitor-resources when creating, updating, or deleting a service, or run aws ecs monitor-express-gateway-service separately. AWS identifies the service as ready to receive traffic when its status becomes ACTIVE. Then open the Application URL and check that the application responds as expected.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Know what you will pay for
Express Mode itself has no separate charge, but the AWS resources it creates are billed. Cost can include Fargate compute, the Application Load Balancer, CloudWatch logs and metrics, and data transfer. There is no single meaningful service price without assumptions about Region, task size and count, uptime, traffic, and logging volume; estimate those resources for your own configuration using current AWS pricing.
AWS says load balancers can be shared among Express Mode services using the same network configuration, which may reduce load-balancer cost per application as the number of services grows. Actual cost still depends on the resources and usage in your account. The Express Mode overview describes availability, pricing categories, and supported interfaces.
When Express Mode is a good fit
Express Mode is aimed at developers and platform teams who have a container image and want AWS to assemble the service’s supporting infrastructure rather than configuring each component themselves. It offers a faster path to a working service, while still leaving the created resources accessible for inspection and management.
Choose a more hands-on ECS setup when you need to control infrastructure details that Express Mode’s defaults or supported settings do not cover. In either case, review network exposure, scaling behavior, and the full underlying-resource cost—not just the convenience of the deployment path. Express Mode is available through the ECS console, AWS CLI, SDKs, CloudFormation, Terraform, and the AWS Labs MCP Server for Amazon ECS.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
