README.md

April 15, 2026 Β· View on GitHub

Project Banner

Latest ReleaseSlack CommunityGet Support

This component provisions AWS ElastiCache Redis clusters. The engine can either be redis or valkey. For more information, see why aws supports valkey.

Tip

πŸ‘½ Use Atmos with Terraform

Cloud Posse uses atmos to easily orchestrate multiple environments using Terraform.
Works with Github Actions, Atlantis, or Spacelift.

Watch demo of using Atmos with Terraform
Example of running atmos to manage infrastructure from our Quick Start tutorial.

Usage

Stack Level: Regional

Here's an example snippet for how to use this component.

stacks/catalog/elasticache/elasticache-redis/defaults.yaml file (default settings for all Redis clusters):

components:
  terraform:
    elasticache-redis:
      vars:
        enabled: true
        name: "elasticache-redis"
        family: redis7.x
        egress_cidr_blocks: ["0.0.0.0/0"]
        port: 6379
        at_rest_encryption_enabled: true
        transit_encryption_enabled: false
        apply_immediately: false
        automatic_failover_enabled: false
        cloudwatch_metric_alarms_enabled: false
        snapshot_retention_limit: 1
        snapshot_window: "06:00-07:00"
        maintenance_window: "tue:08:00-tue:09:00"
        # Global defaults for all redis_clusters (can be overridden per cluster)
        engine: "redis"
        engine_version: "7.0"
        instance_type: cache.t4g.small
        num_replicas: 1
        num_shards: 0
        replicas_per_shard: 0
        create_parameter_group: true
        parameters: []
        redis_clusters:
          redis-main:
            instance_type: cache.t4g.small
            engine_version: "7.0"
            parameters:
              - name: notify-keyspace-events
                value: "lK"

stacks/org/ou/account/region.yaml file (imports defaults and overrides per-cluster settings):

import:
  - catalog/elasticache/elasticache-redis/defaults.yaml

components:
  terraform:
    elasticache-redis:
      vars:
        enabled: true
        redis_clusters:
          redis-main:
            instance_type: cache.t4g.small
            # Per-cluster overrides of the global defaults
            engine_version: "7.1"     # override global default of 7.0
            num_replicas: 2       # override global default of 1
            num_shards: 3         # override global default of 0 (enables cluster mode)
            replicas_per_shard: 1 # override global default of 0
            parameters:
              - name: notify-keyspace-events
                value: lK

Alternatively, if any per-cluster defaults are not covered by component-level variables, use YAML anchors to define shared values once and merge them into each cluster entry:

# stacks/catalog/elasticache/elasticache-redis/defaults.yaml
anchors:
  default_redis: &default_redis
    engine: "redis"
    instance_type: cache.t4g.small
    num_replicas: 1
    num_shards: 0
    replicas_per_shard: 0

components:
  terraform:
    elasticache-redis:
      vars:
        enabled: true
        name: "elasticache-redis"
        family: redis7.x
        port: 6379
        at_rest_encryption_enabled: true
        transit_encryption_enabled: false
        apply_immediately: false
        automatic_failover_enabled: false
        cloudwatch_metric_alarms_enabled: false
        snapshot_retention_limit: 1
        # Global default engine version for all clusters (can be overridden per cluster)
        engine_version: "7.0"
        redis_clusters:
          redis-main:
            <<: *default_redis     # merge anchor defaults
            num_replicas: 2        # override anchor value
          redis-valkey:
            <<: *default_redis
            engine: "valkey"       # override engine to valkey
            num_shards: 3          # enable cluster mode
            replicas_per_shard: 1
          redis-cache:
            <<: *default_redis     # all anchor defaults apply

Important

In Cloud Posse's examples, we avoid pinning modules to specific versions to prevent discrepancies between the documentation and the latest released versions. However, for your own projects, we strongly advise pinning each module to the exact version you're using. This practice ensures the stability of your infrastructure. Additionally, we recommend implementing a systematic approach for updating versions to avoid unexpected changes.

Requirements

NameVersion
terraform>= 1.0.0
aws>= 5.73.0, < 7.0.0
utils>= 2.0.0, < 3.0.0

Providers

No providers.

Modules

