File Storage (NFS)
Elastic NFSv3 file system with mount target, export options, snapshots and NSG-scoped access.
Verification
Static-verifiedPassed: 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
- Cosign signature
Functional
- Live test pending (no cloud run yet)
Last verified 2026-06-28 · 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 oci-file-storage-1.0.0.sigstore.json \
https://www.iac-bazaar.com/api/artifacts/oci-file-storage/signature
# 3. Verify the tarball you downloaded
cosign verify-blob \
--key cosign.pub \
--bundle oci-file-storage-1.0.0.sigstore.json \
oci-file-storage-1.0.0.tar.gz
# → Verified OK
# 4. (optional) confirm the checksum too
echo "54998be939d7a82594a47bf9c7a7190dbffbd673c28a684c015cecd4728f012c oci-file-storage-1.0.0.tar.gz" | sha256sum -cUse it from the registry
terraform · opentofumodule "file_storage" {
source = "www.iac-bazaar.com/iac-bazaar/oci-file-storage/oci"
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 static-verified because the record says so, and the link lands on this page.
[](https://www.iac-bazaar.com/catalog/oci-file-storage?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, static-verified on IaC Bazaar: [File Storage (NFS)](https://www.iac-bazaar.com/catalog/oci-file-storage?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "file_storage" {
source = "www.iac-bazaar.com/iac-bazaar/oci-file-storage/oci"
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
oci-file-storage — File Storage (NFS)
Elastic NFSv3 file system on OCI File Storage: an encrypted-at-rest file
system (optionally keyed by your own Vault key), a mount target that
consumes one private IP in a subnet, an export that binds the file system
into the mount target's export set with deny-leaning per-client options, and
optional on-demand snapshots. Works with Terraform and OpenTofu
(>= 1.6), OCI provider >= 8.0, < 9.0.
Status: static-validated, live-test pending. Ships under live-test quarantine — validated with
tofu fmt,tofu validate, andtflint. Real apply → mount/verify → destroy against an OCI tenancy is pending a cloud sandbox. The mount target consumes a subnet IP and needs NFS ports (111, 2048-2050) open in its NSG to verify a mount, so it is gated until the live lane exists.
Secure / sane defaults
- Private only. The mount target is placed on a subnet you choose and is
never assigned a public address. NFSv3 has no transport encryption, so the
documented posture is: private subnet + an NSG that allows only TCP/UDP
111and TCP/UDP2048-2050from trusted client CIDRs. - Deny-by-default exports. With no
export_options, the export grants no client access — you must add explicit rules. Each rule defaults toROOTidentity squash (remote root is remapped tonobody/65534) andrequire_privileged_source_port = true(clients must use a port < 1024). - Encryption at rest always on. Bring your own key via
kms_key_id(Vault); null uses Oracle-managed keys (still encrypted). - Least-privilege auth.
allowed_authdefaults to["SYS"]; tighten to Kerberos (KRB5/KRB5I/KRB5P) where your fleet supports it.
Requirements
- Terraform or OpenTofu
>= 1.6 oracle/oci>= 8.0, < 9.0
License
Commercial — LicenseRef-IaCBazaar-Commercial. © 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 (key)
- Outputs
- Notes
Related modules
oci-block-volume
Every tenancy ships Bronze, Silver and Gold policies and a volume follows one only through a separate assignment - the page reads Backup policy: none for the many never assigned. Assigns a policy to the volume it creates and refuses one without. Custom schedules add destination_region and retention lock, which Oracle policies lack: same-region backups are a copy of the failure.
oci-backup-policy
A block volume backup policy that many volumes share: incremental daily backups kept thirty days and full weekly backups kept a year, each copied to a second region (one region by name) and encrypted there with a key of yours when given, deletion prevented until retention ends (deletable by name), and every volume in the map assigned, because a policy with no assignment backs up nothing.
oci-lustre
OCI File Storage with Lustre in your subnet, reachable only through the network security groups you name, encrypted with a Vault key of yours (the Oracle-managed key by name), with root on clients squashed to a UID and GID you chose except for the clients you exempt (NONE by name), on the throughput tier you chose, with capacity checked against the 31,200 GB step before the plan.
oci-object-storage-bucket
Bucket with versioning, lifecycle/auto-tiering, retention rules, replication and pre-authenticated request support.
tencent-cfs-file-system
A Tencent Cloud CFS file system (NFS) in your subnet behind its own access group, whose one rule admits the CIDR you name read-write with root squashed (0.0.0.0/0 has to be accepted by name), on the standard or high-performance tier. CFS encrypts at rest with keys it holds, which the module says rather than hides.
azure-file-share
A share inherits its security boundary from the storage account, which defaults to public access and TLS 1.0; the quota is the price on premium; and a share is backed up only when a Recovery Services vault protects it through a policy and an assignment. A private account with TLS 1.2, the quota deliberate, share soft delete on, vault, policy and protection created together (none by name).