Skip to content
Snippets Groups Projects
Commit fa70cc72 authored by Chris Thain's avatar Chris Thain Committed by Chris Thain
Browse files

Docs: Fix path to consul-ecs Terraform modules (#13689)

parent 7f1bd9b8
No related merge requests found
......@@ -6,19 +6,17 @@ description: Compatibility Matrix for Consul ECS
# Compatibility Matrix for Consul on ECS
For every release of Consul on ECS, `consul-ecs` binary and `consul-ecs` terraform module is updated. The terraform module and binary are tightly coupled. Ex: consul-ecs binary 0.4.1 must use consul-ecs terraform 0.4.1.
For every release of Consul on ECS, the `consul-ecs` binary and `consul-ecs` Terraform module are updated. The versions of the Terraform module and binary are tightly coupled. For example, `consul-ecs` 0.4.1 binary must use the `consul-ecs` 0.4.1 Terraform module.
## Supported Consul versions
### Version 0.2.0 and above
| Consul Version | Compatible consul-ecs Versions |
| -------------- | ------------------------------- |
| 1.10.x | 0.2.x |
| 1.11.x | 0.3.0, 0.4.x |
| 1.12.x | 0.5.x |
| 1.11.x | 0.3.0, 0.4.x |
| 1.10.x | 0.2.x |
## Supported Envoy versions
Supported versions of Envoy for Consul versions are also found in [Envoy - Supported Versions](/docs/connect/proxies/envoy#supported-versions). The recommended best practice is to use the default version of Envoy that is provided in the terraform module, as that is the version that has been tested with Consul ECS binaries for a given version.
Refer to [Envoy - Supported Versions](/docs/connect/proxies/envoy#supported-versions) for information about which versions of Envoy are supported for each version of Consul. As a best practice, we recommend using the default version of Envoy that is provided in the Terraform module. This is because we test the default versions with Consul ECS binaries for the given version.
......@@ -84,7 +84,7 @@ is not provided when `consul_partitions_enabled = true`, will default to the `de
```hcl
module "acl_controller" {
source = "hashicorp/consul/aws//modules/acl-controller"
source = "hashicorp/consul-ecs/aws//modules/acl-controller"
...
......@@ -109,7 +109,7 @@ The following example demonstrates how to create a `mesh-task` assigned to the a
```hcl
module "my_task" {
source = "hashicorp/consul/aws//modules/mesh-task"
source = "hashicorp/consul-ecs/aws//modules/mesh-task"
family = "my_task"
...
......
......@@ -68,7 +68,7 @@ The `mesh-task` module is used as follows:
```hcl
module "my_task" {
source = "hashicorp/consul/aws//modules/mesh-task"
source = "hashicorp/consul-ecs/aws//modules/mesh-task"
version = "<latest version>"
family = "my_task"
......
......@@ -80,7 +80,7 @@ the AWS IAM auth method.
```hcl
module "acl_controller" {
source = "hashicorp/consul/aws//modules/acl-controller"
source = "hashicorp/consul-ecs/aws//modules/acl-controller"
version = "<version>"
consul_bootstrap_token_secret_arn = aws_secretsmanager_secret.bootstrap_token.arn
......@@ -141,7 +141,7 @@ should be the same as the `name_prefix` you provide to the ACL controller module
```hcl
module "my_task" {
source = "hashicorp/consul/aws//modules/mesh-task"
source = "hashicorp/consul-ecs/aws//modules/mesh-task"
version = "<version>"
...
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment