Linode Compute Instance (production-ready)
Hardened Linode VM with cloud-init, disk encryption, reverse DNS, backups, and firewall attachment in one apply.
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 linode-instance-1.0.0.sigstore.json \
https://www.iac-bazaar.com/api/artifacts/linode-instance/signature
# 3. Verify the tarball you downloaded
cosign verify-blob \
--key cosign.pub \
--bundle linode-instance-1.0.0.sigstore.json \
linode-instance-1.0.0.tar.gz
# → Verified OK
# 4. (optional) confirm the checksum too
echo "0d55dede1e3f52a6bd804d107f6a5e6f581f618f698d0ea8d0c22eabb6ceb8a4 linode-instance-1.0.0.tar.gz" | sha256sum -cUse it from the registry
terraform · opentofumodule "instance" {
source = "www.iac-bazaar.com/iac-bazaar/linode-instance/linode"
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/linode-instance?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, plan-validated on IaC Bazaar: [Linode Compute Instance (production-ready)](https://www.iac-bazaar.com/catalog/linode-instance?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "instance" {
source = "www.iac-bazaar.com/iac-bazaar/linode-instance/linode"
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
linode-instance
Hardened Linode VM with cloud-init, disk encryption, reverse DNS, backups, and
firewall attachment in one apply. Works with Terraform and OpenTofu
(>= 1.6), Linode provider >= 3.14, < 4.0.
Secure defaults:
- Local Disk Encryption (LDE) enabled by default
- Backups enabled by default
- SSH-key-first auth: keys are uploaded to the account profile
(
linode_sshkey) and authorized for root;root_passstays optional and sensitive. The provider's v3.14 rule (credentials are mandatory when an image is deployed) is enforced with a clear plan-time precondition. - Optional VPC interface as the primary NIC (with or without 1:1 NAT), Cloud
Firewall attachment (
linode_firewall_device), and PTR record (linode_rdns) - Cloud-init user data wired through the Linode Metadata service (base64-encoding handled for you)
Requirements
- Terraform or OpenTofu
>= 1.6 linode/linodeprovider>= 3.14, < 4.0- You must supply at least one SSH key or a
root_pass(provider v3.14 auth requirement — enforced at plan time). disk_encryptionandcloud_init_user_datarequire regions with the LDE and Metadata capabilities respectively.
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
Related modules
linode-image
A Linode image captured from an instance disk, replicated to the regions you name (one region has to be accepted by name), cloud-init ready, with the label carrying the build. The image is the disk at that moment, secrets and all: build the source clean.
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.