v0.36.0

fix: make the security group description configurable @syphernl (#115)

what

• Made the security group description configurable

why

• Since v0.35.0 a description will be set which replaces the default "Managed by Terraform". Unfortunately, a change in security group description requires it to be deleted and re-created. This is however not possible when the security group is in active use and result in a state apply failure. This variable can be used to retain the existing "Managed by Terraform" description which doesn't trigger a re-create of the security group.

references

• #114

v0.35.0

Add rds security group description @nitrocode (#114)

what

• Add rds security group description

why

• tfsec complains

  [AWS018][ERROR] Resource 'module.redis:aws_security_group.default' should include a description for auditing purposes.
  

references

• N/A

v0.34.0

Transit encryption enabled default to true with docs @nitrocode (#111)

what

• Transit encryption enabled default to true with docs

why

• Due to Bridgecrew and other compliance reasons, it needs to default to true.

references

N/A

v0.33.0

Transit encryption enabled default to null @nitrocode (#110)

what

• default transit_encryption_enabled to null which is the default on elasticache_replication_group resource

why

• Using the default parameters I was surprised that I could not instantly connect to redis via redis-cli -h hostname -p 6379 ping
• After some investigation, I found that the culprit was the transit_encryption_enabled parameter
• I came across this doc which involves using stunnel to appropriately connect

references

N/A

v0.32.1

🚀 Enhancements

support more nodes than there are AZs defined @gusse (#108)

what

• Allows not defining availability_zones
• Can create more nodes than you have defined AZs (once AWS provider is fixed hashicorp/terraform-provider-aws#14070 (comment))

why

• availability_zones parameter shouldn't be required.
• You might want to define the AZs you use and have more nodes than AZs, e.g. use two AZs and 4 nodes

references

• hashicorp/terraform-provider-aws#14070 (comment)
• Similar fix was done to memcached module cloudposse/terraform-aws-elasticache-memcached#28

v0.32.0

Add Multi-AZ option @patrick-armitage (#109)

what

• Add option to enable Multi-AZ

why

• Available in Terraform resource's parameters
• Useful, the main draw for creating read replicas as an automated failover to new AZ

references

• Terraform reference
• AWS Docs on Elasticache Multi-AZ

v0.31.0

context.tf updated to v0.24.1, minimum required Terraform version bumped to 0.13.0 when needed, readme updated @maximmi (#107)

what

• update context.tf to v0.24.1
• minimum required Terraform version bumped to 0.13.0
• readme updated, Bridgecrew compliance badges added

why

• It allows for setting the letter case of tag names and labels, back compatibility with context v0.22.0 and below
• we have dropped support for Terraform 0.12
• To be able see and fix the recommendations from Bridgecrew so we can position our modules as standards compliant

v0.30.0

Terraform 0.14 upgrade @maximmi (#100)

what

• Upgrade to support Terraform 0.14 and bring up to current Cloud Posse standard

why

• Support Terraform 0.14

v0.29.1

🤖 Automatic Updates

chore(deps): update terraform cloudposse/route53-cluster-hostname/aws to v0.10.1 @renovate (#105)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/route53-cluster-hostname/aws (source)	terraform	patch	0.10.0 -> 0.10.1

---

Release Notes

cloudposse/terraform-aws-route53-cluster-hostname

v0.10.1

Compare Source

🤖 Automatic Updates

Update README.md and docs @​cloudpossebot (#​33)

#### what This is an auto-generated PR that updates the README.md and docs #### why To have most recent changes of README.md and doc from origin templates

v0.29.0

add ability to restore cluster from snapshots #96 @skang0601 (#97)

what

Allows the ability to create redis cluster from snapshots

references

• closes #96