AWSLive-testedattested

ElastiCache for Redis / Valkey

A cluster-mode-disabled ElastiCache Redis/Valkey cache with encryption at rest and in transit both on, no public exposure, and the subnet group and security group created for you.

terraformAWSaws

Compare In-Memory Cache across clouds →

Part of: AWS Production Landing Zone

aws-elasticache-redisvizier v1.2.0

Verification

Live-tested

Really deployed to a cloud sandbox, verified against its outputs and assertions, then destroyed - with the teardown confirmed.

Conformance

  • Static validation (fmt · validate · tflint)
  • Security scan clean (Checkov)
  • Plan test superseded by live test

Provenance

Functional

  • Live-tested - applied, verified, destroyed

Last verified 2026-06-30 · how we verify

Verify this download

cosign · sha-256

Don't take our word for it. Every release is signed with cosign - check the bytes against our pinned public key before you trust them.

# 1. Our pinned public key - fetch once, trust out-of-band
curl -O https://www.iac-bazaar.com/cosign.pub

# 2. This module's Sigstore bundle
curl -o aws-elasticache-redis-1.0.0.sigstore.json \
  https://www.iac-bazaar.com/api/artifacts/aws-elasticache-redis/signature

# 3. Verify the tarball you downloaded
cosign verify-blob \
  --key cosign.pub \
  --bundle aws-elasticache-redis-1.0.0.sigstore.json \
  aws-elasticache-redis-1.0.0.tar.gz
# → Verified OK

# 4. (optional) confirm the checksum too
echo "e8d988b12b946eecf5bd97ee73773915adce54392cc21c995b5e85054c382ec9  aws-elasticache-redis-1.0.0.tar.gz" | sha256sum -c

Use it from the registry

terraform · opentofu
module "elasticache_redis" {
  source  = "www.iac-bazaar.com/iac-bazaar/aws-elasticache-redis/aws"
  version = "1.0.0"
}

Needs a registry token from /account/tokens. The module itself is free; the account is what identifies you. Full setup: registry docs.

Cite it in your README

badge · attribution

Paste this beside the module in the repository that uses it. The badge is rendered from this artifact's verification record, so it reads live-tested because the record says so, and the link lands on this page.

README.md, GitLab, Gitea
[![IaC Bazaar: live-tested](https://www.iac-bazaar.com/api/artifacts/aws-elasticache-redis/badge)](https://www.iac-bazaar.com/catalog/aws-elasticache-redis?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)

Terraform module 1.0.0, live-tested on IaC Bazaar: [ElastiCache for Redis / Valkey](https://www.iac-bazaar.com/catalog/aws-elasticache-redis?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)

```hcl
module "elasticache_redis" {
  source  = "www.iac-bazaar.com/iac-bazaar/aws-elasticache-redis/aws"
  version = "1.0.0"
}
```

Preview:IaC Bazaar: live-tested

Inputs & outputs

Create a free account to read this module's contract

The declared contract - every input name, type, default and description, plus every output - is shown to signed-in accounts, not to anonymous visitors.

A free account sees the contract of every module in the catalogue. There is no subscription and nothing to buy - the modules are free to download, and they run under Vizier.

Documentation

aws-elasticache-redis

Amazon ElastiCache for Redis / Valkey, cluster mode disabled (a single primary with optional read replicas). Works with Terraform and OpenTofu (>= 1.6), AWS provider >= 6.0, < 7.0. Secure by default and self-contained: encryption at rest and in transit are both on, the cache is never publicly reachable, and the networking pieces (subnet group + security group) are created for you — falling back to the account's default VPC so a minimal cache applies with just a name.

Secure defaults:

  • Encryption at rest on (at_rest_encryption_enabled = true); use a customer-managed key via kms_key_id, otherwise the AWS-managed ElastiCache key
  • Encryption in transit (TLS) on (transit_encryption_enabled = true); optional auth_token adds Redis AUTH on top (the token is never an output)
  • No public exposure — access is via a module-created security group that opens the cache port only to allowed_cidrs / allowed_security_group_ids (no ingress at all by default)
  • Automatic minor version upgrades on, to pick up security patches
  • Footgun guards (plan-time preconditions): Multi-AZ implies automatic failover, automatic failover implies num_cache_clusters >= 2, auth_token implies TLS, kms_key_id implies at-rest encryption

Cost note: the default cache.t4g.micro single node is the cheapest option (~$0.016/hr). HA (replicas + automatic_failover_enabled + multi_az_enabled) is off by default — opt in for production.

Security notes

  • Clients must speak TLS while transit_encryption_enabled is on. Add an auth_token for password auth; the token is supplied via TF_VAR_auth_token or a secrets manager and is never exposed as an output.
  • Keep allowed_cidrs / allowed_security_group_ids as tight as possible — prefer granting an application security group over a CIDR range.
  • For real deployments pin subnet_ids to private subnets instead of relying on the default-VPC fallback.

Requirements

  • Terraform or OpenTofu >= 1.6
  • hashicorp/aws >= 6.0, < 7.0

License

Commercial — IaC Bazaar EULA. © IaC Bazaar. Original work (not derived from a third-party module).

Usage code & full reference need an account

The complete copy-paste usage, the full input/output reference, and operational notes are free with an account - shown here and bundled in the download. Sign in and this section fills in.

  • Usage
  • Inputs
  • Outputs

Related modules

Static validatedLive test pending

aws-keyspaces

point_in_time_recovery defaults to DISABLED and Keyspaces has no snapshots or automated backups, so off means a dropped table is simply gone. PITR on, a customer-managed key, and the two one-way doors - client-side timestamps and TTL - named rather than set quietly.

View module
Static validatedLive test pending

aws-database-proxy

Amazon RDS Proxy in front of an RDS instance or Aurora cluster: TLS required, clients authenticate with IAM tokens while the proxy reads the password from Secrets Manager, through a role limited to those secrets. Debug logging writes SQL statement text to the logs, so it is off unless that is accepted. End-to-end IAM removes the stored password entirely.

View module
Static validatedLive test pending

aws-dax-cache

DynamoDB Accelerator with TLS and encryption at rest. DAX leaves both off by default, and neither can be turned on for an existing cluster, so a fix means a new cluster. This module also creates its own security group (DAX otherwise uses the VPC default), a service role limited to the named tables and their indexes, and states that writes bypassing DAX leave stale reads until the TTL.

View module
Static validatedLive test pending

aws-neptune

Neptune has no user, no password and no GRANT. Authorization is IAM and it defaults to OFF, so anything that can reach port 8182 can read every edge and drop the lot. IAM auth on, storage encrypted, and the audit log driven from one variable because its two halves live in different resources and either alone logs nothing.

View module
Static validatedLive test pending

aws-dms

ssl_mode defaults to none in AWS, so a task reads your entire production database and writes it elsewhere unencrypted. This defaults to require, refuses none unless stated, and pushes the credential into Secrets Manager rather than state.

View module
Static validatedLive test pending

aws-quicksight

A QuickSight subscription on Enterprise edition through IAM Identity Center, with admin, author and reader groups, termination protection on because unsubscribing deletes every dashboard, and a VPC connection with its own role so a private database stays private. The authentication method is permanent; Standard edition and QuickSight-managed users are accepted by name.

View module