IAM Roles, Policies & OIDC Trust
Least-privilege IAM roles, managed policies, and GitHub/EKS OIDC federation in one composable module.
Compare Identity & Access across clouds →
Part of: AWS Production Landing Zone
Verification
Live-testedReally 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
- SHA-256 checksum
- Cosign signature
Functional
- Live-tested - applied, verified, destroyed
Last verified 2026-06-11 · 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 aws-iam-roles-1.0.0.sigstore.json \
https://www.iac-bazaar.com/api/artifacts/aws-iam-roles/signature
# 3. Verify the tarball you downloaded
cosign verify-blob \
--key cosign.pub \
--bundle aws-iam-roles-1.0.0.sigstore.json \
aws-iam-roles-1.0.0.tar.gz
# → Verified OK
# 4. (optional) confirm the checksum too
echo "51e73c4478b5f432f1599363f5a5272319bf21516d46d632136ccebe396f0851 aws-iam-roles-1.0.0.tar.gz" | sha256sum -cUse it from the registry
terraform · opentofumodule "iam_roles" {
source = "www.iac-bazaar.com/iac-bazaar/aws-iam-roles/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 live-tested because the record says so, and the link lands on this page.
[](https://www.iac-bazaar.com/catalog/aws-iam-roles?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, live-tested on IaC Bazaar: [IAM Roles, Policies & OIDC Trust](https://www.iac-bazaar.com/catalog/aws-iam-roles?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "iam_roles" {
source = "www.iac-bazaar.com/iac-bazaar/aws-iam-roles/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-iam-roles
Least-privilege IAM roles, managed policies, and GitHub/EKS OIDC federation in
one composable module. Works with Terraform and OpenTofu (>= 1.6), AWS
provider >= 6.0, < 7.0. Roles, customer-managed policies, OIDC identity
providers, and instance profiles are all driven from maps, so a single module
call provisions an account's whole role layout — and the policy-document
plumbing (trust statements, aud/sub conditions, attachment fan-out) is
already correct.
Secure defaults:
- Trust policies are composed per-role from explicit sources only
(
trusted_services,trusted_role_arnswith optionalexternal_id, GitHub OIDC subjects, custom OIDC issuers) — no wildcard principals - GitHub OIDC trust pins the
audclaim and usesrepo:-prefixedsubpatterns; built on v6-era standalone attachment resources (the removedinline_policy/managed_policy_arnsrole arguments are not used) max_session_durationdefaults to 1 hour;force_detach_policieson; permissions-boundary support per role
Requirements
- Terraform or OpenTofu
>= 1.6 hashicorp/aws>= 6.0, < 7.0
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
- Notes
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.