Deprecated

This version of the module has been deprecated in favor of https://github.com/7Factor/terraform-aws-ecs-http-task which exists on the Terraform Registry. Please migrate to this version at your earliest convenience. Instructions for migration can be found in the new repository.

ECS HTTP Task

This module will allow you to deploy an ECS Task and an ECS Service. This is intended to be run as part of your app deployment pipeline. It works well with Concourse. It is assumed you already have a solution for deploying an ECS Cluster. If not, check out ours. This particular iteration assumes that you are deploying applications behind a load balancer with SSL termination and redirection from port 80 (i.e. AWS application load balancer).

Prerequisites

First, you need a decent understanding of how to use Terraform. Hit the docs for that. Then, you should familiarize yourself with ECS concepts, especially if you've never worked with a clustering solution before. Once you're good, import this module and pass the appropriate variables. Then, plan your run and deploy.

We also assume that you're deploying an application behind an ALB to port 443 (a really good idea). We will ask for your certificate ARN and automagically configure an HTTP to HTTPS redirect on the ALB. If you need more interesting features like opening ports other than 80 and 443 then feel free to use this as a template.

Example Usage

module "terraform-ecs-task" {
  source                = "git::https://github.com/7Factor/terraform-ecs-task.git"
  vpc_id                = "${data.aws_vpc.primary_vpc.id}"
  alb_subnets           = "${data.aws_subnet_ids.subnet_ids.ids}"
  lb_security_group_id  = "${data.aws_security_group.primary_sg.id}"
  app_name              = "${var.app_name}"
  app_port              = "${var.app_port}"
  cpu                   = "256"
  memory                = "256"
  desired_task_count    = "2"
  service_role_arn      = "${var.service_role_arn}"
  service_name          = "Angular Starter Service"
  container_definitions = "${data.template_file.container_definitions.rendered}"
}

Deployment Options

The default configuration will perform standard blue/green deployments by setting the minimum and maximum "percentages" to 100% and 200%, respectively. When deploying non-critical services (e.g. development and staging instances) in tightly constrained environments, deployments may fail if there are insufficient CPU/memory "units" to start new tasks before stopping the old ones. To resolve this, set these values to 0% and 100%:

service_deployment_maximum_percent         = 100
service_deployment_minimum_healthy_percent = 0