Shield Advanced that Blocks Rather than Counts
Protections, protection groups, response-team access and the automatic layer-7 response. That response can be enabled and do nothing: COUNT labels the request and lets it through, so this defaults to BLOCK and names the counting ones.
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
- Signature (pending)
Functional
- Live test pending (no cloud run yet)
Last verified 2026-09-12 · how we verify
Use it from the registry
terraform · opentofumodule "shield" {
source = "www.iac-bazaar.com/iac-bazaar/aws-shield/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.
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-shield
AWS Shield Advanced protections, protection groups, response-team access and the
automatic layer-7 response. Works with Terraform and OpenTofu (>= 1.6),
AWS provider >= 6.0, < 7.0.
This module does not subscribe you. Shield Advanced is a 3,000 USD/month commitment for the organization on a one-year term, enabled once per payer account through the console or the Organizations API. Every resource here fails on an unsubscribed account - correct behaviour, opaque error, so it is said first.
The automatic response can be on and do nothing. Its action is BLOCK or
COUNT, and COUNT counts: it labels the request and lets it through. That is
the right setting for the first week while you find out what it would break, and
it is not protection - so the module defaults to BLOCK and the
counting_only_resources output names the ones that are only counting.
It also requires a WAF web ACL already associated with the resource. Shield writes its rules into that ACL; without one there is nowhere to write.
Two more things worth knowing:
- Without
drt_access_role_arnthe Shield Response Team can advise during an attack and cannot act. Granting it during an incident is granting it too late, andresponse_team_can_actis an output so the answer is visible before one - A protection group is judged as one thing. An attack spread across twenty resources can stay under every individual threshold while being obvious in aggregate, which is the entire reason groups exist
Emergency contact email addresses are validated, because that list is what somebody reads at 3am.
Verification
Static validation runs tofu fmt, init, validate, tflint and checkov.
This module has not yet had a live test, so it is published as statically
validated with its live test pending and does not carry the live-tested mark.
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
Related modules
aws-signer
Signing profiles for Lambda packages and container images, plus the code signing configuration that enforces them. Defaults to Enforce rather than the API default Warn, which logs an untrusted artifact and deploys it anyway.
aws-cognito
A secure-by-default Cognito user pool and app client with optional hosted-UI domain - strong password policy, TOTP MFA, account-enumeration protection, SRP-only flows, and refresh-token revocation.
aws-detective
Builds an investigable graph from CloudTrail, VPC flow logs and GuardDuty findings, with member accounts and organization delegation. It detects nothing itself - it makes an existing finding into a timeline.
aws-firewall-manager
WAF, security group and Network Firewall policy applied across an organization. Remediation is off by default so the first apply is a report rather than an edit to resources in every member account.
aws-guardduty
Threat detection with each protection plan - S3, EKS, RDS, Lambda, malware, runtime - a separate decision with its billing dimension stated, plus organization delegation and findings filtered by severity into EventBridge.
aws-iam-access-analyzer
Finds what a principal outside your zone of trust could actually reach, which is the question policy reviews get wrong by reading JSON. External analysis is free; unused-access analysis is a separate, billed analyzer.