Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.iru.com/llms.txt

Use this file to discover all available pages before exploring further.

​
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

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

​
Copy 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 wizard tab open.
3

Copy the trust policy JSON

{
  "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"
    }
  ]
}

​
Create the IAM role in AWS

1

Start Create role

Open IAM → Roles → Create role.
2

Configure trusted entity

Choose AWS account → Another AWS account. Enter 753695775620 (or the ID Iru shows). Enable Require external ID and paste the external ID from Iru.
3

Attach Config permissions

Attach AWSConfigUserAccess, or attach this inline policy:
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "config:Describe*",
        "config:Get*",
        "config:List*",
        "config:Select*",
        "tag:GetResources",
        "tag:GetTagKeys"
      ],
      "Resource": "*"
    }
  ]
}
4

Name the role and copy the ARN

Name the role, create it, and copy the Role ARN.
5

Verify the trust relationship

Confirm Trust relationships matches the wizard JSON.

​
Submit the role ARN in Iru

1

Paste the IAM Role ARN

Paste the Role ARN into the connector where the wizard prompts for it.
2

Confirm the source is Active

Submit until AWS Config shows 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.

​
See also