Serverless Framework IAM Role Generator

Serverless Framework IAM Role Generator converts a pasted IAM policy JSON document into the IAM role block for your serverless.yml, in both syntaxes real projects actually use today: the modern provider.iam.role.statements syntax introduced in Serverless Framework v3, and the legacy provider.iamRoleStatements syntax used by v1/v2 projects and still common in the wild. A tab switches between the two without re-entering anything, since both are generated from the same statements.

Each Statement in your policy becomes one YAML list item with Effect, Action (always rendered as a YAML list, even for a single action), and Resource (also always a YAML list) — matching how these blocks are conventionally written by hand. A Condition block, when present, is embedded inline as JSON, which YAML accepts directly and preserves exactly.

This is a starting-point block to merge into your existing serverless.yml, not a full file: check that indentation lines up with the rest of your file and that it merges cleanly with any provider.iam/iamRoleStatements content you already have.

• Modern syntax — provider.iam.role.statements (Serverless Framework v3+).
• Legacy syntax — provider.iamRoleStatements (pre-v3), one tab away.
• Action/Resource always rendered as YAML lists, matching hand-written convention.
• Condition blocks preserved via inline JSON.
• Works on any valid JSON, with a structural warning if it does not look like a complete IAM policy.
• One-click copy of either syntax.
• 100% client-side — nothing is uploaded.

1. Paste your policy JSON, or click the sample.
2. Click Generate.
3. Switch between the "Modern (v3+)" and "Legacy" tabs to see the syntax that matches your Serverless Framework version.
4. Copy the YAML block and merge it into your serverless.yml.

Example. An S3 read-only Allow statement produces, in modern syntax: provider.iam.role.statements: - Effect: Allow Action: [s3:GetObject] Resource: [arn:aws:s3:::my-bucket/*]; the legacy tab shows the identical statement under provider.iamRoleStatements instead.

• Covers both syntaxes real projects use — no guessing which one your Serverless version expects.
• Matches hand-written YAML conventions — lists, not inline arrays.
• Preserves Condition blocks exactly.
• Private — generation runs entirely in your browser.