NameSourceVersion
dns_delegatedcloudposse/stack-config/yaml//modules/remote-state2.0.0
ekscloudposse/stack-config/yaml//modules/remote-state2.0.0
iam_roles../account-map/modules/iam-rolesn/a
redis_clusters./modules/redis_clustern/a
thiscloudposse/label/null0.25.0
vpccloudposse/stack-config/yaml//modules/remote-state2.0.0
vpc_ingresscloudposse/stack-config/yaml//modules/remote-state2.0.0

Resources

No resources.

Inputs

NameDescriptionTypeDefaultRequired
additional_security_group_rulesA list of Security Group rule objects to add to the created security group, in addition to the ones this module normally creates.list(any)[]no
additional_tag_mapAdditional key-value pairs to add to each map in tags_as_list_of_maps. Not added to tags or id.
This is for some rare cases where resources want additional configuration of tags
and therefore take a list of maps with tag key, value, and additional configuration.
map(string){}no
alarm_actionsAlarm action listlist(string)[]no
alarm_cpu_threshold_percentCPU threshold alarm levelnumber75no
alarm_memory_threshold_bytesRam threshold alarm levelnumber10000000no
allow_all_egressIf true, the created security group will allow egress on all ports and protocols to all IP address.
If this is false and no egress rules are otherwise specified, then no egress will be allowed.
booltrueno
allow_ingress_from_this_vpcIf set to true, allow ingress from the VPC CIDR for this accountbooltrueno
allow_ingress_from_vpc_stagesList of stages to pull VPC ingress cidr and add to security grouplist(string)[]no
apply_immediatelyApply changes immediatelybooln/ayes
at_rest_encryption_enabledEnable encryption at restbooln/ayes
attributesID element. Additional attributes (e.g. workers or cluster) to add to id,
in the order they appear in the list. New attributes are appended to the
end of the list. The elements of the list are joined by the delimiter
and treated as a single ID element.
list(string)[]no
auth_token_enabledEnable auth tokenbooltrueno
auth_token_update_strategyStrategy to use when updating the auth_token. Valid values are SET, ROTATE, and DELETE. Defaults to ROTATE.string"ROTATE"no
auto_minor_version_upgradeSpecifies whether minor version engine upgrades will be applied automatically to the underlying Cache Cluster instances during the maintenance window. Only supported if the engine version is 6 or higher.boolfalseno
automatic_failover_enabledEnable automatic failoverbooln/ayes
availability_zonesAvailability zone IDslist(string)[]no
cloudwatch_metric_alarms_enabledBoolean flag to enable/disable CloudWatch metrics alarmsbooln/ayes
contextSingle object for setting entire context at once.
See description of individual variables for details.
Leave string and numeric variables as null to use default value.
Individual variable settings (non-null) override settings in context object,
except for attributes, tags, and additional_tag_map, which are merged.
any
{
"additional_tag_map": {},
"attributes": [],
"delimiter": null,
"descriptor_formats": {},
"enabled": true,
"environment": null,
"id_length_limit": null,
"label_key_case": null,
"label_order": [],
"label_value_case": null,
"labels_as_tags": [
"unset"
],
"name": null,
"namespace": null,
"regex_replace_chars": null,
"stage": null,
"tags": {},
"tenant": null
}
no
create_parameter_groupDefault setting for whether a new parameter group should be created for all Redis clusters. Set to false to use an existing parameter group. Can be overridden per cluster in redis_clusters.booltrueno
data_tiering_enabledEnables data tiering. Data tiering is only supported for replication groups using the r6gd node type.boolfalseno
delimiterDelimiter to be used between ID elements.
Defaults to - (hyphen). Set to "" to use no delimiter at all.
stringnullno
descriptionDefault description for all Redis replication groups. Can be overridden per cluster in redis_clusters.stringnullno
descriptor_formatsDescribe additional descriptors to be output in the descriptors output map.
Map of maps. Keys are names of descriptors. Values are maps of the form
{<br/> format = string<br/> labels = list(string)<br/>}
(Type is any so the map values can later be enhanced to provide additional options.)
format is a Terraform format string to be passed to the format() function.
labels is a list of labels, in order, to pass to format() function.
Label values will be normalized before being passed to format() so they will be
identical to how they appear in id.
Default is {} (descriptors output will be empty).
any{}no
dns_delegated_component_nameThe name of the Delegated DNS componentstring"dns-delegated"no
egress_cidr_blocksEgress CIDR blocks for the created security group. Only used when allow_all_egress is false.list(string)
[
"0.0.0.0/0"
]
no
egress_cidr_blocks_rule_descriptionDescription for the security group rule allowing egress to the CIDR blocks in egress_cidr_blocks. Only used when allow_all_egress is false.string"Selectively allow outbound traffic"no
eks_component_namesThe names of the eks componentsset(string)[]no
eks_security_group_enabledUse the eks default security groupboolfalseno
elasticache_subnet_group_nameSubnet group name for the ElastiCache instancestring""no
enabledSet to false to prevent the module from creating any resourcesboolnullno
engineDefault cache engine for all Redis clusters. Valid values: redis or valkey. Can be overridden per cluster in redis_clusters.string"redis"no
engine_versionDefault engine version for all Redis clusters (e.g. 7.0). Can be overridden per cluster in redis_clusters.stringnullno
environmentID element. Usually used for region e.g. 'uw2', 'us-west-2', OR role 'prod', 'staging', 'dev', 'UAT'stringnullno
familyRedis familystringn/ayes
final_snapshot_identifierDefault name of the final snapshot to create before deleting all Redis clusters. If null, no final snapshot is created. Can be overridden per cluster in redis_clusters.stringnullno
global_replication_group_idThe ID of the global replication group to which this replication group should belong. If this parameter is specified, the replication group is added to the specified global replication group as a secondary replication group; otherwise, the replication group is not part of any global replication group. If global_replication_group_id is set, the num_node_groups parameter cannot be set.stringnullno
id_length_limitLimit id to this many characters (minimum 6).
Set to 0 for unlimited length.
Set to null for keep the existing setting, which defaults to 0.
Does not affect id_full.
numbernullno
ingress_cidr_blocksCIDR blocks for permitted ingresslist(string)[]no
ingress_cidr_blocks_rule_descriptionDescription for the security group rule allowing ingress from the CIDR blocks in ingress_cidr_blocks.string"Selectively allow inbound traffic"no
instance_typeDefault instance type for all Redis clusters. Can be overridden per cluster in redis_clusters.stringnullno
kms_key_idThe ARN of the key that you wish to use if encrypting at rest. If not supplied, uses service managed encryption. at_rest_encryption_enabled must be set to truestringnullno
label_key_caseControls the letter case of the tags keys (label names) for tags generated by this module.
Does not affect keys of tags passed in via the tags input.
Possible values: lower, title, upper.
Default value: title.
stringnullno
label_orderThe order in which the labels (ID elements) appear in the id.
Defaults to ["namespace", "environment", "stage", "name", "attributes"].
You can omit any of the 6 labels ("tenant" is the 6th), but at least one must be present.
list(string)nullno
label_value_caseControls the letter case of ID elements (labels) as included in id,
set as tag values, and output by this module individually.
Does not affect values of tags passed in via the tags input.
Possible values: lower, title, upper and none (no transformation).
Set this to title and set delimiter to "" to yield Pascal Case IDs.
Default value: lower.
stringnullno
labels_as_tagsSet of labels (ID elements) to include as tags in the tags output.
Default is to include all labels.
Tags with empty values will not be included in the tags output.
Set to [] to suppress all generated tags.
Notes:
The value of the name tag, if included, will be the id, not the name.
Unlike other null-label inputs, the initial setting of labels_as_tags cannot be
changed in later chained modules. Attempts to change it will be silently ignored.
set(string)
[
"default"
]
no
log_delivery_configurationThe log_delivery_configuration block allows the streaming of Redis SLOWLOG or Redis Engine Log to CloudWatch Logs or Kinesis Data Firehose. Max of 2 blocks.list(map(any))[]no
maintenance_windowMaintenance window. Format: ddd:hh:mm-ddd:hh:mm (UTC). Defaults to null (AWS chooses the window).stringnullno
multi_az_enabledMulti AZ (Automatic Failover must also be enabled. If Cluster Mode is enabled, Multi AZ is on by default, and this setting is ignored)boolfalseno
nameID element. Usually the component or solution name, e.g. 'app' or 'jenkins'.
This is the only ID element not also included as a tag.
The "name" tag is set to the full id string. There is no tag with the value of the name input.
stringnullno
namespaceID element. Usually an abbreviation of your organization name, e.g. 'eg' or 'cp', to help ensure generated IDs are globally uniquestringnullno
network_typeThe network type of the cluster. Valid values: ipv4, ipv6, dual_stack.string"ipv4"no
notification_topic_arnNotification topic arnstring""no
num_replicasDefault number of replicas in the replica set for all Redis clusters. Can be overridden per cluster in redis_clusters.number1no
num_shardsDefault number of shards (node groups) for Redis clusters. Value > 0 enables cluster mode. Can be overridden per cluster in redis_clusters.number0no
ok_actionsThe list of actions to execute when this alarm transitions into an OK state from any other state. Each action is specified as an Amazon Resource Number (ARN)list(string)[]no
parameter_group_descriptionManaged by Terraformstringnullno
parameter_group_nameDefault override parameter group name for all Redis clusters. Can be overridden per cluster in redis_clusters.stringnullno
parametersDefault list of Redis parameters to configure for all clusters. Can be overridden per cluster in redis_clusters.
list(object({
name = string
value = string
}))
[]no
portPort numbernumbern/ayes
redis_clustersRedis cluster configurationmap(any)n/ayes
regex_replace_charsTerraform regular expression (regex) string.
Characters matching the regex will be removed from the ID elements.
If not set, "/[^a-zA-Z0-9-]/" is used to remove all characters other than hyphens, letters and digits.
stringnullno
regionAWS regionstringn/ayes
replicas_per_shardDefault number of replica nodes per shard for Redis clusters. Valid values are 0 to 5. Can be overridden per cluster in redis_clusters.number0no
replication_group_idDefault replication group ID for all Redis clusters. Must be 1-20 alphanumeric characters or hyphens, start with a letter, and not end with or contain consecutive hyphens. Can be overridden per cluster in redis_clusters.string""no
serverless_cache_usage_limitsThe usage limits for the serverless cache. Expected keys are data_storage (with maximum, minimum, unit) and ecpu_per_second (with maximum, minimum).map(any){}no
serverless_enabledFlag to enable/disable creation of a serverless redis clusterboolfalseno
serverless_major_engine_versionThe major version of the engine to use for the serverless clusterstring"7"no
serverless_snapshot_arns_to_restoreThe list of ARN(s) of the snapshot that the new serverless cache will be created from. Available for Redis only.list(string)[]no
serverless_snapshot_timeThe daily time (in UTC, format HH:MM) that snapshots will be created from the serverless cache.string"06:00"no
serverless_user_group_idUser Group ID to associate with the serverless replication groupstringnullno
snapshot_arnsDefault list of ARNs of Redis RDB snapshot files in S3 to restore into all new clusters. Can be overridden per cluster in redis_clusters.list(string)[]no
snapshot_nameDefault name of a snapshot to restore into all new Redis clusters. Changing this forces a new resource. Can be overridden per cluster in redis_clusters.stringnullno
snapshot_retention_limitThe number of days for which ElastiCache will retain automatic cache cluster snapshots before deleting them.number0no
snapshot_windowThe daily time range (in UTC) during which ElastiCache begins taking a daily snapshot. Format: hh:mm-hh:mm. Defaults to null (AWS chooses the window). Has no effect when snapshot_retention_limit is 0.stringnullno
stageID element. Usually used to indicate role, e.g. 'prod', 'staging', 'source', 'build', 'test', 'deploy', 'release'stringnullno
tagsAdditional tags (e.g. {'BusinessUnit': 'XYZ'}).
Neither the tag keys nor the tag values will be modified by this module.
map(string){}no
tenantID element _(Rarely used, not included by default)_. A customer identifier, indicating who this instance of a resource is forstringnullno
transit_encryption_enabledEnable TLSbooln/ayes
transit_encryption_modeTransit encryption mode. Valid values are 'preferred' and 'required'stringnullno
user_group_idsUser Group ID to associate with the replication grouplist(string)nullno
vpc_component_nameThe name of a VPC componentstring"vpc"no
vpc_ingress_component_nameThe name of a Ingress VPC componentstring"vpc"no

