Akamai App & API Protector (WAF)
Security configuration with policy, WAF mode, match targets, rate controls, and IP/geo blocking, activated to staging or production.
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: findings disclosed (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 akamai-appsec-waf-1.0.0.sigstore.json \
https://www.iac-bazaar.com/api/artifacts/akamai-appsec-waf/signature
# 3. Verify the tarball you downloaded
cosign verify-blob \
--key cosign.pub \
--bundle akamai-appsec-waf-1.0.0.sigstore.json \
akamai-appsec-waf-1.0.0.tar.gz
# → Verified OK
# 4. (optional) confirm the checksum too
echo "0b6a2ec5df5e409eae72cf4d122ca28bd314dc72ff4d50d4b279bda907a67546 akamai-appsec-waf-1.0.0.tar.gz" | sha256sum -cUse it from the registry
terraform · opentofumodule "appsec_waf" {
source = "www.iac-bazaar.com/iac-bazaar/akamai-appsec-waf/akamai"
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/akamai-appsec-waf?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, plan-validated on IaC Bazaar: [Akamai App & API Protector (WAF)](https://www.iac-bazaar.com/catalog/akamai-appsec-waf?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "appsec_waf" {
source = "www.iac-bazaar.com/iac-bazaar/akamai-appsec-waf/akamai"
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
akamai-appsec-waf
Akamai App & API Protector (WAF) baseline in one module: security
configuration, policy with Akamai's recommended defaults, adaptive WAF mode,
website match target, rate controls, optional IP/geo/ASN firewall, and
staging/production activation. Works with Terraform and OpenTofu
(>= 1.6), Akamai provider >= 10.0, < 11.0.
Secure defaults:
- Security policy created with
default_settings = true(Akamai recommended protections) - WAF protection enabled, rules in
ASE_AUTO(adaptive) mode — Akamai keeps rule actions current - Match target covers all listed hostnames on
/* - A conservative alert-only rate-control spike detector ships enabled, so you
observe before you
deny
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
akamai-network-lists
Versioned IP and geo block/allow lists with activation, ready to feed WAF policies and property rules.
huawei-waf
A dedicated WAF of two anti-affinity instances in your subnet (one by name), pay-per-use, with a policy in block mode (log mode by name) that turns on basic web protection, CC attack protection, precise protection, web shell detection, anti-crawler and data masking, and the protected domain with your certificate, TLS 1.2, cipher suite 2 and PCI DSS checks, forwarding to origins over HTTPS.
azure-waf-policy
Detection mode evaluates every rule, logs every match and forwards every request - the dashboard fills with blocked-looking entries while the backend receives them all. Prevention by default, Detection only by name. A policy attached to no listener protects nothing, so the attached listeners are an output; every exclusion is a hole and has to carry a reason.
ibm-waf
The CIS managed and OWASP core rulesets deployed on an IBM Cloud Internet Services domain, with the OWASP threshold, action and paranoia level set. The resource owns the whole managed phase, so console rules are overwritten, and destroying it leaves the WAF running - the module says so and makes turning it off an explicit step. The deprecated legacy WAF resources are not used.
tencent-waf
A domain on a Tencent Cloud SaaS WAF, rules set to block, with block and allow lists. It reads back the CNAME, the mode the WAF reports and the addresses the WAF forwards from, so the origin can refuse everything else. An allowlist here lets addresses through; it does not make a site private. The client IP is taken from the connection unless you say a proxy sits in front.
oci-waf
CHECK is the action that evaluates the rule, logs the match and lets the request through - the console shows the protection rules and every matched attack reached the backend. BLOCK by default, DETECT only by name. The policy and the firewall binding it to a load balancer are separate resources; both are created, and a policy alone has to be asked for.