0.20.1

Fixes kibana_hostname module using incorrect endpoint output (#66)

0.20.0: [AUTOMATED] Update Version Pinning for Terraform to support 0.13 (#64)

## What

1. Update Version Pinning for Terraform to support 0.13

## Why

1. This is a relatively minor update that the CloudPosse module already likely supports.
1. This allows module consumers to not individually update our Terraform module to support Terraform 0.13.

0.19.0

what

• Amazon Cognito authentication for Kibana is not supported on AWS China.
• Therefore we need to have a way to avoid setting the cognito options inner block on the aws_elasticsearch_domain terraform resource.

why

• When we try to run this module on AWS China we always get the following error:

Error: Error creating ElasticSearch domain: DisabledOperationException: You don’t have permissions to integrate with Cognito. Contact your admin if you need help.
on .terraform/modules/elasticsearch/terraform-aws-elasticsearch-0.18.0/main.tf line 122, in resource 
"aws_elasticsearch_domain" "default": 122: resource "aws_elasticsearch_domain" "default" {

Even though we tried to set the correct IAM roles (see references below) and permissions the error still occurs.

references

• https://docs.amazonaws.cn/en_us/aws/latest/userguide/elasticsearch.html
• https://docs.aws.amazon.com/elasticsearch-service/latest/developerguide/es-cognito-auth.html#es-cognito-auth-config

0.18.0 Allow custom Service Identifier in IAM policy

what

• Adds possibility to insert different AWS EC2 Service Identifier.

why

• Allow to deploy AWS ES in China or GOV regions (ec2.amazonaws.com.cn)

0.17.0

When the Elasticsearch cluster is deployed outside of a VPC (vpc_enabled = false), whitelisted IP ranges (allowed_cidr_blocks) are allowed to access Elasticsearch without authentication.

0.16.0 Ability to spin ES cluster outside of VPC

what

• ES can be used outside of VPC via vpc_enabled variable
• Updated default ES version to latest 7.4
• Updated modules in tests

why

• For currently supported Kinesis Firehose delivery to ElasticSearch (VPC delivery is available in AWS but not yet in tf)

references

hashicorp/terraform-provider-aws#13015

0.15.0 Allow configuration of ingress port range

what

• Adds configuration variables to modify the range of allowed ingress ports (or port)

why

• Allow to limit communication to only a particular port (e.g. 443 to enforce SSL usage) in ES connectivity

0.14.0 Fix `count` for resources

what

• Fix count for resources
• Don't use data sources in counts

why

• When an output from a data source is used in counts, in some cases Terraform can't compute the counts throwing the errors (it's working in the Terratest, but does not work for some customers):

Error: Invalid count argument
 on .terraform/modules/search_service_elasticsearch_master.elasticsearch/main.tf line 76, in resource "aws_iam_service_linked_role" "default":
 76:   count            = var.enabled && var.create_iam_service_linked_role && length(data.aws_iam_role.default.*.id) == 0 ? 1 : 0
The "count" value depends on resource attributes that cannot be determined
until apply, so Terraform cannot predict how many instances will be created.
To work around this, use the -target argument to first apply only the
resources that the count depends on.

• We have a bool variable create_iam_service_linked_role to control that without using data sources. If the AWS account (where the module is provisioned) already has the AWSServiceRoleForAmazonElasticsearchService service role, set the variable create_iam_service_linked_role to false. On a new account, set it to true

0.13.0: Make elasticsearch subdomain configurable (#51)

• Make elasticsearch subdomain configurable

0.12.0 Output domain_name

Add domain_name to outputs (#50)

* Add domain_name to outputs

* Updated README.md

Co-authored-by: actions-bot <58130806+actions-bot@users.noreply.github.com>