Guided IAM editors
IAM policies, roles, and identity providers are configured with JSON documents under the hood. To make them approachable for non-technical users, the portal's create/edit screens for Policies, Roles, and Identity providers each offer two modes:
- Guided — a structured form. No JSON, no syntax to get wrong.
- Advanced (JSON) — the raw document editor, for power users and anything the form doesn't cover.
A toggle at the top of the editor switches between them. New items open in Guided by default.
Policies
The guided policy editor is a list of statements. Each statement has:
- Effect — Allow or Deny.
- Actions — what can be done (e.g.
huudis:Read*), one or more. - Resources — what it applies to (an ID, ARN, or
*for everything). - Condition (advanced, optional) — a JSON sub-editor for fine-grained rules.
"Add statement" builds up the policy; switching to Advanced shows the exact
{ Version, Statement[] } document it produces.
Roles
The guided role editor captures who can assume the role (principal rows — user, role, service account, account, or federated identity) plus an optional condition, and a Max session duration. It builds the role's trust policy. (Permissions are granted separately by attaching policies.)
Identity providers
Pick a type (SAML or OIDC) and the form reveals the right fields — SAML: entity ID / SSO URL / X.509 certificate; OIDC: issuer / client ID / client secret / scopes. It builds the provider's metadata document.
Switching modes safely
Guided and Advanced stay in sync: edits in the form update the JSON, and the JSON populates the form when you switch back. If you're editing an existing item whose JSON uses options the form doesn't model (custom conditions, unusual statement shapes, and so on), the editor opens in Advanced and shows a notice — your configuration is never silently changed or dropped. Edit those in JSON, or use Guided for straightforward cases.