Outputs

NameDescription
redis_clustersRedis cluster objects
security_group_idThe security group ID of the ElastiCache Redis cluster
transit_encryption_modeTLS in-transit encryption mode for Redis cluster

Check out these related projects.

  • Cloud Posse Terraform Modules - Our collection of reusable Terraform modules used by our reference architectures.
  • Atmos - Atmos is like docker-compose but for your infrastructure

References

For additional context, refer to some of these links.

Tip

Use Terraform Reference Architectures for AWS

Use Cloud Posse's ready-to-go terraform architecture blueprints for AWS to get up and running quickly.

βœ… We build it together with your team.
βœ… Your team owns everything.
βœ… 100% Open Source and backed by fanatical support.

Request Quote

πŸ“š Learn More

Cloud Posse is the leading DevOps Accelerator for funded startups and enterprises.

Your team can operate like a pro today.

Ensure that your team succeeds by using Cloud Posse's proven process and turnkey blueprints. Plus, we stick around until you succeed.

Day-0: Your Foundation for Success

  • Reference Architecture. You'll get everything you need from the ground up built using 100% infrastructure as code.
  • Deployment Strategy. Adopt a proven deployment strategy with GitHub Actions, enabling automated, repeatable, and reliable software releases.
  • Site Reliability Engineering. Gain total visibility into your applications and services with Datadog, ensuring high availability and performance.
  • Security Baseline. Establish a secure environment from the start, with built-in governance, accountability, and comprehensive audit logs, safeguarding your operations.
  • GitOps. Empower your team to manage infrastructure changes confidently and efficiently through Pull Requests, leveraging the full power of GitHub Actions.

