Skip to main content

​
About AWS IAM Identity Center (Identity Store)

This source reads users, groups, and memberships through the identitystore: API - the directory layer behind IAM Identity Center. Permission sets, account assignments, and SSO applications live under sso: and are covered by IAM Identity Center (SSO). Create the role in your organization management or delegated administrator account where Identity Center is enabled. AWS does not ship a minimal managed policy only for Identity Store. Use the inline JSON below.

​
How It Works

Iru runs in its own AWS account. To read Identity Store users, groups, and memberships, you create an IAM role with a trust policy (sts:AssumeRole + wizard External ID) and read-only identitystore: permissions. AWS does not publish a minimal managed policy only for Identity Store; the inline JSON on the AWS tab matches what Iru calls. Paste the role’s ARN back into Iru.
DetailValue
CategoryIdentity
AuthenticationCross-account IAM role

​
Prerequisites

  • IAM Identity Center enabled; role in management or delegated admin account.
  • d-xxxxxxxxxx Identity Store ID is discoverable in console Settings once Iru connects.

​
Connect Identity Store 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 (Identity Store)

Find AWS IAM Identity Center (Identity Store) (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 Identity Store card is Active.

​
Troubleshooting

Check pop-up blocker settings for the Iru site and try again.
Wrong account - use management or delegated admin where Identity Center runs.
Use identitystore:, not sso:.
External ID mismatch.

​
Considerations

Identity Center home Region is fixed per…

Identity Center home Region is fixed per organization; evidence reflects that deployment model.

AWS IAM Identity Center (SSO)

Connect and manage the related source in Compliance.

Sources Management

Browse and manage every Compliance source.

Getting Started With Compliance

Frameworks, actions, and Artifacts.