Migrate Tasks to Consul on AWS Elastic Container Service (ECS) with Terraform
This topic describes how to migrate your existing ECS Tasks to use our mesh-task
Terraform module.
Define Tasks in Terraform
Your tasks must first be specified in Terraform using the ecs_task_definition
resource so that they can then be converted to use the mesh-task
module.
For example, your tasks should be defined with Terraform similar to the following:
Convert to the mesh-task
Module
In order to add the necessary sidecar containers for your task to join the mesh,
you must use the mesh-task
module.
The mesh-task
module uses inputs similar to your old ECS task definition but
creates a new version of the task definition with additional containers.
The mesh-task
module is used as follows:
The main differences are:
- You should remove the
execution_role_arn
andtask_role_arn
fields. Themesh-task
module creates the task and execution roles by default. If you need to use existing IAM role(s), set thetask_role
andexecution_role
fields to pass in existing roles. - You must set the
port
field to the port that your application listens on. If your application has no listening port, setoutbound_only = true
and remove theport
field. - You must add the
retry_join
field. This specifies the location of your Consul servers so that your task can join the mesh. - You must remove the
jsonencode()
function from thecontainer_definitions
field.
The mesh-task
module will create a new version of your task definition with the
necessary sidecar containers added so you can delete your existing aws_ecs_task_definition
resource.
Next Steps
Now that your task(s) are migrated to the mesh-task
module,
- Start at the ECS Service section of the Installation Guide to continue installing Consul on ECS.
- Refer to the
mesh-task
reference documentation for all available inputs to your mesh tasks.