AWSStatic-verified

A DynamoDB Cache Encrypted From the Start

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.

terraformAWSaws

Compare In-Memory Cache across clouds →

aws-dax-cachevizier 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 clean (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-16 · how we verify

Use it from the registry

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

DynamoDB Accelerator (DAX). Works with Terraform and OpenTofu (>= 1.6), aws provider >= 6.0, < 7.0.

Both encryption settings are off unless you choose them, and cannot be changed later. A DAX cluster's endpoint is unencrypted and its data at rest is unencrypted by default. AWS cannot turn on either for an existing cluster: the fix is a new cluster and moving the traffic. This module creates every cluster with TLS and encryption at rest. Clients need a recent DAX client, and a TLS cluster refuses plaintext connections.

Not the VPC's default security group. Without a security group DAX uses the VPC's default one. This module creates its own and opens only the cluster's port, to the networks and security groups you name.

The service role reaches only your tables. DAX calls DynamoDB with its own role; this one is limited to the tables in table_arns and their indexes, and allow_writes = false makes it a read-only cache.

A cache serves stale reads. Items and query results stay cached for 5 minutes by default (record_ttl_seconds, query_ttl_seconds), including after something writes to the table without going through DAX.

Some changes replace the cluster: name, node_type and subnet_ids.

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

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-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
Static validatedLive test pending

aws-opensearch-serverless

A collection cannot exist without an encryption policy and the quickest one uses the AWS-owned key; the network policy decides whether the endpoint answers on the internet; without a data access policy nobody can read or write, with a wide one everyone can; indexes grow until a policy expires them. Private through VPC endpoints (public by name), your key when given, principals named.

View module