{"id":15451,"date":"2023-09-19T13:07:56","date_gmt":"2023-09-19T07:37:56","guid":{"rendered":"https:\/\/opstree.com\/blog\/\/?p=15451"},"modified":"2025-11-20T15:53:20","modified_gmt":"2025-11-20T10:23:20","slug":"applications-hosting-on-ecs","status":"publish","type":"post","link":"https:\/\/opstree.com\/blog\/2023\/09\/19\/applications-hosting-on-ecs\/","title":{"rendered":"Applications Hosting on ECS"},"content":{"rendered":"\r\n

Introduction<\/h2>\r\n\r\n\r\n\r\n

Applications hosting on Amazon Elastic Container Service (ECS) is a cloud computing solution provided by AWS that enables organizations to manage, scale, and deploy containerized applications with ease. ECS simplifies container deployment and management, enabling developers to concentrate on creating and running their applications.<\/p>\r\n\r\n\r\n\r\n

In this blog, we will create a repository, copy an image to Amazon Elastic Container Registry (ECR), define a task, and set up an ECS cluster to host an application on Amazon ECS<\/a>.<\/p>\r\n\r\n\r\n\r\n

Create a repo and Copy an Image in ECR<\/h2>\r\n\r\n\r\n\r\n

Amazon ECR is a fully managed container registry service provided by Amazon Web Services (AWS). It allows you to store, manage, and deploy Docker container images. Please follow the below steps to create a repo in ECR and copy an image to that ECR.<\/p>\r\n\r\n\r\n\r\n\r\n\r\n

Step 1:<\/strong> Open a web browser and log in to the AWS Management Console (https:\/\/aws.amazon.com\/<\/a>) by using your AWS account credentials.<\/p>\r\n\r\n\r\n\r\n

Step 2:<\/strong> In the AWS Management Console, click on the “search” box at the top, and then type “ECR” and select “Elastic Container Registry”.<\/p>\r\n\r\n\r\n\r\n

\"\"<\/figure>\r\n\r\n\r\n\r\n

 <\/p>\r\n\r\n\r\n\r\n

Step 3:<\/strong> Now click on the Repositories option under Elastic Container Registry.<\/p>\r\n\r\n\r\n\r\n

\"\"<\/figure>\r\n\r\n\r\n\r\n

 <\/p>\r\n\r\n\r\n\r\n

Step 4:<\/strong> In the Amazon ECR dashboard, click the “Create repository” button to create your repository.<\/p>\r\n\r\n\r\n\r\n

\"\"<\/figure>\r\n\r\n\r\n\r\n

 <\/p>\r\n\r\n\r\n\r\n

Step 5:<\/strong> Choose the visibility setting for your repository. It may be public or private. If we select private then Access will be managed by IAM and repository policy permissions while if we choose public then it will be Publicly visible and accessible for image pulls. By default it’s private.<\/p>\r\n\r\n\r\n\r\n

\"\"<\/figure>\r\n\r\n\r\n\r\n

 <\/p>\r\n\r\n\r\n\r\n

Step 6:<\/strong> Now Enter a unique name for your ECR repository. This name will be part of the repository URI, so it should be unique within your AWS account and region.<\/p>\r\n\r\n\r\n\r\n

Step 7:<\/strong> Choose whether you want to allow or disallow image tag mutations. This setting determines whether image tags can be overwritten. By default, this setting is in the disabled state.<\/p>\r\n\r\n\r\n\r\n

Step 8: <\/strong>You can also enable image scanning that allows Amazon ECR to scan container images for software vulnerabilities. This will help improve the security of your images. By default, this in the disabled state.<\/p>\r\n\r\n\r\n\r\n

\"\"<\/figure>\r\n\r\n\r\n\r\n

 <\/p>\r\n\r\n\r\n\r\n

Step 9:<\/strong> You can use AWS KMS to encrypt images stored in this repository, by default it is disabled.<\/p>\r\n\r\n\r\n\r\n

Step 10:<\/strong> Now click on Create Repository and your repository will be created<\/p>\r\n\r\n\r\n\r\n

Step 11:<\/strong> Go to that repo and then click on view push commands and modify these commands as per your requirements like you can change your image name and tag.<\/p>\r\n\r\n\r\n\r\n

\"\"<\/figure>\r\n\r\n\r\n\r\n

Create a Task Definition<\/h2>\r\n\r\n\r\n\r\n


A Task Definition is a configuration file that defines how a Docker container should run within a task. After creating a Task Definition, you can use it to launch tasks or define services in an ECS cluster. Tasks created from the same Task Definition will inherit its configuration and settings, ensuring consistency across your containerized applications. To create a task definition follow the below steps.<\/p>\r\n\r\n\r\n\r\n

Step 1:<\/strong> In the AWS Management Console, click on the “search” box at the top, and then type “ECS” and select “Elastic Container Service”.<\/p>\r\n\r\n\r\n\r\n

\"\"<\/figure>\r\n\r\n\r\n\r\n

 <\/p>\r\n\r\n\r\n\r\n

Step 2:<\/strong> In the ECS dashboard, navigate to ‘Task Definitions’ in the left navigation pane.<\/p>\r\n\r\n\r\n\r\n

\"\"<\/figure>\r\n\r\n\r\n\r\n

 <\/p>\r\n\r\n\r\n\r\n

Step 3:<\/strong> Click the “Create new Task Definition” button. Here we have two options to create task definition. We can simply create a new task definition using UI or we can create a task definition using a JSON file.<\/p>\r\n\r\n\r\n\r\n

\"\"<\/figure>\r\n\r\n\r\n\r\n

 <\/p>\r\n\r\n\r\n\r\n

Step 4: Create a new task definition using UI<\/strong>
Click on Create a new task definition and then provide the name of the task in the Task definition family option.<\/p>\r\n\r\n\r\n\r\n

\"\"<\/figure>\r\n\r\n\r\n\r\n

Choose the launch type compatibility (EC2 or Fargate), operating system, CPU, and memory for your task depending on your use case.<\/p>\r\n\r\n\r\n\r\n

Step 5:<\/strong> You can create a new task execution role or select an existing one. This role is used by the container agent to make AWS API requests on your behalf.<\/p>\r\n\r\n\r\n\r\n

\"\"<\/figure>\r\n\r\n\r\n\r\n

 <\/p>\r\n\r\n\r\n\r\n

Step 6:<\/strong> Now fill in the container details like
Container Name:<\/strong> A unique name for the container.
Image URI:<\/strong> The Docker image to use for the container (if the image is stored in ECR then you can copy the image URI from there).
Port Mappings:<\/strong> If your container exposes any ports, map them to the host ports.
Memory Limits:<\/strong> Set the soft and hard memory limits for the container.
CPU Units:<\/strong> Specify CPU units for the container.
Environment Variables (optional):<\/strong> Define any environment variables needed for your container.
Volumes (optional): <\/strong>Attach any Amazon EFS volumes or other volumes to your container if required.<\/p>\r\n\r\n\r\n\r\n

Step 7:<\/strong> You can also set monitoring and tag your task definition, it’s optional and click on the create button.<\/p>\r\n\r\n\r\n\r\n

\"\"<\/figure>\r\n\r\n\r\n\r\n

 <\/p>\r\n\r\n\r\n\r\n

\"\"<\/figure>\r\n\r\n\r\n\r\n

 <\/p>\r\n\r\n\r\n\r\n

Step 8:<\/strong> Create a new task definition using JSON file<\/strong>
You can also create a JSON file to create a task definition. Just go on the ECS dashboard and then click on Create task definition with JSON.<\/p>\r\n\r\n\r\n\r\n

\"\"<\/figure>\r\n\r\n\r\n\r\n

 <\/p>\r\n\r\n\r\n\r\n

Paste your JSON code and then click on the create button.<\/p>\r\n\r\n\r\n\r\n

Sample JSON file:<\/strong><\/p>\r\n\r\n\r\n\r\n

{\r\n    \"family\": \"task-defination-name\",\r\n    \"containerDefinitions\": [\r\n        {\r\n            \"name\": \"container-name\",\r\n            \"image\": \"image-uri-from-ECR\",\r\n            \"cpu\": 256,\r\n            \"portMappings\": [\r\n                {\r\n                    \"name\": \"container-name-80-tcp\",\r\n                    \"containerPort\": 80,\r\n                    \"hostPort\": 80,\r\n                    \"protocol\": \"tcp\",\r\n                    \"appProtocol\": \"http\"\r\n                }\r\n            ],\r\n            \"essential\": true,\r\n            \"environment\": [],\r\n            \"environmentFiles\": [],\r\n            \"mountPoints\": [],\r\n            \"volumesFrom\": [],\r\n            \"ulimits\": [],\r\n        }\r\n    ],\r\n    \"executionRoleArn\": \"role-arn-should-be-here\",\r\n    \"networkMode\": \"bridge\",\r\n    \"requiresCompatibilities\": [\r\n        \"EC2\"\r\n    ],\r\n    \"cpu\": \"1024\",\r\n    \"memory\": \"3072\",\r\n    \"runtimePlatform\": {\r\n        \"cpuArchitecture\": \"X86_64\",\r\n        \"operatingSystemFamily\": \"LINUX\"\r\n    }\r\n}<\/code><\/pre>\r\n\r\n\r\n\r\n\r\n\r\n
Create a Cluster<\/h2>\r\n\r\n\r\n\r\n
A cluster in Amazon ECS is a logical grouping of container instances (EC2 instances or Fargate tasks) that are managed collectively to run containerized applications. Each cluster can be associated with one or more services and tasks, allowing you to organize and manage your containerized applications effectively. Please follow the below steps to create a cluster.<\/p>\r\n\r\n\r\n\r\n
Step 1:<\/strong> Search for Elastic Container Service and click on it.<\/p>\r\n\r\n\r\n\r\n
\"\"<\/figure>\r\n\r\n\r\n\r\n
 <\/p>\r\n\r\n\r\n\r\n
Step 2:<\/strong> Click on clusters and create a cluster.<\/p>\r\n\r\n\r\n\r\n
\"\"<\/figure>\r\n\r\n\r\n\r\n
 <\/p>\r\n\r\n\r\n\r\n
Step 3:<\/strong> Fill Cluster name, and choose infrastructure Here I am deploying an application on ECS using Amazon EC2 instances.<\/p>\r\n\r\n\r\n\r\n
\"\"<\/figure>\r\n\r\n\r\n\r\n
 <\/p>\r\n\r\n\r\n\r\n
If you already have an Auto scaling group(ASG) then select that ASG otherwise create a new ASG by selecting EC2 instance type, desired capacity, operating system, and SSH key pair.<\/p>\r\n\r\n\r\n\r\n\r\n\r\n
Step 4:<\/strong> Select a VPC with multiple subnets in which you want to deploy your applications.<\/p>\r\n\r\n\r\n\r\n
\"\"<\/figure>\r\n\r\n\r\n\r\n
 <\/p>\r\n\r\n\r\n\r\n
Monitoring and Tags are optional. When using Monitoring, there is a cost associated with it.<\/p>\r\n\r\n\r\n\r\n
Step 5:<\/strong> Now click on the Create button.<\/p>\r\n\r\n\r\n\r\n
Create a service<\/h2>\r\n\r\n\r\n\r\n
In Amazon Elastic Container Service (ECS), a service is a resource that manages and maintains a specified number of instances of a task definition. ECS services define how tasks should be managed, scaled, updated, and distributed across container instances within a cluster. Please follow the below steps to create a service.<\/p>\r\n\r\n\r\n\r\n
Step 1:<\/strong> In the ECS dashboard, navigate to the cluster where you want to create the service and Click the “Create” button in the “Services” tab.<\/p>\r\n\r\n\r\n\r\n
\"\"<\/figure>\r\n\r\n\r\n\r\n
 <\/p>\r\n\r\n\r\n\r\n
Step 2:<\/strong> Choose a compute option as per your use case. Here I am choosing the launch type and then selects a launch type (EC2 or Fargate) that matches your cluster type.<\/p>\r\n\r\n\r\n\r\n
\"\"<\/figure>\r\n\r\n\r\n\r\n
 <\/p>\r\n\r\n\r\n\r\n
Step 3:<\/strong> Select the task definition you want to run as a service and define the service name, service type, number of desired tasks, and deployment configuration.<\/p>\r\n\r\n\r\n\r\n
\"\"<\/figure>\r\n\r\n\r\n\r\n
 <\/p>\r\n\r\n\r\n\r\n
Step 4:<\/strong> Configure load Balancer for the application that you want to deploy in this service. You can also configure auto-scaling options if needed.<\/p>\r\n\r\n\r\n\r\n
\"\"<\/figure>\r\n\r\n\r\n\r\n
 <\/p>\r\n\r\n\r\n\r\n
\"\"<\/figure>\r\n\r\n\r\n\r\n
 <\/p>\r\n\r\n\r\n\r\n
Step 5: Now click on the Create button and your service will be created.<\/p>\r\n\r\n\r\n\r\n
\"\"<\/figure>\r\n\r\n\r\n\r\n
 <\/p>\r\n\r\n\r\n\r\n
\"\"<\/figure>\r\n\r\n\r\n\r\n
 <\/p>\r\n\r\n\r\n\r\n
Step 6:<\/strong> Now go to your loadbalancer which you configured in your service and copy DNS name of that loadbalancer and try to hit on your browser and you can find your web service is working.<\/p>\r\n\r\n\r\n\r\n
\"\"<\/figure>\r\n\r\n\r\n\r\n
 <\/p>\r\n\r\n\r\n\r\n
\"\"<\/figure>\r\n\r\n\r\n\r\n
 <\/p>\r\n\r\n\r\n\r\n
After creating the service, you can monitor its status and the running tasks in the ECS dashboard. The service will automatically maintain the desired number of tasks, as specified in the service configuration, ensuring they are running continuously.<\/p>\r\n\r\n\r\n\r\n
Conclusion:<\/h2>\r\n\r\n\r\n\r\n
ECS is a valuable service for modern application development and deployment in the AWS cloud. Hosting applications on ECS empowers organizations to leverage the benefits of containerization while simplifying the complexities of orchestration and infrastructure management. It provides a scalable and efficient platform for running containerized applications.<\/p>\r\n\r\n\r\n\r\n
Blog Pundits: Prakash Jha<\/strong><\/a> and Sandeep Rawat<\/a><\/strong><\/p>\r\n\r\n\r\n\r\n
OpsTree is an End-to-End DevOps Solution<\/a> Provider.<\/strong><\/p>\r\n
Related Searches – AWS Consulting Services<\/a> | Database Migration Services<\/a>\u00a0<\/strong><\/p>\r\n\r\n\r\n\r\n
<\/div>\r\n\r\n\r\n\r\n