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)
- No applicable security policies for this provider
- 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 vultr-compute-stack-1.0.0.sigstore.json \
https://www.iac-bazaar.com/api/artifacts/vultr-compute-stack/signature
# 3. Verify the tarball you downloaded
cosign verify-blob \
--key cosign.pub \
--bundle vultr-compute-stack-1.0.0.sigstore.json \
vultr-compute-stack-1.0.0.tar.gz
# → Verified OK
# 4. (optional) confirm the checksum too
echo "f11ccf305da93c5aede58df6158c77e1b91e33d56c34f627a938e7c827694167 vultr-compute-stack-1.0.0.tar.gz" | sha256sum -cUse it from the registry
terraform · opentofumodule "compute_stack" {
source = "www.iac-bazaar.com/iac-bazaar/vultr-compute-stack/vultr"
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/vultr-compute-stack?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, plan-validated on IaC Bazaar: [Vultr Compute Stack](https://www.iac-bazaar.com/catalog/vultr-compute-stack?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "compute_stack" {
source = "www.iac-bazaar.com/iac-bazaar/vultr-compute-stack/vultr"
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
vultr-compute-stack
A Vultr compute stack: N identical instances on a private VPC behind a default-deny cloud firewall, with optional per-instance block storage and an optional reserved (static) IP that survives instance rebuilds.
Status: static-validated, live-test pending. Validated with
tofu validate+tflint+checkovagainst thevultr/vultrprovider. Not yet applied against a live Vultr account, so it ships under live-test quarantine.
Design & secure defaults
- SSH closed by default. Vultr firewall groups deny inbound traffic that
matches no rule, so SSH stays shut until you list
allowed_ssh_cidrs. Add arbitraryfirewall_rulesfor everything else. - Private networking. Instances join a dedicated VPC (created unless you
pass an existing
vpc_id); setdisable_public_ipv4 = truefor VPC-only or IPv6-only fleets. - Backups on by default (
backups_enabled = true) with a configurable schedule — turn off for ephemeral environments. - Optional persistence:
block_storage_size_gbattaches a live NVMe (or HDD) volume per instance;create_reserved_ippins a static IPv4 to instance 1.
Provider
vultr/vultr >= 2.0, < 3.0. Requires Terraform/OpenTofu >= 1.6.
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
- Key inputs
- Outputs
Related modules
vultr-snapshot
A Vultr snapshot of an instance, which is Vultr's custom image: global, deployable in any region, billed per gigabyte stored. The snapshot is the instance at that moment, secrets and all, so build the source clean and stop it first; the description carries the build.
tencent-cvm-instance
A CVM instance in your subnet with login by key pair and no password, ordered security groups, no public address (one by name), the system disk encrypted with your KMS key (the service key by name), the Cloud Workload Protection and Cloud Monitor agents left on, a CAM role when you name one, and API termination refused. Pay-as-you-go by the hour.
aws-lightsail-instance
A Lightsail instance is created with 22 and 80 open to every address; its public address changes when it stops unless a static IP is attached, and every DNS record pointing at it is then wrong; and automatic snapshots are off. The port list replaced by your rules with SSH from anywhere accepted by name, a static IP attached, and the daily AutoSnapshot add-on on at the hour you choose.
scaleway-instance
A Scaleway instance on a Private Network with a required security group (the project default allows everything inbound), no public address unless a flexible IP is accepted by name, the project's SSH keys and no password, a Block Storage root volume deleted with the instance, cloud-init, and protection from deletion (off by name).
ibm-vsi-instance
A VPC virtual server in your subnet with the SSH keys you name and no password, security groups on the primary interface, no floating IP, the boot volume encrypted with a Key Protect key (IBM's key by name), secure boot on, and the metadata service on so a trusted profile can be the instance identity instead of a stored API key.
alicloud-ecs-instance
An ECS instance in your vSwitch with login by key pair and no password, no public address unless bandwidth above zero is accepted by name, the system disk encrypted with your KMS key (the service key by name), the metadata service on IMDSv2 only with a hop limit of one, the Security Center agent on, and deletion protection. Pay-as-you-go.