Releases: cloudposse/terraform-aws-elasticsearch
Releases · cloudposse/terraform-aws-elasticsearch
0.5.0 Allow use of multiple availability zones
what
- Allow use of multiple availability zones
why
- Allow use of 3 availability zones after hashicorp/terraform-provider-aws#9398
0.4.0 Convert to TF 0.12. Add tests. Add Codefresh test pipeline
what
- Port module to Terraform 0.12
- Pin all providers
- Add example for testing
- Add
bats
andterratest
for the example - Add Codefresh badge to point to the test pipeline in
terraform-modules
project - Update README
why
- Module currently does not work with 0.12. Much easier syntax
- Better regression control
- Automatically test the example on every commit and pull request
- Provision resources on AWS in the test account and check the outputs for the correct values
terraform-modules
project contains pipelines for all terraform modules
0.3.0
0.2.0: Support the node-to-node encryption feature (#12)
* support the node-to-node encryption feature * ran terraform fmt and rebuilt README.md with make
0.1.5: Fix ports openes (#11)
0.1.4
What
- All available log options are individually configurable and can be enabled or disabled (default)
- The CloudWatch log group ARN can be reused for each logging type or a separate one can be used
Why
- To be able to choose any/all or none logging type instead of being bound to only one
0.1.3 Fix ingress securty group bug
What
- Fix error
* aws_security_group_rule.ingress_security_groups: Error updating security group sg-028042200cf49ff7d rule description: InvalidParameterValue: When protocol is ALL, you cannot specify from-port.
status code: 400, request id: d6784da7-a7c8-4748-bdc2-ae44226ba382
How
- Make only
tcp
protocol opened
Why
- To fix error
0.1.2
0.1.1
what
- Fix
aws_security_group_rule
- Add
aws_iam_service_linked_role
why
count
was calculated incorrectly whenvar.allowed_cidr_blocks
was empty- To add
AWSServiceRoleForAmazonElasticsearchService
role before provisioning Elasticsearch domain
references
0.1.0
what
- Terraform module to provision an
Elasticsearch
cluster in a VPC with build-inKibana
andLogstash
why
- Easily provision
Elasticsearch
cluster with the specified node count in the provided subnets in a VPC - Provision Elasticsearch domain policy that accepts a list of IAM role ARNs from which to permit management traffic to the cluster
- Provision Security Group to control access to the Elasticsearch domain (inputs to the Security Group are other Security Groups or CIDRs blocks to be allowed to connect to the cluster)
- Provision DNS hostname record for Elasticsearch cluster
- DNS hostname record for Kibana