Installation

Task Module: Define the to create a task definition with the necessary sidecar containers for your application to join the service mesh.
Routing: With your tasks as part of the mesh, you must specify their upstream services and change the URLs the tasks are using so that they’re making requests through the service mesh.
Now that all communication is flowing through the service mesh, you should change the address your application is listening on to so that it only receives requests through the sidecar proxy.

NOTE: This page assumes you’re familiar with ECS. See What is Amazon Elastic Container Service for more details.

In order to add the necessary sidecar containers for your task to join the mesh, you must use the :

All possible inputs are documented on the module reference documentation, however there are some important inputs worth highlighting:

is used as the task definition family but it’s also used as the name of the service that gets registered in Consul.
accepts an array of container definitions. This is where you include application containers.
is the port that your application listens on. This should be set to a string, not an integer, i.e. port = "9090", not port = 9090.
retry_join is passed to the option for the Consul agent. This tells the agent the location of your Consul servers so that it can join the Consul cluster.

NOTE: If your tasks run in a public subnet, they must have assign_public_ip = true in their network_configuration block so that ECS can pull the Docker images.

To define an ECS Service, reference the mesh-task module’s task_definition_arn output value in your aws_ecs_service resource:

resource "aws_ecs_service" "my_task" {
  ...
}

Now that your tasks are registered in the mesh, you’re able to use the service mesh to route between them.

In order to make calls through the service mesh, you must configure the sidecar proxy to listen on a different port for each upstream service your application needs to call. You then must modify your application to make requests to the sidecar proxy on that port.

For example, if your application web makes calls to another application called backend, then you would first configure the mesh-task module’s upstream(s): backend.

Set the destination_name to the name of the upstream service (in this case backend)
Set to an unused port. This is the port that the sidecar proxy will listen on. Any requests to this port will be forwarded over to the destination_name. This does not have to be the port that backend is listening on because the service mesh will handle routing the request to the right port.

If you have multiple upstream services they each need to be listed here.

Next, configure your application to make requests to localhost:8080 when it wants to call the backend service.

module "web" {
  family = "web"
  upstreams = [
    {
      destination_name = "backend"
      local_bind_port  = 8080
    }
  ]
  container_definitions = [
    {
        {
          name  = "BACKEND_URL"
          value = "http://localhost:8080"
        }
      ]
      ...
    }
  ]
  ...
}

To ensure that your application only receives traffic through the service mesh, you must change the address that your application is listening on to only the loopback address (also known as localhost, lo, and 127.0.0.1) so that only the sidecar proxy running in the same task can make requests to it.

If your application is listening on all interfaces, e.g. 0.0.0.0, then other applications can call it directly, bypassing its sidecar proxy.

Changing the listening address is specific to the language and framework you’re using in your application. Regardless of which language/framework you’re using, it’s a good practice to make the address configurable via environment variable.

For example in Go, you would use:

In Django you’d use:

python manage.py runserver "127.0.0.1:8080"

Configure a secure .
Now that your applications are running in the service mesh, read about other Service Mesh features.
View the documentation to understand what’s going on under the hood.