Linode Cloud Firewall Baseline
Opinionated stateful firewall with deny-by-default inbound, curated allow rules, and multi-device attachment.
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 linode-firewall-1.0.0.sigstore.json \
https://www.iac-bazaar.com/api/artifacts/linode-firewall/signature
# 3. Verify the tarball you downloaded
cosign verify-blob \
--key cosign.pub \
--bundle linode-firewall-1.0.0.sigstore.json \
linode-firewall-1.0.0.tar.gz
# → Verified OK
# 4. (optional) confirm the checksum too
echo "c26ed6bda28563fb335f01d10f17ff8c11573f1de48447861d01371d2d812510 linode-firewall-1.0.0.tar.gz" | sha256sum -cUse it from the registry
terraform · opentofumodule "firewall" {
source = "www.iac-bazaar.com/iac-bazaar/linode-firewall/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 static-verified because the record says so, and the link lands on this page.
[](https://www.iac-bazaar.com/catalog/linode-firewall?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, static-verified on IaC Bazaar: [Linode Cloud Firewall Baseline](https://www.iac-bazaar.com/catalog/linode-firewall?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "firewall" {
source = "www.iac-bazaar.com/iac-bazaar/linode-firewall/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-firewall
Opinionated stateful Linode Cloud Firewall: deny-by-default inbound, curated
named allow-rule presets, and multi-device attachment. Works with Terraform
and OpenTofu (>= 1.6), Linode provider >= 3.14, < 4.0.
Secure defaults:
inbound_policy = "DROP"— nothing is reachable unless you allow it- 23 curated presets (
ssh,https,postgres,redis,k8s-api,wireguard,ping, ...) with the right protocol/ports baked in - Every rule — preset or custom — must declare explicit source CIDRs;
there is no silent
0.0.0.0/0default - Attachment via
linode_firewall_device, so instances and NodeBalancers can be added or removed without touching rule definitions
Requirements
- Terraform or OpenTofu
>= 1.6 linode/linodeprovider>= 3.14, < 4.0- Cloud Firewall is a free Linode service.
Note: with the default inbound_policy = "DROP" and no presets, an attached
instance accepts no inbound traffic at all — add at least an ssh preset
scoped to your management CIDR before attaching.
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
do-firewall
A firewall with no droplets and no tags applies to nothing while the console shows it active; SSH from 0.0.0.0/0 is the first rule the console offers; and with no outbound rule nothing leaves, DNS included. Droplets or tags expected, port 22 from everywhere refused unless accepted, and an outbound default that allows what a server needs.
vultr-firewall
A firewall group filters inbound on the public interface only: outbound is always open and the VPC interface is never filtered. It is attached by the instance, so the group cannot see whether any uses it, and SSH from a /0 is the first rule offered. Named sources or Cloudflare's edge, SSH from anywhere refused unless accepted, and outputs that say attachment is not proven and outbound is open.
gcp-firewall-policy
A global network firewall policy exists independently of any network; an association puts it in the path, and a policy with a hundred rules and none governs nobody while rendering as fully configured. enable_logging defaults to false on every rule, so a deny that fires leaves no evidence. Refuses a policy with no network, logs every rule unless told not to, and counts the disabled ones.
civo-firewall
create_default_rules defaults to true and the rules it writes allow all inbound traffic on every port from every address, which turns a firewall into a name on a list; SSH from 0.0.0.0/0 is the first rule offered; and with the defaults off a firewall with no egress rule blocks all outbound. Defaults off, SSH from anywhere refused unless accepted, egress opened unless outbound rules narrow it.
hetzner-firewall
A firewall applied to no server protects nothing; SSH from everywhere is the default suggestion; and once one outbound rule exists Hetzner drops every other outbound packet, DNS included. Servers or a label selector expected, port 22 from everywhere refused unless accepted, a DNS and HTTPS baseline added once outbound is restricted, and an output that says the private network is not filtered.
alicloud-security-group
inner_access_policy defaults to Accept, so every instance in a group talks to every other on every port and one compromised web node is a route to the database beside it; SSH from 0.0.0.0/0 is the first rule offered; and the group is attached by the instance, which it cannot see. Members isolated unless told otherwise, SSH from anywhere refused unless accepted, egress open until rules narrow it.