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.
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/aws-shield?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, static-verified on IaC Bazaar: [Shield Advanced that Blocks Rather than Counts](https://www.iac-bazaar.com/catalog/aws-shield?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "shield" {
source = "www.iac-bazaar.com/iac-bazaar/aws-shield/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-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-verified-permissions
validation_settings.mode defaults to OFF, so a Cedar policy naming an action the schema does not define is accepted and then never matches. A broken permit fails closed and somebody complains; a broken forbid fails OPEN and nobody does. STRICT here, with the schema that makes it possible.
aws-rolesanywhere
Any certificate chaining to the trust anchor can exchange itself for AWS credentials, so the CA is the perimeter - and it is usually run by people who were never told. The profile carries the scope, sessions are narrowed below the role, the caller cannot name itself in CloudTrail, and CA expiry warns before every workload loses credentials at once.
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-conformance-packs
AWS Config conformance packs for one account or a whole organisation, with a ten-rule baseline of AWS managed rules taken from AWS's CIS sample pack. AWS Audit Manager no longer takes new customers and points them here. The module says a pack evaluates nothing without a configuration recorder and that Terraform cannot detect a pack edited in the console.
aws-lake-formation
AWS Lake Formation with its own permissions switched on for new databases and tables: admins, registered S3 locations and explicit grants. AWS ships it in IAM-only mode, and its settings resource clears any admin it is not given, so admins are required and the settings are protected from destroy. Existing databases keep IAM-only access until revoked outside Terraform, and it says so.