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 Secrets Manager

This connector enumerates secret metadata, rotation configuration, resource policies, and tags - but never calls GetSecretValue. Avoid SecretsManagerReadWrite because it grants GetSecretValue. Use the inline JSON below unless your cloud security group publishes an audited equivalent.

​
How it works

Standard sts:AssumeRole trust plus explicit secretsmanager actions that skip value retrieval.
DetailValue
CategorySecrets management
AuthenticationCross-account IAM role

​
Prerequisites

  • IAM rights to create roles and inline policies.

​
Connect AWS Secrets Manager 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 Secrets Manager

Find AWS Secrets Manager (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 the metadata-only inline policy

Add this inline policy (do not attach SecretsManagerReadWrite):
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "secretsmanager:DescribeSecret",
        "secretsmanager:ListSecrets",
        "secretsmanager:ListSecretVersionIds",
        "secretsmanager:GetResourcePolicy"
      ],
      "Resource": "*"
    }
  ]
}
GetSecretValue is intentionally omitted. Iru cannot fetch cleartext secrets with this policy.
4

Name the role and copy the ARN

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

​
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 Secrets Manager turns Active.

​
Troubleshooting

Check pop-up blocker settings for the Iru site and try again.
Secret resource policies may deny cross-account principals - adjust policies cautiously with security stakeholders.
External ID mismatch.

​
Considerations

Secrets are Regional: inventory spans enabled…

Secrets are Regional; inventory spans enabled Regions.

​
See also