// the take
A grab-bag of IAM submodules from the terraform-aws-modules org covering accounts, groups, policies, roles, users, and OIDC/SAML providers, including IRSA wiring for EKS service accounts. Useful for any team provisioning AWS IAM via Terraform/OpenTofu who wants off-the-shelf trust policies instead of hand-writing JSON policy documents every time.
Covers the full IAM surface (account password policy, groups, roles, users, OIDC/SAML providers, read-only policies) as independently composable submodules rather than one monolithic resource. The IRSA submodule ships pre-built trust-policy and permission sets for common EKS addons like VPC CNI, so you're not hand-rolling OIDC subject conditions. Actively maintained — pushed October 2026, semantic-release versioning, CHANGELOG, and CI gating via pre-commit hooks. Wrapper modules support for_each, which matters if you're provisioning the same role shape across many accounts.
The README itself admits Terraform can't use dynamic values in lifecycle blocks, so IAM role tags get silently reverted if anything outside Terraform touches them — the only fixes are `default_tags` or forking the module to add `ignore_changes`; this isn't solved, just documented. That same section then steers you toward the maintainer's own paid product (compliance.tf) as 'the' workaround, which is a real vendor-lock consideration before you adopt it. The IRSA submodule's own docs tell you to use EKS Pod Identity instead for new clusters, meaning a chunk of what this module advertises is already being deprecated by its author. With this many submodules spanning accounts, roles, users, and providers, policy ARN and OIDC thumbprint drift across AWS updates is something you'll be chasing indefinitely rather than something the module can fully insulate you from.
We read the README, the directory tree and a key source file in November 2026. Nobody pays to be listed. How we judge →