Consul Enterprise on AWS Elastic Container Service (ECS)

You can run Consul Enterprise on ECS by specifying the Consul Enterprise Docker image in the Terraform module parameters.

Specify the Consul image

When you set up an instance of the mesh-task or gateway-task module, set the parameter consul_image to a Consul Enterprise image. The following example instructs the mesh-task module to import Consul Enterprise version 1.12.0:

module "my_task" {
  source  = "hashicorp/consul-ecs/aws//modules/mesh-task"
  version = "<latest version>"

  consul_image = "hashicorp/consul-enterprise:1.12.0-ent"
  ...
}

Licensing

Consul Enterprise requires a license. If running Consul on ECS with ACLs enabled, the license will be automatically pulled down from Consul servers.

Currently there is no capability for specifying the license when ACLs are disabled so if you wish to run Consul Enterprise clients then you must enable ACLs.

Running Consul Community Edition clients

You can operate Consul Enterprise servers with Consul CE (community edition) clients as long as the features you are using do not require Consul Enterprise client support. Admin partitions and namespaces, for example, require Consul Enterprise clients and are not supported with Consul CE.

Feature Support

Consul on ECS supports the following Consul Enterprise features. If you are only using features that run on Consul servers, then you can use a CE client in your service mesh tasks on ECS. If client support is required for any of the features, then you must use a Consul Enterprise client in your mesh-tasks.

Admin Partitions and Namespaces

Consul on ECS supports admin partitions and namespaces when Consul Enterprise servers and clients are used. These features have the following requirements:

• ACLs must be enabled.
• ACL controller must run in the ECS cluster.
• mesh-task must use a Consul Enterprise client image.
• gateway-task must use a Consul Enterprise client image.

The ACL controller manages configuration of the AWS IAM auth method on the Consul servers. It ensures unused tokens created by tasks are cleaned up. It also creates admin partitions and namespaces if they do not already exist.

Each ACL controller manages a single admin partition. Consul on ECS supports one ACL controller per ECS cluster; therefore, the administrative boundary for admin partitions is one admin partition per ECS cluster.

The following example demonstrates how to configure the ACL controller to enable admin partitions and manage an admin partition named my-partition. The consul_partition field is optional and if it is not provided when consul_partitions_enabled = true, will default to the default admin partition.

module "acl_controller" {
  source = "hashicorp/consul-ecs/aws//modules/acl-controller"

  ...

  consul_partitions_enabled = true
  consul_partition          = "my-partition"
}

Services are assigned to admin partitions and namespaces through the use of task tags. The mesh-task module automatically adds the necessary tags to the task definition. If the ACL controller is configured for admin partitions, services on the mesh will always be assigned to an admin partition and namespace. If the mesh-task does not define the partition it will default to the default admin partition. Similarly, if a mesh-task does not define the namespace it will default to the default namespace.

The following example demonstrates how to create a mesh-task assigned to the admin partition named my-partition, in the my-namespace namespace.

module "my_task" {
  source = "hashicorp/consul-ecs/aws//modules/mesh-task"
  family = "my_task"

  ...

  consul_image     = "hashicorp/consul-enterprise:<version>-ent"
  consul_partition = "my-partition"
  consul_namespace = "my-namespace"
}

Audit Logging

Consul on ECS supports audit logging when using Consul Enterprise clients. This feature has the following requirements:

• ACLs must be enabled.
• mesh-task must use a Consul Enterprise image.
• gateway-task must use a Consul Enterprise image.

To enable audit logging, set audit_logging = true when configuring the client.

module "my_task" {
  source = "hashicorp/consul-ecs/aws//modules/mesh-task"
  family = "my_task"

  ...

  consul_image  = "hashicorp/consul-enterprise:<version>-ent"
  audit_logging = true
}