Hetzner Load-Balanced Web Tier
Managed LB with health checks, cert, and label-selected server targets.
Verification
Static-verifiedPassed: validated and lint-clean (provider-schema-validated for AWS/Azure/GCP; Terraform-language lint elsewhere).
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 hetzner-lb-web-tier-1.0.0.sigstore.json \
https://www.iac-bazaar.com/api/artifacts/hetzner-lb-web-tier/signature
# 3. Verify the tarball you downloaded
cosign verify-blob \
--key cosign.pub \
--bundle hetzner-lb-web-tier-1.0.0.sigstore.json \
hetzner-lb-web-tier-1.0.0.tar.gz
# → Verified OK
# 4. (optional) confirm the checksum too
echo "df727e4b8cb24f142624be4dfdc0fc91ac981a4e2fd937afcd6add64870d8cd0 hetzner-lb-web-tier-1.0.0.tar.gz" | sha256sum -cUse it from the registry
terraform · opentofumodule "lb_web_tier" {
source = "www.iac-bazaar.com/iac-bazaar/hetzner-lb-web-tier/hetzner"
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/hetzner-lb-web-tier?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, static-verified on IaC Bazaar: [Hetzner Load-Balanced Web Tier](https://www.iac-bazaar.com/catalog/hetzner-lb-web-tier?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "lb_web_tier" {
source = "www.iac-bazaar.com/iac-bazaar/hetzner-lb-web-tier/hetzner"
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
hetzner-lb-web-tier
A Hetzner Cloud load-balanced web tier: a managed load balancer with health-checked services, a Let's Encrypt managed certificate, and label-selected server targets so backends auto-enroll as they scale.
Status: static-validated, live-test pending. Validated with
tofu validate+tflint+checkovagainst thehetznercloud/hcloudprovider. Not yet applied against a live Hetzner project, so it ships under live-test quarantine.
Design & secure defaults
- HTTPS-first. The default service is HTTPS:443 with an automatic
HTTP→HTTPS redirect; a plan-time precondition refuses an
httpsservice that has no certificate (certificate_domain_names,existing_certificate_ids, or per-servicecertificate_ids). - Delete protection on by default — set
delete_protection = falsefor ephemeral environments sodestroyworks without a manual toggle. - Label-selected targets.
target_label_selector = "role=web"enrolls every matching server automatically;target_server_idsadds explicit ones. - Private backends, optionally. Attach a network (
network_id) and setuse_private_ip = trueto send traffic to targets over the private network;enable_public_interface = falsemakes the LB internal-only. - Exactly one of
location/network_zoneis enforced by precondition.
Provider
hetznercloud/hcloud >= 1.0, < 2.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
tencent-clb
A listener's health check is a switch that, off, sends traffic to every target forever; a port-80 listener forwards unless a redirection resource points it at 443; and delete_protect defaults to false. HTTP health checks on a path through listener rules, a 301 from 80 to 443 whenever a certificate is given, deletion protection on, access logs when a CLS topic is given.
huawei-elb
The default TLS policy accepts TLS 1.0; a pool without a monitor resource is never unhealthy and sends traffic to every member forever; an HTTPS listener does nothing about port 80 until an L7 policy redirects it; and deletion protection is off. tls-1-2-strict, an HTTP monitor on a path, a redirect on 80 whenever a certificate is given, two zones unless one is accepted, deletion protection on.
vultr-load-balancer
The default health check is TCP on the backend port, which a process that stopped serving still passes; ssl_redirect defaults to false, so the site stays in clear on 80; and a balancer with no instances is a public address that fails. HTTP checks on a path, redirect on whenever HTTPS exists, backends required, and a Let's Encrypt certificate from auto_ssl_domain rather than a pasted key in state.
do-load-balancer
The default health check is a TCP handshake, which a process that stopped serving still passes; redirect_http_to_https defaults to false, so the site stays in clear on 80; and a balancer with no tag and no droplets is a public address that 503s. HTTP checks on a path, redirect on whenever HTTPS exists, STRONG ciphers, backends required, and a Let's Encrypt certificate made from your domains.
upcloud-load-balancer
The backend health check defaults to TCP, which a process that stopped serving still passes; TLS is a certificate bundle nobody creates; a port-80 frontend forwards unless a rule redirects it; and a public network puts the frontend on the internet. HTTP checks on a path (TCP by name), a Let's Encrypt bundle for the hostnames you list, a 301 from 80 whenever it exists, and public by name.
scaleway-load-balancer
A Scaleway Load Balancer on a flexible IP with a Let's Encrypt certificate it issues itself (so the DNS must point at it first), TLS at the modern compatibility level (older clients by name), HTTP/3, the port 80 frontend answering only a 301 to HTTPS, and backends named by their Private Network address and probed over HTTP on a path you chose.