---
title: "Discussion on \"Deploying NestJS Application on ECS Fargate using AWS Copilot\" | Hashnode"
description: "Discussion on \"Deploying NestJS Application on ECS Fargate using AWS Copilot\". Learn how to deploy your NestJS application on ECS Fargate with ease using AWS Copilot. Our step-by-step guide walks you through the entire process."
url: "https://hashnode.com/posts/deploying-nestjs-application-on-ecs-fargate-using-aws-copilot/6402f6d71eac58beba9b3fb1"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Deploying NestJS Application on ECS Fargate using AWS Copilot](https://marksabelita.hashnode.dev/deploying-nestjs-application-on-ecs-fargate-using-aws-copilot?utm_source=hashnode&utm_medium=feed)

Learn how to deploy your NestJS application on ECS Fargate with ease using AWS Copilot. Our step-by-step guide walks you through the entire process.

Mar 4, 2023 · 12 min read · marksabelita.hashnode.dev  
Updated Mar 6, 2023  
Read the article

-   [#nestjs](https://hashnode.com/tag/nestjs)
-   [#docker](https://hashnode.com/tag/docker)
-   [#aws-fargate](https://hashnode.com/tag/aws-fargate)
-   [#full-stack-development](https://hashnode.com/tag/full-stack-development)
-   [#aws-copilot](https://hashnode.com/tag/aws-copilot)

## Written by

[Mark Sabelita](https://hashnode.com/@marksabelita)

@marksabelita · Manila, PH

  
[View profile](https://hashnode.com/@marksabelita)

Fullstack Developer

I love crafting elegant solutions that make an impact. With expertise in both front-end and back-end technologies, I'm passionate about creating dynamic, user-focused applications. When I'm not coding, you can find me exploring new technologies, experimenting with new frameworks, or brainstorming my next big project. Let's collaborate and bring your ideas to life!

## Responses 1

Markdown supported · ⌘↵ to post

[Node Edge Ops](https://hashnode.com/@nodeedgeops)

[4d ago](https://hashnode.com/posts/deploying-nestjs-application-on-ecs-fargate-using-aws-copilot/6402f6d71eac58beba9b3fb1/comment/6aec46445edfbe1129549dd0)

For Nest on Copilot/Fargate, treat the service manifest and task size as the contract: the container port Nest listens on, CPU/memory, and env must match what the process actually binds. Keep the ALB (or service) health check on a cheap liveness route that only proves the Nest process is up — put Mongo/RDS/Redis depth on a separate readiness path so a brief dependency blip does not force Fargate to thrash task replacements. Inject secrets at task/runtime, not into image layers that ECR keeps forever.

Ops prove-out after the first stable revision: confirm healthy running tasks, hit the public service URL once and a task private IP:port once, and compare status codes plus Host / X-Forwarded-\* behaviour against what Nest assumed on localhost. If the target group flaps, check security groups, the mapped container port, and whether the health path still waits on a dependency that is not ready at start.