Skip to main content

​
About AWS Organizations

AWS Organizations evidence includes accounts, OUs, roots, SCPs, and related policies. The role must live in the management account - member accounts cannot enumerate the full org graph via these APIs.

​
How It Works

Iru runs in its own AWS account. To read AWS Organizations structure and settings in your management account, you create an IAM role with sts:AssumeRole trust (wizard External ID) and read-only organizations: permissions. Paste the role’s ARN back into Iru. Attach AWSOrganizationsReadOnlyAccess, or narrow to organizations:Describe* / organizations:List* via inline JSON.
DetailValue
CategoryCloud governance
AuthenticationCross-account IAM role (management account)

​
Prerequisites

  • IAM admin rights in the management account (not a workload member account).
  • Connector principal + external ID.

​
Connect AWS Organizations 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 the management account. 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 Organizations

Find AWS Organizations (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 the management account.

​
Submit the role ARN in Iru

Finish the AWS tab first (through Create the IAM role in the management account) 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 Organizations card is Active.

​
Troubleshooting

Check pop-up blocker settings for the Iru site and try again.
Confirm role creation happened in the management account.
External ID mismatch.

​
Considerations

Org APIs evolve: wildcard **Describe* / List***…

Org APIs evolve - wildcard Describe* / List* pairs reduce churn when AWS ships new read operations.

Sources Management

Browse and manage every Compliance source.

Getting Started With Compliance

Frameworks, actions, and Artifacts.

Iru Overview

How Endpoint, Compliance, and Identity fit together.

Artifacts Management

Upload, review, and organize evidence from sources and actions.