Memorystore Redis/Valkey
Private Memorystore instance or cluster (Redis or Valkey) with auth, TLS and maintenance policy on your VPC.
Compare In-Memory Cache across clouds →
Part of: GCP Production Landing Zone
Verification
Live-testedReally 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
- SHA-256 checksum
- Cosign signature
Functional
- Live-tested - applied, verified, destroyed
Last verified 2026-06-30 · how we verify
Verify this download
cosign · sha-256Don'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 gcp-memorystore-1.0.0.sigstore.json \
https://www.iac-bazaar.com/api/artifacts/gcp-memorystore/signature
# 3. Verify the tarball you downloaded
cosign verify-blob \
--key cosign.pub \
--bundle gcp-memorystore-1.0.0.sigstore.json \
gcp-memorystore-1.0.0.tar.gz
# → Verified OK
# 4. (optional) confirm the checksum too
echo "3a5375f3a2cfc84a66420180e291a27918621d7459764d5912355380d27c0d1b gcp-memorystore-1.0.0.tar.gz" | sha256sum -cUse it from the registry
terraform · opentofumodule "memorystore" {
source = "www.iac-bazaar.com/iac-bazaar/gcp-memorystore/gcp"
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 · attributionPaste 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.
[](https://www.iac-bazaar.com/catalog/gcp-memorystore?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, live-tested on IaC Bazaar: [Memorystore Redis/Valkey](https://www.iac-bazaar.com/catalog/gcp-memorystore?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "memorystore" {
source = "www.iac-bazaar.com/iac-bazaar/gcp-memorystore/gcp"
version = "1.0.0"
}
```Preview:
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
gcp-memorystore
A private Memorystore cache on your VPC — Valkey (the 2026-current
google_memorystore_instance path), classic Redis
(google_redis_instance), or a sharded Redis cluster
(google_redis_cluster) — selected by a single flavor variable. One module
call gives you a cache that is private, TLS-encrypted, auth-protected and
deletion-protected by default. Works with Terraform and OpenTofu
(>= 1.6), Google provider >= 7.0, < 8.0.
Timing: a real instance takes five to ten minutes to provision.
Design & secure defaults
- Private connectivity only. Valkey and Redis-cluster attach to your VPC
via PSC auto-connection; classic Redis defaults to
connect_mode = PRIVATE_SERVICE_ACCESS. No public endpoint is ever exposed. - TLS in transit on (
transit_encryption_enabled = true) →SERVER_AUTHENTICATION. The per-flavor enum spelling is handled for you. - Auth on (
iam_auth_enabled = true): IAM auth for Valkey / Redis-cluster, OSS Redis AUTH (auth_string) for classic Redis, which has no IAM-auth mode. - Resilient placement:
MULTI_ZONEdistribution andreplica_count = 1by default. - Durable:
RDBpersistence on by default so data survives a restart. - Deletion protection on by default.
The flavor switch is exactly one resource — the module never creates more
than one cache.
Requirements
| Requirement | Version |
|---|---|
| Terraform / OpenTofu | >= 1.6 |
hashicorp/google | >= 7.0, < 8.0 |
License
Commercial — LicenseRef-IaCBazaar-Commercial. See the IaC Bazaar terms.
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
gcp-datastream
A stream is created NOT_STARTED and replicates nothing until somebody starts it; the source password is a literal in state unless it is a Secret Manager reference; public connectivity means the database admits Google's published ranges; and backfill_none is change capture with no history. Running from apply, private connection peered into your VPC, secret required, backfill on.
gcp-firestore
Type, location and CMEK cannot be changed after creation - getting one wrong means exporting every document into a new database and repointing every client. delete_protection defaults OFF, and Firestore has no snapshots: point-in-time recovery is the only way back and only covers incidents after it was enabled.
gcp-looker
A Looker (Google Cloud core) instance reachable over Private Service Connect from the VPCs you allow, no public address, sign-in limited to your email domains, encrypted with your Cloud KMS key, in a maintenance window you chose. The OAuth client secret is sensitive and never output; the edition has no default because the annual editions commit for a year.
gcp-alloydb
AlloyDB cluster with primary + read-pool instances, PSC connectivity, automated backups and columnar/vector engine flags.
gcp-bigquery-dataset
Datasets with partitioned/clustered tables, authorized views, CMEK and dataset-level access controls.
gcp-bigtable
A single-cluster Cloud Bigtable instance (one 1-node SSD cluster, the smallest footprint) plus a table with column families, IAM-only access, optional CMEK, and deletion protection on.