Skip to main content

​
About Amazon Relational Database Service (RDS)

The Amazon RDS connector collects instance and Aurora cluster settings, parameter groups, subnet groups, snapshots, backups, and encryption posture without connecting to databases or running queries. Authentication is a cross-account IAM role with sts:AssumeRole and an external ID.

​
How It Works

Iru runs in its own AWS account. To read RDS configuration in your account, you create an IAM role with sts:AssumeRole trust (wizard External ID) and read-only rds:Describe* (and related) permissions. Paste the role’s ARN back into Iru. Attach AmazonRDSReadOnlyAccess for simplicity, or paste the inline JSON below for a narrower rds:Describe* footprint.
DetailValue
CategoryDatabases
AuthenticationCross-account IAM role
References: AmazonRDSReadOnlyAccess, RDS IAM.

​
Prerequisites

  • IAM rights to create roles and policies.
  • Live principal + external ID from your connector tab.

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

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

​
Troubleshooting

Check pop-up blocker settings for the Iru site and try again.
Fix external ID / principal typos.
Ensure rds:DescribeDBClusters is allowed (Describe* covers it).
Confirm DescribeDBSnapshots / cluster snapshot APIs match your engine types.

​
Considerations

RDS APIs are Regional: inventory spans enabled…

RDS APIs are Regional; inventory spans enabled Regions.

Evidence is infrastructure metadata, not SQL result…

Evidence is infrastructure metadata, not SQL result sets.

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.