ECS Demo Part 1

• Prerequisites: Docker (optional, for building images) and an AWS account with permissions to create ECS, IAM, VPC, and security group resources.
• Public images used in this demo (available on Docker Hub):
  • KodeKloud/ECS-Project1
  • KodeKloud/ECS-Project2

• https://hub.docker.com/

​

Application (Project 1)

<!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="UTF-8" />
    <meta http-equiv="X-UA-Compatible" content="IE=edge" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <link rel="stylesheet" href="css/style.css" />
    <title>Document</title>
  </head>
  <body>
    <h1>ECS Project 1</h1>
  </body>
</html>

const express = require("express");
const path = require("path");

const app = express();

app.set("view engine", "ejs");
app.set("views", path.join(__dirname, "views"));

app.use(express.static(path.join(__dirname, "public")));

app.get("/", (req, res) => {
  res.render("index");
});

app.listen(3000, () => {
  console.log("Server is running on port 3000");
});

FROM node:16
WORKDIR /usr/src/app

COPY package*.json ./
RUN npm ci --only=production
COPY . .
EXPOSE 3000
CMD [ "node", "index.js" ]

​

1) Quick start: use the ECS wizard

• Container name: ecs-project1
• Image: KodeKloud/ECS-Project1
• Memory limits: optional/sensible defaults
• Port mappings: container port 3000 (TCP)

• Container port: 3000 (TCP)
• Image: KodeKloud/ECS-Project1
• Optional: memory, CPU, health checks, environment variables, logging

CMD-SHELL, curl -f http://localhost:3000/ || exit 1

​

2) Clean up wizard resources (so we can recreate manually)

• Delete the service (stops and removes tasks).
• Delete the cluster (removes cluster and the VPC/subnets the wizard created).

​

3) Create a cluster and task definition manually

• Go to ECS → Clusters → Create Cluster
• Choose “Networking only (Fargate)”
• Name the cluster, e.g., cluster1
• Let ECS create a VPC and subnets for you (or choose an existing VPC)
• Create and open the cluster

• ECS → Task Definitions → Create task definition → select FARGATE
• Name the task definition and select the Task execution role (this role lets ECS pull images and write logs)
• OS family: Linux
• Set Task CPU and Memory appropriate to your app
• Add a container definition:
  • Container name: node-app
  • Image: KodeKloud/ECS-Project1
  • Port mapping: container port 3000, TCP
  • Optionally: health check, env vars, logging (awslogs)

• Cluster → Services → Create
• Launch type: FARGATE
• Task definition: select your newly created task definition (latest revision)
• Cluster: cluster1
• Service name: project-one-service
• Number of tasks: desired scale (e.g., 1 or 2)
• Networking:
  • VPC and subnets: choose those created for the cluster
  • Security group: ensure it allows inbound traffic to the container port (3000) from the clients that need access
• Load balancer: optional (skipped in this demo)
• Auto Scaling: optional (skip for the demo)

​

4) Updating the app image and redeploying

# Build and tag locally
docker build -t kodekloud/ecs-project1:latest .

# Push to Docker Hub
docker push kodekloud/ecs-project1:latest

• In the Service view: Choose Update → check “Force new deployment” — this causes ECS to create new tasks that pull the updated image.
• Or: Create a new revision of the Task Definition (if you changed configuration) and update the service to use that revision.

​

5) Final cleanup and next steps

• Delete the service (this will stop tasks).
• Delete the cluster (if you don’t plan to reuse it).
• Delete any related security groups, VPCs, or load balancers the demo created (if applicable).

• Amazon ECS docs: https://docs.aws.amazon.com/ecs/
• Amazon EC2 (for EC2-backed ECS): https://learn.kodekloud.com/user/courses/amazon-elastic-compute-cloud-ec2