zone_awareness_config block within cluster_config is not working about terraform-aws-elasticsearch HOT 3 CLOSED

@gzanotto using the public example, the plan shows the right settings for cluster_config:

      + cluster_config {
          + dedicated_master_count   = 3
          + dedicated_master_enabled = true
          + dedicated_master_type    = "r5.large.elasticsearch"
          + instance_count           = 3
          + instance_type            = "r5.large.elasticsearch"
          + warm_enabled             = false
          + zone_awareness_enabled   = true

          + zone_awareness_config {
              + availability_zone_count = 3
            }
        }

Take into account this:

zone_awareness_enabled - (Optional) Indicates whether zone awareness is enabled, set to true for multi-az deployment. To enable awareness with three Availability Zones, the availability_zone_count within the zone_awareness_config must be set to 3.

And also:

availability_zone_count - (Optional) Number of Availability Zones for the domain to use with zone_awareness_enabled. Defaults to 2. Valid values: 2 or 3

If you are using VPC, also check you VPC has at least 3 AZs.

from terraform-aws-elasticsearch.

I faced this issue too, it is happening because of a type casting issue i think.

This line is using contains(["2", "3"]...

Changing it to contains([2, 3]... makes it work for 3 zones.

from terraform-aws-elasticsearch.

@gzanotto @animeshjain release 0.10.0 removed the constraint. I hope it fixes for you!

from terraform-aws-elasticsearch.