Shulou(Shulou.com)05/31 Report--

This article introduces you how to understand AWS ECS, the content is very detailed, interested friends can refer to, hope to be helpful to you.

Introduction to ECS:

Elastic container service (ECS): a highly scalable and fast container management service that can quickly run, stop, and manage containers on a docker cluster.

ECS can launch containers on fargate and EC2S.

With ECS, you can start and stop container-based applications by simply calling API, get cluster status from centralized services, and access many familiar EC2 functions.

You can use ECS to plan the placement of containers in the cluster based on resource requirements, isolation policies, and availability requirements. With ECS, you don't have to operate your own cluster management and configuration management system, and you don't have to worry about extending the management infrastructure.

ECS can be used to create a consistent deployment and build experience, manage and extend batch and extract-transform-load (ETL) workloads, and build advanced application architectures on microservice models.

Functions of ECS:

ECS is a regional service that simplifies running application containers in a highly available manner in multiple availability zones within the zone. An ECS cluster can be created in a new or existing VPC, and after the cluster is up and running, you can define task definitions and services for the specified image that the docker container runs.

The following is the architecture of an ECS environment started with the fargate type:

Containers and Images

To deploy the application in ECS, you must build the application components to run in the container.

Task definition

A task definition is a text file in JSON format that describes one or more containers (up to 10) that make up the application. You can call it the blueprint of the application.

The task definition specifies parameters for the application:

Which container to use, which startup type, the port opened by the application, and which data volumes are used by the container in the task.

The specific parameters of the task definition depend on the startup type.

The following is an example of the task definition initiated by the nginx web container (using the fargate startup type)

{"family": "webserver", "containerDefinitions": [{"name": "web", "image": "nginx", "memory": "100th", "cpu": "99" >

Tasks and plans

A task is an instantiation of a task definition in a cluster. After creating a task definition on ECS, you can specify the number of tasks running on the cluster.

Tasks that use the fargate startup type have their own isolation boundaries and do not share the underlying kernel, CPU, memory, or resilient network interfaces with other tasks.

The task scheduler is responsible for putting tasks into the cluster.

Cluster

When ECS runs a task, you need to put the task on the cluster, which is a logical grouping of resources.

When tasks in the cluster use the fargate startup type, the cluster is the ECS that manages the cluster resources. When using the EC2 startup type, the cluster is ECS managed by a set of container instances.

The ECS container instance is an EC2 instance that runs the ECS container agent. ECS downloads the image in the specified registry and starts the image in the cluster.

Container agent

The container agent runs on every infrastructure on the ECS cluster. Send ECS information about the task definition and resource utilization that the resource is running, and when receiving a request from ECS, stop the container.

On how to understand AWS ECS to share here, I hope that the above content can be of some help to you, can learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.