This repo shows how to deploy and publish a sample nginx container to aws using terraform scripts.

• terraform installed (more informations are here)
• an aws account
• your iam user aws key and secret
• a key-pair name and file (a user guide is here)

clone this repo: git clone https://github.com/gsiciliano/terraform-ecs-sample.git

rename file terraform.tfvars.example in terraform.tfvars

edit terraform.tfvars replacing:

• aws_access_key = "your-aws-access-key"
• aws_secret_key = "your-aws-secret-key"
• aws_key_pair_name = "your-aws-key-pair-name"
• aws_key_pair_file = "your-aws-key-pair.pem"

cd in repo folder: cd terraform-ecs-sample

init terraform: terraform init

run terraform: terraform apply

When terraform deploy is done it will display your nginx-alb address, then you can open your favorite browser and navigate the given url

Ouput should be something like this:

Apply complete! Resources: 27 added, 0 changed, 0 destroyed.

Outputs:

ecs_cluster_runner_ip = [
  [
    "52.19.149.208",
  ],
]
nginx_dns_lb = "nginx-load-balancer-1889713574.eu-west-1.elb.amazonaws.com"

If you want to remove all the infrastructure and resources create with terraform apply, put terraform destroy command in the terminal and then answer "yes" to the question to confirm your decision. After some minutes you can say goodbye to your nginx-ecs infrastructure.

Final output sound like this: Destroy complete! Resources: 27 destroyed.

That's all

The terraform tf files in this repo create a kind of infrastructure stratus in AWS to expose an nginx server container for demo purpose.

Each file describe a piece of the architecure in order to be maintened as best as possible

The components of this stratus are:

• Networking
• Application load balancer (alb)
• ECS Cluster
• Nginx server container (with aws fargate)

Some other files contains variables, support information or terminal output commands

The only file to be edited after the first clone is terraform.tfvars that must be copied from terraform.tvars.example for security reasons (this is repo is public in git-hub and normally no real variable-filled files should be pushed in a remote repository) putting aws secrets and certificate file path and name into it.