AWSStatic-verified

MemoryDB with a Real ACL, Not open-access

Durable Redis-compatible storage with an ACL holding real users, authenticated through IAM. MemoryDB ships an ACL named open-access that accepts any connection reaching the port with no credentials; this module will not use it.

terraformAWSaws
aws-memorydbvizier v1.2.0

Verification

Static-verified

Passed: validated and lint-clean (provider-schema-validated for AWS/Azure/GCP; Terraform-language lint elsewhere).

Conformance

  • Static validation (fmt · validate · tflint)
  • Security scan pending (Checkov)
  • Plan tests (mocked: validation rules · outputs)

Provenance

  • SHA-256 checksum
  • Signature (pending)

Functional

  • Live test pending (no cloud run yet)

Last verified 2026-09-12 · how we verify

Use it from the registry

terraform · opentofu
module "memorydb" {
  source  = "www.iac-bazaar.com/iac-bazaar/aws-memorydb/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.

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-memorydb

An Amazon MemoryDB cluster with a real ACL, its users, subnet group and parameter group. Works with Terraform and OpenTofu (>= 1.6), AWS provider >= 6.0, < 7.0.

Why MemoryDB rather than ElastiCache. ElastiCache replicates asynchronously, so a failover can drop writes the client was already told had succeeded. MemoryDB commits every write to a multi-availability-zone transaction log before acknowledging it. That durability is the whole reason to pay the difference - which is why this module defaults to a replica per shard and requires two subnets.

The ACL is the part people get wrong. MemoryDB ships an ACL named open-access, and a cluster pointed at it accepts any connection reaching the port with no credentials at all. This module will not use it. It creates an ACL holding real users and authenticates them through IAM by default, so no password is written into the state file and rotation does not mean editing infrastructure code.

Other defaults worth knowing:

  • tls_enabled is hard-coded on, not a variable. Encryption in transit is settable only at creation, so a cluster created without it stays without it
  • snapshot_retention_days is 7. AWS defaults it to 0, which leaves point-in-time recovery with no points
  • A precondition asks you to confirm num_replicas_per_shard = 0: the log keeps the data, but a lost node is an outage until AWS rebuilds it
  • Each access_string is validated to start with on . A user whose rule starts with off is created successfully and cannot connect
  • The example rules are narrow (~app:*, +@read +@write) rather than ~* +@all

Verification

Static validation runs tofu fmt, init, validate, tflint and checkov. This module has not yet had a live test, so it is published as statically validated with its live test pending and does not carry the live-tested mark.

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

Related modules