A Policy Store where a Broken Rule Cannot Hide
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.
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-13 · how we verify
Use it from the registry
terraform · opentofumodule "verified_permissions" {
source = "www.iac-bazaar.com/iac-bazaar/aws-verified-permissions/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-verified-permissions
A Verified Permissions policy store whose policies are checked against a schema,
so a rule that can never match cannot be written. Works with Terraform and
OpenTofu (>= 1.6), AWS provider >= 6.0, < 7.0.
validation_settings.mode defaults to OFF. With it off, a Cedar policy
naming an action or entity type your schema does not define is accepted without
complaint - and then never matches anything, ever.
That is worse than it sounds, because of which direction it fails in. Cedar
is default-deny, so a broken permit fails closed: somebody does not get
access they should have had, they complain, you fix it. A broken forbid fails
open. forbid is the rule that overrides every permit - "contractors may
never read salary data" - and a typo in its action name turns it into a policy
that forbids nothing, silently, while sitting in the console looking exactly like
a policy that works. STRICT here, which makes the schema non-optional too, and
forbid_policies is an output because those are the ones worth checking.
deletion_protection defaults to DISABLED, and deleting a policy store
deletes every policy in it with no undo.
A precondition refuses STRICT with no schema, since STRICT validates each
policy against the schema and without one every policy is rejected; another
refuses OFF unless accept_unvalidated_policies states it.
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.