DRG Hub & Spoke Connectivity
Dynamic Routing Gateway with VCN attachments, custom DRG route tables, remote peering and IPSec/FastConnect attach points.
Verification
Plan-validatedPassed: module logic verified on a mocked plan - inputs, validation rules, conditional creation and outputs resolve (no real provider, no cloud).
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-drg-hub-1.0.0.sigstore.json \
https://www.iac-bazaar.com/api/artifacts/oci-drg-hub/signature
# 3. Verify the tarball you downloaded
cosign verify-blob \
--key cosign.pub \
--bundle oci-drg-hub-1.0.0.sigstore.json \
oci-drg-hub-1.0.0.tar.gz
# → Verified OK
# 4. (optional) confirm the checksum too
echo "5375d630e5873c4efec805c2fb44d4c755598367588479cc372079fc1e649926 oci-drg-hub-1.0.0.tar.gz" | sha256sum -cUse it from the registry
terraform · opentofumodule "drg_hub" {
source = "www.iac-bazaar.com/iac-bazaar/oci-drg-hub/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 plan-validated because the record says so, and the link lands on this page.
[](https://www.iac-bazaar.com/catalog/oci-drg-hub?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, plan-validated on IaC Bazaar: [DRG Hub & Spoke Connectivity](https://www.iac-bazaar.com/catalog/oci-drg-hub?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "drg_hub" {
source = "www.iac-bazaar.com/iac-bazaar/oci-drg-hub/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-drg-hub
Status: static-validated, live-test pending. This module ships under live-test quarantine — it passes
tofu fmt,tofu validateandtflint, but a real apply → verify → destroy has not yet run (no OCI cloud sandbox available). Promotion to a full live-tested artifact follows when a sandbox exists.
Dynamic Routing Gateway as a hub-and-spoke connectivity fabric: one DRG with
VCN spoke attachments, custom DRG route tables, route distributions, optional
remote peering (cross-region / cross-tenancy), and Site-to-Site VPN (IPSec)
attach points to on-prem CPE devices. Works with Terraform and OpenTofu
(>= 1.6), OCI provider >= 8.0, < 9.0.
Secure / deliberate defaults:
- VCN attachments bind to an explicit custom DRG route table when one is named, so transit routing is intentional rather than the auto-generated default.
- IPSec connections require
static_routes(the on-prem prefixes) — no wildcard transit is implied; you advertise exactly what you mean to. - Remote Peering Connections are created un-peered; you peer them deliberately (peering is a cross-tenancy trust decision, not a default).
- The DRG and its attachments create no public exposure; the DRG itself is free.
Requirements
- Terraform or OpenTofu
>= 1.6 - Provider
oracle/oci>= 8.0, < 9.0
License
Commercial — LicenseRef-IaCBazaar-Commercial.
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
oci-remote-peering
A remote peering connection is half a link until the requestor connects to the acceptor, and a PEERED connection with no DRG route import and no VCN route rule passes nothing while reading as connected. Acceptor and requestor halves from one module, the peering status exported, and an output that lists the routes and security rules that live outside it and are the usual reason no packets cross.
oci-fastconnect
One virtual circuit is one cable that goes down for maintenance, and the SLA assumes two; BFD is off by default, leaving a failed link to BGP hold timers for up to ninety seconds; and a circuit without a gateway is PROVISIONED and reaches no VCN. BFD on, the DRG required, a redundant partner circuit declared or the single circuit accepted by name, and the redundancy metadata exported.
oci-local-peering
A local peering gateway with no peer stays NEW forever, and a PEERED pair with no route rule sending the other CIDR to the gateway passes nothing while reading as connected. Both gateways created and connected from one call, a route table with the rule to the peer created on each side for the subnets that should reach across, overlap refused, and an output that says it is not transitive.
oci-nat-gateway
A NAT gateway for an existing VCN with the private route table that sends subnets through it, because a gateway no table points at forwards nothing. The NAT address is ephemeral unless a reserved public IP is attached, and every allow-list that named it breaks on recreation; the ephemeral address is accepted by name. block_traffic, the kill switch, stays off and is exported.
oci-site-to-site-vpn
Every OCI IPSec tunnel is created with IKE version 1 unless told otherwise, and negotiates from a compatibility list that still accepts SHA-1, AES-128 and DH group 2 - so the weakest option a peer proposes is what it gets, and the tunnel shows UP. IKEv2 on both tunnels, explicit proposals for both phases with the weak ones refused by validation, BGP routing, and one configured tunnel only by name.
oci-vcn
Production VCN with public/private subnets, internet/NAT/service gateways, route tables, NSGs and IPv6 - the module every OCI tenancy starts with.