This article is an overview for beginners with\u00a0Amazon Elastic Container Service (Amazon ECS).<\/strong> VTI Cloud will refer to concepts, core terms, simple architectural diagrams, and summary examples.<\/p>\n To understand Amazon ECS, we must first\u00a0understand the concept\u00a0<\/span>of Docker.<\/p>\n Docker\u00a0<\/strong>\u2013 a run time container is a software \u2013 a tool that allows building, deploying, packaging applications easily and quickly compared to the previous virtualization architecture. Containers\u00a0<\/strong>run\u00a0by Run Time Containers\u00a0<\/em>such as Docker are a kind of fully packaged software standard library, the source code required to run applications with high stability, availability without concern for physical infrastructure. Many different containers can be run on a host, as long as the host has Docker software installed.<\/p>\n As you can see in the diagram above, Docker is different from normal Virtualization.\u00a0Docker<\/strong>\u00a0is located between the application and the server operating system (OS). Docker can share the host operating system on multiple “Containers” instead of asking each person to have and run the operating system separately.<\/p>\n Each container is full of what an application needs \u2013 for example, certain versions of a language or library \u2013 and no more than it needs. Many containers can be used for different parts of the application if you wish and they can be set up to communicate with each other as needed.<\/p>\n This allows packing its application into a reusable module, which can run on any machine available. This enables more detailed resource allocation and can minimize the amount of CPU or memory resources wasted.<\/p>\n By using the docker container specified to run\u00a0production\u00a0<\/span>code, make sure that the dev and production environment are the same.<\/strong><\/em><\/p>\n As your application grows, managing deployment, structure, schedule, and expansion of containers for applications quickly becomes very complicated. This is when the container management service was born. It aims to allow simple configuration options and handle non-professional work while you focus on application programming.<\/p>\n Amazon\u00a0<\/span>Elastic Container Service (Amazon ECS)<\/span><\/a>, as defined by AWS is<\/p>\n A highly scalability container management service that easily runs, stops, or manages docker containers in a cluster. You can host a serverless infrastructure by running a service or task using Fargate launch type or using EC2 launch type to run EC2 instances.<\/p>\n<\/blockquote>\n Amazon ECS has been compared to\u00a0Kubernetes,<\/a>\u00a0<\/span>Docker Swarm<\/span>,<\/a>\u00a0and\u00a0Azure\u00a0Container Instances.<\/a><\/span><\/p>\n Amazon ECS\u00a0<\/strong>runs containers in clusters of\u00a0many Amazon EC2 instances<\/strong> pre-installed with Docker. It handles container installation, scalability, monitoring, and management of these instances (launch\/stop) through both APIs and AWS management consoles.<\/p>\n Amazon Elastic Container Service enables to simplify the view of EC2 instances into a resource pool, such as CPU and memory.<\/p>\n You can use Amazon ECS to install\u00a0containers<\/span>\u00a0through clusters\u00a0and rely on the<\/span>\u00a0resources you need, independent policies, or the ability to change. With Amazon ECS, you don’t have to operate your own cluster management and configuration management system or worry about expanding your management infrastructure.<\/p>\n Amazon ECS is a region-based service that simplifies runs container applications across multiple A’s in the same region. You can create an ECS cluster inside a new or old VPC. After a cluster is initially and run, you can define the\u00a0task and services that it defines the Docker\u00a0container\u00a0<\/span>image that will run through clusters.<\/p>\n Here we come to two new groups of terms:<\/p>\n Task Definition<\/strong>,\u00a0Task<\/strong>, v\u00e0\u00a0Service.<\/strong><\/p>\n<\/li>\n ECS Container Instance<\/strong>,\u00a0<\/em>ECS Container Agent<\/strong>, v\u00e0\u00a0Cluster<\/strong>.<\/p>\n<\/li>\n<\/ul>\n This is a text file (JSON format). It will describe 1 or more containers (up to 10) to form your application. Task definition will specify a few parameters for the application, such as which container will be used, image used, launch type used, the configuration of the container (CPU and memory)), open port, and what data volume will be created with the container in the task …<\/p>\n The parameter in the task definition depends on which launch type is being used. An example of a task definition that contains a container used to run an NGINX web server that uses the Fargate launch type.<\/strong><\/p>\n {<\/span><\/span><\/p>\n “family”: “webserver”,<\/span><\/span><\/p>\n<\/div>\n “containerDefinitions”: [<\/span><\/span><\/p>\n<\/div>\n {<\/span><\/span><\/p>\n<\/div>\n “name”: “web”,<\/span><\/span><\/p>\n<\/div>\n “image”: “nginx”,<\/span><\/span><\/p>\n<\/div>\n “memory”: “100”,<\/span><\/span><\/p>\n<\/div>\n “cpu”: “99”<\/span><\/span><\/p>\n<\/div>\n },<\/span><\/span><\/p>\n<\/div>\n ],<\/span><\/span><\/p>\n<\/div>\n “requiresCompatibilities”: [<\/span><\/span><\/p>\n<\/div>\n “FARGATE”<\/span><\/span><\/p>\n<\/div>\n ],<\/span><\/span><\/p>\n<\/div>\n “networkMode”: “awsvpc”,<\/span><\/span><\/p>\n<\/div>\n “memory”: “512”,<\/span><\/span><\/p>\n<\/div>\n “cpu”: “256”,<\/span><\/span><\/p>\n<\/div>\n }<\/span><\/span><\/p>\n A task is the initial creation of a task definition inside the cluster. Many different Tasks can be created by a Task Definition, depending on your needs, but specify a certain number of tasks. However, these tasks may be the same.<\/p>\n For each task using the Fargate launch type, there is a separate boundary and does not share kernel, CPU resources, memory, or elastic network interface with other tasks.<\/p>\n Amazon ECS task scheduler is responsible for replacing tasks inside the cluster. There are a few different ways to schedule a task<\/p>\n Service schedule<\/p>\n<\/li>\n Manually running task<\/p>\n<\/li>\n Running task on a cron-like schedule<\/p>\n<\/li>\n Custom scheduler<\/p>\n<\/li>\n<\/ul>\n Determine the minimum and maximum of one or more Tasks from a Task Definition that runs at any certain time.<\/span><\/p>\n Now that service is available, Service Tasks need to be run somewhere to be accessible. It needs to be placed on\u00a0a Cluster\u00a0<\/strong>and the container management service will handle it when running on one or more\u00a0ECS Container Instance(s).<\/strong><\/p>\n In the image below is\u00a0an EC2 instance<\/strong> that has a\u00a0docker engine<\/strong>\u00a0installed and\u00a0an ECS Container Agent<\/strong>\u00a0inside. An ECS Container Instance can run multiple Tasks of the same or different breed, from the same or different Services.<\/p>\n The agent is used to support exchange connections between ECS and instances, provide information about running containers, and manage newly created containers.<\/p>\n As seen above, a Cluster is a group of ECS Container Instances. Amazon ECS handles the logic of scheduling, maintaining, and processing scalability requests for these instances. Tasks running on ECS are always in the cluster.<\/p>\n When tasks are run on Fargate, cluster resources are managed by Fargate. When using the EC2 launch type, clusters are ECS Container Instance groups (powered by EC2 instances).<\/span><\/p>\n See more on Cluster in AWS Documentation:What is Amazon Elastic Container Service? – Amazon Elastic Container Service<\/a><\/span><\/p>\n<\/blockquote>\n A Cluster can run multiple Services. If your product has multiple apps, then you can put some of these apps in a Cluster. This makes it more efficient to use available resources and minimizes setup time compared to traditional management models.<\/p>\n<\/div>\n Amazon ECS loads your image containers from the registry you set up earlier and then runs these images in your cluster:<\/p>\n Cluster there Region-specific<\/span>.<\/p>\n<\/li>\n Cluster can contain many tasks using both Fargate launch type and EC2 launch type.<\/p>\n<\/li>\n When tasks use EC2 launch type, clusters can contain many different ECS Container Instances. At the same time, an ECS Container Instance belongs to only one cluster.<\/p>\n<\/li>\n You can create a custom IAM policy for cluster enabled or limit user access to clusters.<\/span><\/p>\n<\/li>\n<\/ul>\n The workload is big, but still wants to save costs<\/strong><\/p>\n<\/li>\n<\/ul>\n When an application needs a high CPU and multiple GB of memory and an optimal desire for AWS costs, it is possible to use clusters of reserved EC2 instances or EC2 spot instances.<\/p>\n You’ll be responsible for maintaining and optimizing this cluster, but the advantage of Amazon EC2 will save quite a bit of cost (when using spot or reserved instance)<\/p>\n Test environment<\/strong><\/p>\n<\/li>\n<\/ul>\n With testing environments that don’t require too much workload, using AWS Fargate serverless services instead of EC2 instance services will help you get the most out of your resources.<\/p>\n The workload environment is small, but occasionally there is a sudden increase (burst)<\/strong><\/p>\n<\/li>\n<\/ul>\n When workloads are small but occasionally have occasional spikes, such as traffic or requests unexpectedly increasing during the day and low at night, using the Fargate launch type will be more advantaged.<\/p>\n Because Fargate can scale up resources from a tiny night container (extremely low cost) for responding to daytime spikes that simply pay for CPU core and GB of on-demand memory.<\/p>\n Large workload, but does not want to consume resources for operation (Overhead cost)<\/strong><\/p>\n<\/li>\n<\/ul>\n Operating a cluster of multiple EC2 instances takes a lot of effort and time, as you must ensure the latest patching, security, and update of docker and ECS Agent instances. At this point, Fargate would be the best option!<\/p>\n The reason is that this serverless service is automatically protected by AWS engineers behind and patches and updates from AWS infrastructure without businesses bothering.<\/p>\n Periodical workload<\/strong><\/p>\n<\/li>\n<\/ul>\n When the system always has to run tasks periodically, such as cron jobs (hourly or occasionally) from the queue, AWS Fargate will provide the most stable support for the system. Instead of having to restart ec2 instances after these tasks while running and still being charged when EC2 instances are turned off, Fargate is only charged while in run mode.<\/p>\n We’ve seen how an application running on Docker can be performed using Task Definition and has a 1:1 relationship with a Service, thereby using Task Definition to create a variety of Task instances.<\/p>\n The service is deployed to a Cluster of ECS Container Instances, providing the pool of resources needed to run and extend the application. Additional Services can be deployed to the same Cluster.<\/p>\n Amazon ECS, or any container management service, will aim to simplify as much as possible, eliminating many of the complexities of operating infrastructure at scale.<\/p>\n As the needs of the system become more complex, container management services will ensure easy management of the system. By using APIs or Management Consoles, you can come up with Task definitions to add new ECS Container Instances as needed. This ensures that there are always a number of Tasks running and all alluring resources intelligently across the Services.<\/p>\n The case study of Deliveroo that leverages the Amazon ECS’s benefits are shown at this link: Deliveroo – Reduce operating costs by more than 50% with AWS | VTI CLOUD<\/a><\/p>\nFirst of all, we have to learn about Docker<\/h2>\n
![\"docker](\"https:\/\/vticloud.io\/wp-content\/uploads\/2021\/02\/docker-vs-vm.png\")
<\/p>\nCompare Docker and Virtualization<\/h3>\n
When the number of containers expands too fast<\/h3>\n
Learn about Amazon ECS<\/h2>\n
\n
![\"container](\"https:\/\/vticloud.io\/wp-content\/uploads\/2021\/02\/container-in-docker.png\")
<\/p>\nAmazon ECS core terminology and architectural diagrams<\/h2>\n
\n
Task Definition<\/h3>\n
Task and Schedule<\/h3>\n
![\"task](\"https:\/\/vticloud.io\/wp-content\/uploads\/2021\/02\/task-in-task-definition.png\")
<\/div>\n\n
![\"overview-service-fargate\"](\"https:\/\/vticloud.io\/wp-content\/uploads\/2021\/02\/overview-service-fargate.png\")
<\/p>\nService<\/h3>\n
![\"service](\"https:\/\/vticloud.io\/wp-content\/uploads\/2021\/02\/service-in-ecs.png\")
<\/p>\nAmazon ECS Container Instances and Amazon ECS Container\u00a0Agents<\/u><\/a><\/h3>\n
![\"fargate](\"https:\/\/vticloud.io\/wp-content\/uploads\/2021\/02\/fargate-ecs.png\")
<\/p>\nCluster<\/h3>\n
![\"cluster](\"https:\/\/vticloud.io\/wp-content\/uploads\/2021\/02\/cluster-amazon-ecs.png\")
<\/p>\n\n
![\"services](\"https:\/\/vticloud.io\/wp-content\/uploads\/2021\/02\/services-in-a-cluster.png\")
<\/p>\n\n
EC2 launch type use cases in Amazon ECS<\/h2>\n
\n
Cases of using Fargate launch type in Amazon ECS<\/h2>\n
\n
\n
\n
\n
Conclusion<\/h2>\n
![\"amazon](\"https:\/\/vticloud.io\/wp-content\/uploads\/2021\/02\/amazon-ecs-cluster.png\")
<\/p>\nReference:\u00a0<\/h3>\n