Terraform IAM Policy Resource Generator

Terraform IAM Policy Resource Generator goes beyond wrapping a policy JSON document in a bare jsonencode(...) call: it generates a complete, named aws_iam_policy resource with editable name, path, and description arguments, and — when you turn on the role option — an aws_iam_role plus an aws_iam_role_policy_attachment wiring the new policy to that role. The role's trust document is generated from a chosen AWS service principal (EC2, Lambda, ECS tasks, and more), so the output is a small, deployable mini-module rather than a single orphaned policy resource.

The policy document itself is embedded with jsonencode(...), the standard, idiomatic pattern most real Terraform codebases use for a raw IAM policy, since it accepts a JSON-compatible literal directly and reproduces your policy exactly, only re-indented to fit the HCL block.

Every generated name is a clearly labeled placeholder. This is a starting point for review, not a finished module: rename resource identifiers, the policy path, and the role name to fit your project, and add any dynamic Terraform references (like another resource's ARN) by hand — this tool only converts the static JSON you paste.

• Full aws_iam_policy resource with editable name, path, and description.
• Optional aws_iam_role + aws_iam_role_policy_attachment pair, toggled with one checkbox.
• Service-principal trust policy for the role — EC2, Lambda, ECS tasks, Step Functions, Glue, or EKS.
• Uses the idiomatic jsonencode(...) pattern for both the policy and the trust document.
• Works on any valid JSON, with a structural warning if it does not look like a complete IAM policy.
• One-click copy of the generated HCL.
• 100% client-side — nothing is uploaded.

1. Paste your policy JSON, or click the sample.
2. Set the resource name, policy name, path, and description.
3. Optionally check "Also generate a role + attachment" and pick a service principal and role name.
4. Click Generate Terraform.
5. Copy the HCL and rename the placeholders to fit your project before applying.

Example 1 — policy only. A simple S3 read-only statement produces one aws_iam_policy.example resource.

Example 2 — policy + role. With the role option on and "lambda" selected, the output additionally includes aws_iam_role.example (trusted by lambda.amazonaws.com) and an aws_iam_role_policy_attachment linking the two — a deployable mini-module for a Lambda execution role.

• A deployable module, not a lone resource — policy, role, and attachment together in one step.
• Real trust-policy generation for common AWS service principals.
• Uses the pattern real Terraform codebases actually use for embedding policy JSON.
• Clearly labeled placeholders so you know exactly what to rename.
• Private — generation runs entirely in your browser.