Skip to main content

​
About AWS Config

AWS Config evidence includes resource inventory, compliance evaluations, and configuration timeline data - assuming Config recorders are actually enabled in each Region you care about. Iru assumes a cross-account IAM role with read-only Config APIs.

​
How It Works

Iru runs in its own AWS account. To read AWS Config recorder and rule metadata in your account, you create an IAM role with sts:AssumeRole trust (wizard External ID) and read-only config: / related permissions. Paste the role’s ARN back into Iru. Attach AWSConfigUserAccess for parity with AWS documentation for interactive Config usage, or paste the config: + tag: inline JSON below for tighter scope.
DetailValue
CategoryGovernance
AuthenticationCross-account IAM role

​
Prerequisites

  • IAM rights to create roles.
  • AWS Config enabled per Region - otherwise APIs return empty sets legitimately.

​
Connect AWS Config 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 Config

Find AWS Config (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 Config card is Active.

​
Troubleshooting

Check pop-up blocker settings for the Iru site and try again.
Enable Config recorders + delivery channels there first.
External ID mismatch.

​
Considerations

Config is Regional: repeat enablement steps where…

Config is Regional. Repeat enablement steps where audits apply.

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.