Releases: cloudposse/terraform-aws-elasticsearch
v0.25.1
🚀 Enhancements
Bump dependencies to support v14 @svrakitin (#88)
Bumped versions to eliminate following errors on v0.14.x:
Error: Unsupported Terraform Core version
on xxx, in terraform:
2: required_version = ">= 0.12.0, < 0.14.0"
v0.25.0
[GH Issue 85] Support Audit Logging @neuroticnetworks (#86)
what
- This PR enables
AUDIT_LOGS
support in the CloudPosse ES Module.
why
- There are currently four types of logs supported by Terraform Elasticsearch:
INDEX_SLOW_LOGS
,SEARCH_SLOW_LOGS
,ES_APPLICATION_LOGS
, andAUDIT_LOGS
(xref log_publishing_options here) The CloudPosse module currently supports the first of these log types, but does not allow you to enableAUDIT_LOGS
.
references
v0.24.1
v0.24.0
Allow authenticated access from anywhere @Nuru (#75)
what
- Allow authenticated access from anywhere
- Avoid specifying
warm_count
andwarm_type
whenwarm_enabled == false
- Revert PR #66
- Minor cleanups
why
-
PR #58 allowed unauthenticated access from whitelisted CIDRs, but in the process restricted authenticated access to those IPs as well. This PR make authenticated access not subject to the CIDR restriction.
-
PR #74 introduced support for UltraWarm clusters, but always set
warm_count
andwarm_type
, eve whenwarm_enabled == false
. This caused Terraform to always see the state as needing updating, since the detected state whenwarm_enabled == false
iswarm_count = 0
andwarm_type
unset. The PR leaves them unset to avoid apparent drift. -
The
kibana_endpoint
is not just a domain name, it includes a path component, the end result being something likeesdomain-ntzuxwxpuxm7dmxcbpy4slbc4u.us-west-1.es.amazonaws.com/_plugin/kibana/
. As such, is not suitable for a DNS record. The plainendpoint
is the hostname portion and should be used for DNS. The previous code was correct but misunderstood. -
Some working code was nevertheless not the best style, and to the extent this serves as an example, we want the code to be in our preferred style.
v0.23.0
Add support for ultraWarm and advanced security @maciejasembler (#74)
what
- Adds in-module support for ultrawarm nodes
- Adds in-module support for advanced security features (fine-grained access control)
why
- People are using it, obviously
references
v0.22.0
Adds *_hostname_enabled vars for explicit opt-in to hostnames @Gowiem (#73)
what
- Adds
domain_hostname_enabled
andkibana_hostname_enabled
var flags to fix an issues withcount
when dns_zone_id is not being passed static.
why
- Implicit opt-in through checking dns_zone_id was causing folks problems as count / enabled need to be calculated during the plan which caused using
-target
. - This fixes needing a targeted apply when passing dns_zone_id from a resource or module reference.
references
- Fixes + Closes #13
- Discussion in SweetOps: https://sweetops.slack.com/archives/CB6GHNLG0/p1600294860394500
0.21.0 AWS provider 3.x
what
- enable 3.x AWS provider versions to be used with this module
why
- latest version should be used, 2.x not getting updates any more
0.20.4: Update terraform-aws-route53-cluster-hostname versions to support Terraform 0.13 #68
Update terraform-aws-route53-cluster-hostname versions to support Ter…
0.20.3: Set ebs volume size for basic example #65
what
- Setting EBS volume size of 10 for basic example
why
- Terraform apply is failing on
Error: Error creating ElasticSearch domain: ValidationException: EBS storage must be selected for t2.small.elasticsearch
as this is currently being defaulted to 0 https://github.com/cloudposse/terraform-aws-elasticsearch/blob/master/variables.tf#L154