Network Load Balancer (L4)
A Layer-4 Network Load Balancer with map-driven TCP/UDP/TLS listeners and target groups, modern TLS 1.3 termination from an ACM cert, and self-contained default-VPC networking.
Verification
Live-testedReally deployed to a cloud sandbox, verified against its outputs and assertions, then destroyed - with the teardown confirmed.
Conformance
- Static validation (fmt · validate · tflint)
- Security scan clean (Checkov)
- Plan test superseded by live test
Provenance
- SHA-256 checksum
- Cosign signature
Functional
- Live-tested - applied, verified, destroyed
Last verified 2026-06-30 · 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 aws-nlb-1.0.0.sigstore.json \
https://www.iac-bazaar.com/api/artifacts/aws-nlb/signature
# 3. Verify the tarball you downloaded
cosign verify-blob \
--key cosign.pub \
--bundle aws-nlb-1.0.0.sigstore.json \
aws-nlb-1.0.0.tar.gz
# → Verified OK
# 4. (optional) confirm the checksum too
echo "5689403cf092af4585d9bc0f2aa5a7c46d69c450f6e86e1a61e3434163e42d50 aws-nlb-1.0.0.tar.gz" | sha256sum -cUse it from the registry
terraform · opentofumodule "nlb" {
source = "www.iac-bazaar.com/iac-bazaar/aws-nlb/aws"
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 live-tested because the record says so, and the link lands on this page.
[](https://www.iac-bazaar.com/catalog/aws-nlb?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, live-tested on IaC Bazaar: [Network Load Balancer (L4)](https://www.iac-bazaar.com/catalog/aws-nlb?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "nlb" {
source = "www.iac-bazaar.com/iac-bazaar/aws-nlb/aws"
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
aws-nlb — Network Load Balancer
Layer-4 Network Load Balancer with TCP/UDP/TLS listeners and target groups —
drop-in for ultra-low-latency, high-throughput, or static-IP workloads
(databases, game servers, MQTT/gRPC backends, anything that needs the client's
real source IP). Define target groups and listeners as simple maps; the module
wires each listener's default forward action to its target group. Hand it an ACM
certificate on a TLS listener and the NLB terminates TLS with a modern TLS 1.3
(1.2-floor) policy.
Self-contained networking: omit subnet_ids and the module discovers every
subnet in the account's default VPC (and derives the VPC for the target
groups), so a throwaway NLB applies with nothing but a name. Pin explicit
subnets for real deployments.
Works with Terraform and OpenTofu (>= 1.6), AWS provider >= 6.0, < 7.0.
Security notes
- Encryption / TLS:
TLSlisteners useELBSecurityPolicy-TLS13-1-2-2021-06(TLS 1.3 with a TLS 1.2 floor) by default; override per-listener withssl_policyor globally withdefault_ssl_policy. TCP listeners pass bytes through unterminated — terminate TLS at the target for end-to-end encryption. - Deletion protection defaults on;
terraform destroyrequires flippingenable_deletion_protection = falseand applying first. - Security groups: NLB SGs can only be attached at creation and never
removed afterwards. With
security_group_ids = []the NLB has no SG and the targets' own security groups govern access (the classic NLB model). - Client IP: NLBs preserve the client source IP for
instance/iptargets by default; setpreserve_client_ip = falseper target group to disable, orproxy_protocol_v2 = trueto forward connection metadata. - Cross-zone is off by default (the AWS default for NLB) to avoid inter-AZ data-transfer charges; enable it for even distribution across AZs.
Requirements
- Terraform or OpenTofu
>= 1.6 hashicorp/aws>= 6.0, < 7.0
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
- Cost
Related modules
aws-gateway-load-balancer
A Gateway Load Balancer for firewall or IDS appliances, its endpoint service and endpoints. AWS turns cross-zone off, keeps flows on failed appliances and leaves deletion protection off by default; this module turns cross-zone and protection on and makes flow failover an explicit choice. It also says plainly that nothing is inspected until route tables point at the endpoints.
aws-alb
ALB with HTTPS listeners, target groups, listener rules, and access logging - drop-in for ECS/EC2/Lambda targets.
aws-global-accelerator
Two anycast addresses in front of load balancers or instances, with per-region endpoint groups, health checks and traffic dials for draining a region without deleting it.
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.