Request Quote

Day-2: Your Operational Mastery

  • Training. Equip your team with the knowledge and skills to confidently manage the infrastructure, ensuring long-term success and self-sufficiency.
  • Support. Benefit from a seamless communication over Slack with our experts, ensuring you have the support you need, whenever you need it.
  • Troubleshooting. Access expert assistance to quickly resolve any operational challenges, minimizing downtime and maintaining business continuity.
  • Code Reviews. Enhance your team’s code quality with our expert feedback, fostering continuous improvement and collaboration.
  • Bug Fixes. Rely on our team to troubleshoot and resolve any issues, ensuring your systems run smoothly.
  • Migration Assistance. Accelerate your migration process with our dedicated support, minimizing disruption and speeding up time-to-value.
  • Customer Workshops. Engage with our team in weekly workshops, gaining insights and strategies to continuously improve and innovate.

Request Quote

✨ Contributing

This project is under active development, and we encourage contributions from our community.

Many thanks to our outstanding contributors:

For πŸ› bug reports & feature requests, please use the issue tracker.

In general, PRs are welcome. We follow the typical "fork-and-pull" Git workflow.

  1. Review our Code of Conduct and Contributor Guidelines.
  2. Fork the repo on GitHub
  3. Clone the project to your own machine
  4. Commit changes to your own branch
  5. Push your work back up to your fork
  6. Submit a Pull Request so that we can review your changes

