Amazon Elastic Container Service ( Amazon ECS )

A container management service to run, stop, and manage Docker containers on a cluster.

ECS can be used to create a consistent deployment and build experience, manage, and scale batch and Extract-Transform-Load (ETL) workloads, and build sophisticated application architectures on a microservices model.

Amazon ECS is a regional service.

Features

You can create ECS clusters within a new or existing VPC.

After a cluster is up and running, you can define task definitions and services that specify which Docker container images to run across your clusters.

Components

Your application components must be architected to run in containers ー containing everything that your software application needs to run: code, runtime, system tools, system libraries, etc.

Containers are created from a read-only template called an image.

Images are typically built from a Dockerfile, a plain text file that specifies all of the components that are included in the container. These images are then stored in a registry from which they can be downloaded and run on your cluster.

When you launch a container instance, you have the option of passing user data to the instance. The data can be used to perform common automated configuration tasks and even run scripts when the instance boots.

Task Components

Task definitions specify various parameters for your application. It is a text file, in JSON format, that describes one or more containers, up to a maximum of ten, that form your application.

Task definitions are split into separate parts:

Task family – the name of the task, and each family can have multiple revisions.

IAM task role – specifies the permissions that containers in the task should have.

Network mode – determines how the networking is configured for your containers.

Container definitions – specify which image to use, how much CPU and memory the container are allocated, and many more options.

Volumes – allow you to share data between containers and even persist the data on the container instance when the containers are no longer running.

Task placement constraints – lets you customize how your tasks are placed within the infrastructure.

Launch types – determines which infrastructure your tasks use.

Tasks and Scheduling

A task is the instantiation of a task definition within a cluster. After you have created a task definition for your application, you can specify the number of tasks that will run on your cluster.

Each task that uses the Fargate launch type has its own isolation boundary and does not share the underlying kernel, CPU resources, memory resources, or elastic network interface with another task.

The task scheduler is responsible for placing tasks within your cluster. There are several different scheduling options available.

REPLICA — places and maintains the desired number of tasks across your cluster. By default, the service scheduler spreads tasks across Availability Zones. You can use task placement strategies and constraints to customize task placement decisions.

DAEMON — deploys exactly one task on each active container instance that meets all of the task placement constraints that you specify in your cluster. When using this strategy, there is no need to specify a desired number of tasks, a task placement strategy, or use Service Auto Scaling policies.

You can upload a new version of your application task definition, and the ECS scheduler automatically starts new containers using the updated image and stop containers running the previous version.

Clusters

When you run tasks using ECS, you place them in a cluster, which is a logical grouping of resources.

Clusters are Region-specific.

Clusters can contain tasks using both the Fargate and EC2 launch types.

When using the Fargate launch type with tasks within your cluster, ECS manages your cluster resources.

When using the EC2 launch type, then your clusters are a group of container instances you manage. These clusters can contain multiple different container instance types, but each container instance may only be part of one cluster at a time.

Before you can delete a cluster, you must delete the services and deregister the container instances inside that cluster.

Services

ECS allows you to run and maintain a specified number of instances of a task definition simultaneously in a cluster.

In addition to maintaining the desired count of tasks in your service, you can optionally run your service behind a load balancer.

There are two deployment strategies in ECS:

Rolling Update

This involves the service scheduler replacing the current running version of the container with the latest version.

The number of tasks ECS adds or removes from the service during a rolling update is controlled by the deployment configuration, which consists of the minimum and maximum number of tasks allowed during a service deployment.

Blue/Green Deployment with AWS CodeDeploy

This deployment type allows you to verify a new deployment of a service before sending production traffic to it.

The service must be configured to use either an Application Load Balancer or Network Load Balancer.

Container Agent

The container agent runs on each infrastructure resource within an ECS cluster.

It sends information about the resource’s current running tasks and resource utilization to ECS, and starts and stops tasks whenever it receives a request from ECS.

Container agent is only supported on Amazon EC2 instances.

AWS Fargate

You can use Fargate with ECS to run containers without having to manage servers or clusters of EC2 instances.

You no longer have to provision, configure, or scale clusters of virtual machines to run containers.

Fargate with ECS is currently only available in the following Regions:

Region Name

Region

US East (N. Virginia)

us-east-1

US East (Ohio)

us-east-2

US West (N. California)

us-west-1

US West (Oregon)

us-west-2

EU (Ireland)

eu-west-1

EU (London)

eu-west-2

EU (Frankfurt)

eu-central-1

Asia Pacific (Tokyo)

ap-northeast-1

Asia Pacific (Seoul)

ap-northeast-2

Asia Pacific (Singapore)

ap-southeast-1

Asia Pacific (Sydney)

ap-southeast-2

Task Definitions for Fargate Launch Type

Fargate task definitions require that the network mode is set to awsvpc. The awsvpc network mode provides each task with its own elastic network interface.

Fargate task definitions require that you specify CPU and memory at the task level.

Fargate task definitions only support the awslogs log driver for the log configuration. This configures your Fargate tasks to send log information to Amazon CloudWatch Logs.

Task storage is ephemeral. After a Fargate task stops, the storage is deleted.

Put multiple containers in the same task definition if:

Containers share a common lifecycle.

Containers are required to be run on the same underlying host.

You want your containers to share resources.

Your containers share data volumes.

Otherwise, define your containers in separate tasks definitions so that you can scale, provision, and deprovision them separately.

Task Definitions for EC2 Launch Type

Create task definitions that group the containers that are used for a common purpose, and separate the different components into multiple task definitions.

After you have your task definitions, you can create services from them to maintain the availability of your desired tasks.

For EC2 tasks, the following are the types of data volumes that can be used:

Docker volumes

Bind mounts

Private repositories are only supported by the EC2 Launch Type.

Monitoring

You can configure your container instances to send log information to CloudWatch Logs. This enables you to view different logs from your container instances in one convenient location.

With CloudWatch Alarms, watch a single metric over a time period that you specify, and perform one or more actions based on the value of the metric relative to a given threshold over a number of time periods.

Share log files between accounts, monitor CloudTrail log files in real time by sending them to CloudWatch Logs.

Tagging

ECS resources, including task definitions, clusters, tasks, services, and container instances, are assigned an Amazon Resource Name (ARN) and a unique resource identifier (ID). These resources can be tagged with values that you define, to help you organize and identify them.

Pricing

With Fargate, you pay for the amount of vCPU and memory resources that your containerized application requests. vCPU and memory resources are calculated from the time your container images are pulled until the Amazon ECS Task terminates.

There is no additional charge for EC2 launch type. You pay for AWS resources (e.g. EC2 instances or EBS volumes) you create to store and run your application.

Limits

Resource

Default Limit

Number of clusters per region, per account

1000

Number of container instances per cluster

1000

Number of services per cluster

500

Number of tasks using the EC2 launch type per service (the desired count)

1000

Number of tasks using the Fargate launch type, per region, per account

50

Number of load balancers per service

1

Number of tasks launched (count) per run-task

10

Number of container instances per start-task

10

Task definition max containers

10

Maximum layer size of an image used by a task using the Fargate launch type

4 GB

Maximum size of a shared volume used by multiple containers within a task using the Fargate launch type

AWS Certified Solutions Architect is consistently among the top paying IT certifications in the world, considering that Amazon Web Services is the leading cloud services platform with almost 50% market share! Earn over $150,000 per year with an AWS certification!

Subscribe to our newsletter for more helpful AWS training notes and blogs like this and answer as many AWS practice exams as you can. 🙂