Creating an Amazon ECS Express Mode service - Amazon Elastic Container Service
PrerequisitesWalkthroughsCustomizing
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Creating an Amazon ECS Express Mode service

An Amazon ECS Express Mode service reduces the complexity of deploying containerized applications by providing sensible defaults and automating the configuration of supporting Amazon services. Instead of managing configuration parameters across multiple services, an Express Mode service requires only a container image, task execution role and infrastructure role to get started.

After your deployment completes you will be returned a unique URL for your application. You can find the service you just deployed in Clusters, and if you did not specify a cluster it will be in the Default cluster.

Prerequisites

Before creating an Express Mode service, ensure you have one of the following:

  • A container image stored in Amazon ECR.

  • Or a container image stored in a private registry. To use a private registry, configure a Secrets Manager secret. For more information, see Create an Amazon Secrets Manager secret in the Amazon Secrets Manager User Guide.

Note

IAM Roles are also required, but is covered in the Console and CLI guides separately. The Amazon ECS Console has automated flows for role creation.

Walkthroughs

Customizing

When creating an Express Mode service, Amazon ECS selects defaults for your Amazon ECS and other Amazon resources. Customize the application when needed by using the optional parameters. Take advantage of an Express Mode service and customize the following:

  • Service name

  • Amazon ECS Cluster

  • Container settings - port and health check path

  • Environment variables and secrets

  • Custom commands

  • Task role - This role allows your application code (on the container) to use other Amazon services.

    You need this role when your application accesses other Amazon services, such as Amazon S3.

  • Compute resources - CPU and memory allocation

  • Network configuration - subnets and service security group

  • Application Auto Scaling policies - metrics, target values, and task limits

  • CloudWatch Logs configuration

  • Resource tags