Google CloudLive-testedattested

Cloud Filestore NFS Share

A managed Cloud Filestore NFS share for GKE and Compute Engine, VPC-peered with no public exposure, optional per-client export rules for least-privilege access, and deletion protection on.

terraformGoogle Cloudgcp

Compare Shared File Storage across clouds →

gcp-filestorevizier 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 gcp-filestore-1.0.0.sigstore.json \
  https://www.iac-bazaar.com/api/artifacts/gcp-filestore/signature

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

# 4. (optional) confirm the checksum too
echo "dadd17d8f503a68ab4b9a52eb7ab4adeca9db2b2b2dc9641a22fd66a06d7d971  gcp-filestore-1.0.0.tar.gz" | sha256sum -c

Use it from the registry

terraform · opentofu
module "filestore" {
  source  = "www.iac-bazaar.com/iac-bazaar/gcp-filestore/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 · 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/gcp-filestore/badge)](https://www.iac-bazaar.com/catalog/gcp-filestore?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)

Terraform module 1.0.0, live-tested on IaC Bazaar: [Cloud Filestore NFS Share](https://www.iac-bazaar.com/catalog/gcp-filestore?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)

```hcl
module "filestore" {
  source  = "www.iac-bazaar.com/iac-bazaar/gcp-filestore/gcp"
  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

gcp-filestore

A managed Cloud Filestore NFS file share for GKE and Compute Engine workloads. Connected to a VPC over private peering (no public exposure), with optional per-client NFS export rules for least-privilege access and deletion protection on by default. Works with Terraform and OpenTofu (>= 1.6), Google provider >= 7.0, < 8.0.

Defaults:

  • tier = "BASIC_HDD" (the cheapest tier), NFS_V3
  • Private connectivity via DIRECT_PEERING to your VPC; no public IP
  • deletion_protection_enabled = true

Cost: BASIC_HDD's minimum share is 1024 GB (1 TiB) — capacity cannot go lower, so even the smallest instance reserves 1 TiB at $0.20/GB-month ($200/mo). This is the priciest-to-leave-running of the storage modules; tear it down when done.

Requirements

  • Terraform or OpenTofu >= 1.6
  • hashicorp/google >= 7.0, < 8.0
  • API: file.googleapis.com

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
  • Notes

Related modules

Static validatedLive test pending

gcp-backup-dr

The vault and the plan are what the console shows; the association is what makes a backup exist, and a plan associated with nothing backs up nothing. Enforced retention is the setting ransomware cannot undo - no backup younger than it can be deleted by anyone - and WITHIN_PROJECT access lets a compromised owner restore everything. Resources come with the plan; 14 days enforced; org-scoped.

View module
Static validatedLive test pending

gcp-persistent-disk

A snapshot schedule is a resource policy, and its attachment to a disk is a separate resource, so a schedule in the console with no disks is the usual state; encryption is Google-managed unless a KMS key is given. The daily schedule created and attached or yours attached (none by name), your key when given, and the disk attached from its own side so the instance's disk list is left alone.

View module
Static validatedLive test pending

gcp-parallelstore

A persistent Parallelstore instance on the private services range you already allocated, because a VPC has one service networking peering and a module that made another would break the databases on it. Twelve TiB minimum in steps of four, balanced striping, one zone. SCRATCH, which loses the data on maintenance, is accepted by name; the bucket you import from is the durable copy.

View module
Static validatedLive test pending

gcp-snapshot-schedule

The resource policy is the schedule; a disk follows it only through a separate attachment, so a policy that reads daily-keep-30 in the console and is attached to nothing has never taken a snapshot. Takes the disks with the schedule and refuses one with none. Keeps the snapshots when the disk is deleted, because APPLY_RETENTION_POLICY lets them age out in exactly the window they are needed.

View module
Static validatedLive test pending

gcp-storage-transfer

delete_objects_unique_in_sink turns a backup into a mirror: an object deleted at the source is deleted at the destination on the next run, replicating the event the copy was meant to survive; and a job with no notification fails while its status stays ENABLED. Copies only, refuses mirroring and moving unless accepted, publishes every outcome to a topic, and spells out what the service agent needs.

View module
Live-tested

gcp-gcs-bucket

Hardened GCS bucket with uniform access, versioning, lifecycle/soft-delete policies, CMEK and least-privilege IAM.

View module