Skip to main content

​
About Amazon Inspector

Inspector v2 uses the inspector2: action namespace (not legacy inspector:). Enable Inspector in each Region where you expect findings. AmazonInspector2ReadOnlyAccess is the fastest attach; least-privilege mirrors List*, Get*, Describe*, BatchGet*, and Search*.

​
How It Works

Iru runs in its own AWS account. To read Amazon Inspector v2 data in your account, you create an IAM role with a trust policy (Iru’s principal and sts:AssumeRole with the wizard External ID) and a permissions policy that grants read-only inspector2: access. The inline body below is a typical least-privilege shape; you can attach AmazonInspector2ReadOnlyAccess instead if your team allows the managed policy. 
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "inspector2:List*",
        "inspector2:Get*",
        "inspector2:Describe*",
        "inspector2:BatchGet*",
        "inspector2:Search*"
      ],
      "Resource": "*"
    }
  ]
}
DetailValue
CategoryVulnerability management
AuthenticationCross-account IAM role

​
Prerequisites

  • Inspector v2 activated per Region under review.
  • IAM rights to create roles.

​
Connect Amazon Inspector 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 Amazon Inspector

Find Amazon Inspector (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 Amazon Inspector card is Active.

​
Troubleshooting

Check pop-up blocker settings for the Iru site and try again.
Activate Inspector v2 in that Region (Account management).
Switch to inspector2: APIs.
Deploy the role in the delegated administrator account when Org-wide administration applies.
External ID mismatch.

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.