AzureLive-testedattested

Application Gateway v2 + WAF

Regional L7 load balancer with WAF v2 policy, TLS termination from Key Vault, autoscaling and health probes.

terraformAzureazure

Compare Load Balancer across clouds →

Part of: Azure Production Landing Zone

azure-application-gatewayvizier v1.2.0

Verification

Live-tested

Really 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

Functional

  • Live-tested - applied, verified, destroyed

Last verified 2026-06-29 · how we verify

Verify this download

cosign · sha-256

Don'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 azure-application-gateway-1.0.0.sigstore.json \
  https://www.iac-bazaar.com/api/artifacts/azure-application-gateway/signature

# 3. Verify the tarball you downloaded
cosign verify-blob \
  --key cosign.pub \
  --bundle azure-application-gateway-1.0.0.sigstore.json \
  azure-application-gateway-1.0.0.tar.gz
# → Verified OK

# 4. (optional) confirm the checksum too
echo "4e23fe59e0c49b2c120fbf6e526351819eb4cfbf2e8102e4f49380ba255935ca  azure-application-gateway-1.0.0.tar.gz" | sha256sum -c

Use it from the registry

terraform · opentofu
module "application_gateway" {
  source  = "www.iac-bazaar.com/iac-bazaar/azure-application-gateway/azure"
  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 · attribution

Paste 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.

README.md, GitLab, Gitea
[![IaC Bazaar: live-tested](https://www.iac-bazaar.com/api/artifacts/azure-application-gateway/badge)](https://www.iac-bazaar.com/catalog/azure-application-gateway?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)

Terraform module 1.0.0, live-tested on IaC Bazaar: [Application Gateway v2 + WAF](https://www.iac-bazaar.com/catalog/azure-application-gateway?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)

```hcl
module "application_gateway" {
  source  = "www.iac-bazaar.com/iac-bazaar/azure-application-gateway/azure"
  version = "1.0.0"
}
```

Preview:IaC Bazaar: live-tested

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

azure-application-gateway

Regional L7 load balancer with WAF v2 policy, TLS termination from Key Vault, autoscaling and health probes. Works with Terraform and OpenTofu (>= 1.6), azurerm provider >= 4.0, < 5.0.

azurerm_application_gateway is a monolithic resource with a dozen nested block types that must cross-reference each other by name. This module flattens that into plain maps keyed by name, generates frontend ports from your listeners, and enforces the cross-block invariants (redirect XOR backend per rule, certificate required on HTTPS listeners) at plan time.

Secure defaults:

  • WAF_v2 SKU with OWASP 3.2 managed rules in Prevention mode
  • Predefined TLS policy AppGwSslPolicy20220101 (TLS 1.2+)
  • Key Vault TLS certificates via a dedicated user-assigned identity (no certificate blobs in state) — pass versionless secret IDs for auto-rotation
  • HTTP/2 enabled, autoscaling 1-3 capacity units, zone-deployable

Requirements

  • Terraform or OpenTofu >= 1.6
  • hashicorp/azurerm >= 4.0, < 5.0 (built against 4.76)
  • A dedicated subnet (nothing but Application Gateways in it)
  • Running cost is roughly $0.45/hr for WAF_v2 — destroy test stacks promptly

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

Live-tested

azure-front-door

Global entry point: Front Door profile, endpoints, origin groups, custom domains with managed TLS and WAF policy.

View module
Live-tested

azure-load-balancer

An Azure Standard L4 load balancer with a self-created static public IP frontend, a backend address pool, health probes and load-balancing rules - Standard SKU throughout.

View module
Live-tested

azure-traffic-manager

Global, DNS-based load balancing with a Traffic Manager profile and map-driven external endpoints - Performance, Priority, Weighted, Geographic, Subnet or MultiValue routing with an HTTPS health probe.

View module
Static validatedLive test pending

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.

View module
Static validatedLive test pending

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.

View module
Static validatedLive test pending

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.

View module