NOTE: Be sure to merge the latest changes from "upstream" before making a pull request!

Running Terraform Tests

We use Atmos to streamline how Terraform tests are run. It centralizes configuration and wraps common test workflows with easy-to-use commands.

All tests are located in the test/ folder.

Under the hood, tests are powered by Terratest together with our internal Test Helpers library, providing robust infrastructure validation.

Setup dependencies:

To run tests:

  • Run all tests:
    atmos test run
    
  • Clean up test artifacts:
    atmos test clean
    
  • Explore additional test options:
    atmos test --help
    

The configuration for test commands is centrally managed. To review what's being imported, see the atmos.yaml file.

Learn more about our automated testing in our documentation or implementing custom commands with atmos.

🌎 Slack Community

Join our Open Source Community on Slack. It's FREE for everyone! Our "SweetOps" community is where you get to talk with others who share a similar vision for how to rollout and manage infrastructure. This is the best place to talk shop, ask questions, solicit feedback, and work together as a community to build totally sweet infrastructure.

πŸ“° Newsletter

Sign up for our newsletter and join 3,000+ DevOps engineers, CTOs, and founders who get insider access to the latest DevOps trends, so you can always stay in the know. Dropped straight into your Inbox every week β€” and usually a 5-minute read.

πŸ“† Office Hours

Join us every Wednesday via Zoom for your weekly dose of insider DevOps trends, AWS news and Terraform insights, all sourced from our SweetOps community, plus a live Q&A that you can’t find anywhere else. It's FREE for everyone!

License

License

Preamble to the Apache License, Version 2.0

Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements.  See the NOTICE file
distributed with this work for additional information
regarding copyright ownership.  The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License.  You may obtain a copy of the License at

  https://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied.  See the License for the
specific language governing permissions and limitations
under the License.

Trademarks

All other trademarks referenced herein are the property of their respective owners.


Copyright Β© 2017-2026 Cloud Posse, LLC

README footer

Beacon