Oracle CloudStatic-verified

A Block Volume that Is Backed Up, to Another Region

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.

terraformOracle Cloudoci

Compare Block Storage across clouds →

oci-block-volumevizier 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-14 · how we verify

Use it from the registry

terraform · opentofu
module "block_volume" {
  source  = "www.iac-bazaar.com/iac-bazaar/oci-block-volume/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 · 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 static-verified because the record says so, and the link lands on this page.

README.md, GitLab, Gitea
[![IaC Bazaar: static-verified](https://www.iac-bazaar.com/api/artifacts/oci-block-volume/badge)](https://www.iac-bazaar.com/catalog/oci-block-volume?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)

Terraform module 1.0.0, static-verified on IaC Bazaar: [A Block Volume that Is Backed Up, to Another Region](https://www.iac-bazaar.com/catalog/oci-block-volume?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)

```hcl
module "block_volume" {
  source  = "www.iac-bazaar.com/iac-bazaar/oci-block-volume/oci"
  version = "1.0.0"
}
```

Preview:IaC Bazaar: static-verified

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-block-volume

A block volume with a backup policy that is assigned, and backups that leave the region. Works with Terraform and OpenTofu (>= 1.6), oci provider >= 8.0, < 9.0.

A backup policy that is assigned to nothing backs up nothing. Every OCI tenancy ships Bronze, Silver and Gold, and a volume follows one only through a separate assignment resource. The volume's page shows "Backup policy: none" for the many that were never assigned, easy to miss among the green. This module assigns one to the volume it creates - a custom policy defined here, or an Oracle policy by name - and refuses a volume with none unless accept_no_backups.

Oracle's policies stay in the region. A custom policy with destination_region copies each backup to a second region, which is the difference between a backup and a copy of the failure. A custom policy is also where retention lock lives: locked backups cannot be deleted before they expire, including by the account that made them. A custom policy without a destination region needs accept_same_region_backups.

Encryption is always on; the question is whose key. Without kms_key_id the volume uses an Oracle-managed key that protects the disk from the datacenter and not from the tenancy. Refused without accept_oracle_managed_key.

vpus_per_gb is the performance dial and the price. Auto-tune drops a detached volume to Lower Cost by itself; raising a busy one needs performance_auto_tune_max_vpus.

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

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.

View module
Static validatedLive test pending

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.

View module
Static validatedLive test pending

oci-file-storage

Elastic NFSv3 file system with mount target, export options, snapshots and NSG-scoped access.

View module
Static validatedLive test pending

oci-object-storage-bucket

Bucket with versioning, lifecycle/auto-tiering, retention rules, replication and pre-authenticated request support.

View module
Static validatedLive test pending

exoscale-block-storage

Snapshots exist as a resource you take and nothing on the platform schedules one; a volume attaches from the instance side, one instance at a time, in its zone; and a volume made from a snapshot is the restore path. A baseline snapshot when asked, restore from a snapshot when given, and an output that says no schedule exists.

View module
Static validatedLive test pending

ibm-block-volume

VPC backup policies match volumes by user tag, so a volume created without the tag sits silently outside the policy; encryption is provider-managed unless a root key CRN is given; and an attachment can delete the volume with the instance. The policy created with its plan and the volume tagged with the tag it matches (none by name), your key when given, the volume kept on instance deletion.

View module