carlospalaciosc / terraform-ecs Goto Github PK

• We will be able to run one command to deploy our entire application giving us:

  • A Virtual Private Cloud with private and public subnets
  • Internet Gateway and NatGateway
  • Multiple running container instances
  • A load balancer distributing traffic between the containers
  • Auto scaling of your resources
  • Health checks and logs

To get internet traffic to containers using a load balancer, the load balancer is placed into a public subnet. ECS configures the load balancer to forward traffic to the container tasks in the private subnet:

This configuration allows your tasks in Fargate to be safely isolated from the rest of the internet. They can still initiate network communication with external resources via the NAT gateway, and still receive traffic from the public via the Application Load Balancer that is in the public subnet.

• All configurations can be changed in:

variables.ft

You can choose your docker image application to deploy in Fargate, changing app_image and app_port in variables.tf

variable "az_count" {
  description = "Number of AZs to cover in a given region"
  default     = "2"
}

variable "app_image" {
  description = "Docker image to run in the ECS cluster"
  default     = "gcr.io/google-samples/hello-app:2.0"
}

1. Terraform init, plan and validate scripts

terraform init
terraform plan

terraform validate

2. Apply changes

terraform apply

Output console: Plan: 34 to add, 0 to change, 0 to destroy.

Before to create all resources you can access to application with

curl -v http:/<LOAD_BALANCER_HOSTNAME>/

3. Remember to destroy all resources to avoid incurring payments

terraform destroy -auto-approve