https://github.com/shresth72/terraform_vpc_networking

Complete ECS - VPC network in Terraform with best practices.
https://github.com/shresth72/terraform_vpc_networking

aws docker ecr ecs nat-gateways route-tables subnets terraform terraform-modules vpc

Last synced: 5 months ago
JSON representation

Complete ECS - VPC network in Terraform with best practices.

• Host: GitHub
• URL: https://github.com/shresth72/terraform_vpc_networking
• Owner: Shresth72
• Created: 2024-03-25T12:18:45.000Z (over 2 years ago)
• Default Branch: main
• Last Pushed: 2024-12-09T19:24:18.000Z (over 1 year ago)
• Last Synced: 2025-02-13T15:26:43.767Z (over 1 year ago)
• Topics: aws, docker, ecr, ecs, nat-gateways, route-tables, subnets, terraform, terraform-modules, vpc
• Language: HCL
• Homepage:
• Size: 3.35 MB
• Stars: 0
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

          
# VPC and ECS Networks

## VPC & Networking



## ECS

ECS helps in managing the execution of fleets of containers in a high available manner and monitors resource consumption and requirements.

- Helps in scaling elastically and integrate with other Services along with load balancing

- Managing containers through programmatic API and AWS CLI tools such as ECR and EC2

- Secure through policies, availability, granular control over isolated resources and their allocation. Also, allows usage of VPC for clusters and setup security groups to manage traffic.

There are three main components:

- Cluster

- Task

- Service

### Cluster

- Group of EC2 instances spread across multiple availability zones, that are running the AWS ECS container agent.

- Agents allow EC2 instances to talk with the backend logic of ECS, which allows for resource management, lifecycle coordination and efficient scheduling.

- Containers in a cluster are grouped in task and asked to EC2 to run them. They can have mix of instance types and other EC2 specifications.

![alt text](./vpc_nat/images/ecr.png)

![alt text](./vpc_nat/images/ecs1.png)

![alt text](./vpc_nat/images/ecs2.png)

![alt text](./vpc_nat/images/add_container.png)

### Task

- Task definition is a file that describes one or more containers that should run together and are deployed as a single unit.

- Task is one instantiation of a task definition that runs all containers together in the AWS EC2 instance.

![alt text](./vpc_nat/images/task_def.png)

- Schedule tasks based on the task definition and run them in the cluster

![alt text](./vpc_nat/images/schedule_tasks.png)

### Service

- Service is where all of this functionalities are connected together, and it schedules tasks based on their definition in the cluster. Defines min and max no of tasks desired in the cluster and also helps in restarting failed tasks along with scalability.

- Configure the service to run the tasks in the cluster

![alt text](./vpc_nat/images/configure_service.png)

- Set Application Load Balancer to route traffic to the ECS service

![alt text](./vpc_nat/images/alb_1.png)

![alt text](./vpc_nat/images/alb_2.png)

- Add Auto Scaling to the ECS service

![alt text](./vpc_nat/images/auto_scaling.png)

- Add CloudWatch to monitor the ECS service

- Review and create the ECS service

![alt text](./vpc_nat/images/final_ecs.png)

- The apps running in the cluster can be accessed through the EC2 ALB DNS name

## CICD

To facilitate the deployment of the ECS service, we can use the CICD pipeline to automate the process.

We can have the following stages in the pipeline:

1. Monitor the source code repository for changes

2. Build the Docker image

3. Push the Docker image to ECR or image repository

4. Update the ECS service with the new image