Skip to main content

​
About AWS IAM Identity Center (SSO)

This connector targets sso: APIs - permission sets, account assignments, instances, and SSO applications. Users and groups come from Identity Store (identitystore:). AWSSSOReadOnly exists but often needs supplementation; the inline policy below tracks Describe*, Get*, List*, and Search* on sso:. Deploy the role in the management or delegated administrator account.

​
How It Works

Iru runs in its own AWS account. To read IAM Identity Center SSO configuration (permission sets, assignments, instances, applications), you create an IAM role in your management or delegated administrator account with a trust policy (sts:AssumeRole + wizard External ID) and read-only sso: permissions. AWSSSOReadOnly exists but does not always cover every action Iru needs, so the inline policy on the AWS tab is the reliable default. Paste the role’s ARN back into Iru.
DetailValue
CategoryIdentity / access governance
AuthenticationCross-account IAM role

​
Prerequisites

  • IAM Identity Center enabled for the organization.
  • Permissions to create roles in management or delegated admin.

​
Connect IAM Identity Center (SSO) to Iru

Start here: open the source wizard and copy the trust policy (and note the external ID). When you are ready to create the role in AWS, switch to the AWS tab and follow Create the IAM role in AWS. After you have the Role ARN, return to the Iru Compliance tab and complete Submit the role ARN in Iru below.

​
Get the trust policy from Iru

1

Open Sources

In Iru Compliance, on the left navigation bar, expand Compliance and select Sources.
Left navigation: Compliance expanded, Sources selected
2

Turn on AWS IAM Identity Center (SSO)

Find AWS IAM Identity Center (SSO) (use Category or Search by name or description). On that card, turn on the toggle. Leave the Iru is requesting access to external services wizard tab open.
3

Copy the trust policy JSON

The wizard shows the trust policy JSON your IAM role must use (Principal and sts:ExternalId). Below is an example of the structure; copy the live JSON from your wizard so the account, principal ARN, and external ID match exactly.
copy=false
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Principal": {
        "AWS": "arn:aws:iam::753695775620:role/IruConnect"
      },
      "Condition": {
        "StringEquals": {
          "sts:ExternalId": "YOUR_EXTERNAL_ID"
        }
      },
      "Action": "sts:AssumeRole"
    }
  ]
}
4

Switch to AWS to create the role

Keep the Iru wizard tab open for reference, then switch to the AWS tab and follow Create the IAM role in AWS.

​
Submit the role ARN in Iru

Finish the AWS tab first (through Create the IAM role in AWS) so you have the Role ARN from the new role.
1

Paste the IAM Role ARN

Return to the Iru wizard tab. Paste the Role ARN where the connector prompts for it.
2

Finish the connection

Click Submit Role. When the connection succeeds, the wizard shows Connection Configured.
3

Confirm the source is Active

Close the Iru is requesting access to external services browser tab, then return to Compliance → Sources and confirm the AWS IAM Identity Center (SSO) card is Active.

​
Troubleshooting

Check pop-up blocker settings for the Iru site and try again.
Member-account roles cannot see org SSO config - use management/delegated admin.
Confirm sso:List* / sso:Describe* coverage (wildcard above).
SSO management uses sso:, not identitycenter: for these reads.
External ID mismatch.

AWS IAM Identity Center (Identity Store)

Connect and manage the related source in Compliance.

Sources Management

Browse and manage every Compliance source.

Getting Started With Compliance

Frameworks, actions, and Artifacts.