> ## 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.

# Amazon Redshift Serverless

> Connect Amazon Redshift Serverless to Iru Compliance with a cross-account IAM role to collect namespace, workgroup, snapshot, and access metadata.

### About Amazon Redshift Serverless

**Redshift Serverless** APIs use the **`redshift-serverless:`** prefix, distinct from **`redshift:`** for provisioned clusters. There is **no** dedicated AWS managed **read-only** policy; attach an **inline** policy covering **`List*`** and **`Get*`** for namespaces, workgroups, snapshots, and usage limits.

### How It Works

Iru runs in its own AWS account. It **assumes a role** in your account, gated by an **External ID**, to read Redshift Serverless metadata through the API. AWS does not ship a managed read-only policy scoped only to Redshift Serverless, so you attach an **inline** (or equivalent customer-managed) policy. The permission statement usually matches the following:

```json lines theme={null}
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "redshift-serverless:ListNamespaces",
        "redshift-serverless:ListWorkgroups",
        "redshift-serverless:ListSnapshots",
        "redshift-serverless:ListUsageLimits",
        "redshift-serverless:GetNamespace",
        "redshift-serverless:GetWorkgroup",
        "redshift-serverless:GetSnapshot",
        "redshift-serverless:GetUsageLimit"
      ],
      "Resource": "*"
    }
  ]
}
```

| Detail             | Value                  |
| ------------------ | ---------------------- |
| **Category**       | Databases              |
| **Authentication** | Cross-account IAM role |

### Prerequisites

* IAM rights to **create roles** in the account hosting **Serverless** workgroups.

### Connect Amazon Redshift Serverless to Iru

<Tabs>
  <Tab title="Iru Compliance">
    <Note>
      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**](#aws) tab and follow [**Create the IAM role**](#create-the-iam-role). After you have the **Role ARN**, return to the [**Iru Compliance**](#iru-compliance) tab and complete [**Submit the role ARN in Iru**](#submit-the-role-arn-in-iru) below.
    </Note>

    #### Get the trust policy from Iru

    <Steps>
      <Step title="Open Sources">
        In Iru Compliance, on the left navigation bar, expand **Compliance** and select **Sources**.

        <Frame>
          <img src="https://mintcdn.com/iru/7HsGH7lnQ8GpVmI0/assets/media/images/iru-navigation-compliance-sources.png?fit=max&auto=format&n=7HsGH7lnQ8GpVmI0&q=85&s=595982441fd777b333b3ecfea24adc24" alt="Left navigation: Compliance expanded, Sources selected" width="424" height="1056" data-path="assets/media/images/iru-navigation-compliance-sources.png" />
        </Frame>
      </Step>

      <Step title="Turn on Amazon Redshift Serverless">
        Find **Amazon Redshift Serverless** (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.
      </Step>

      <Step title="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.

        ```json copy=false lines theme={null}
        {
          "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"
            }
          ]
        }
        ```
      </Step>

      <Step title="Switch to AWS to create the role">
        Keep the Iru wizard tab open for reference, then switch to the [**AWS**](#aws) tab and follow [**Create the IAM role**](#create-the-iam-role).
      </Step>
    </Steps>

    #### Submit the role ARN in Iru

    <Note>
      Finish the [**AWS**](#aws) tab first (through [**Create the IAM role**](#create-the-iam-role)) so you have the **Role ARN** from the new role.
    </Note>

    <Steps>
      <Step title="Paste the IAM Role ARN">
        Return to the Iru wizard tab. Paste the **Role ARN** where the connector prompts for it.
      </Step>

      <Step title="Finish the connection">
        Click **Submit Role**. When the connection succeeds, the wizard shows **Connection Configured**.
      </Step>

      <Step title="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 Redshift Serverless** card is **Active**.
      </Step>
    </Steps>
  </Tab>

  <Tab title="AWS">
    <Note>
      Complete [**Get the trust policy from Iru**](#get-the-trust-policy-from-iru) on the [**Iru Compliance**](#iru-compliance) tab before you create this role. Use the **external ID** and trust policy from the live wizard when you configure **Trusted entity**. For permissions, reuse the inline policy JSON under **How it works** on this article (or an equivalent customer-managed policy).
    </Note>

    #### Create the IAM role

    <Steps>
      <Step title="Start the Create role workflow">
        Open **IAM** → **Roles** → **Create role**.
      </Step>

      <Step title="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.
      </Step>

      <Step title="Attach the Serverless inline policy">
        Create an **inline policy** using the JSON under **How it works** at the top of this article (or save it as a customer-managed policy and attach it to the role).
      </Step>

      <Step title="Name the role and copy the ARN">
        Name the role, create it, and copy the **Role ARN**. Switch back to the [**Iru Compliance**](#iru-compliance) tab and complete [**Submit the role ARN in Iru**](#submit-the-role-arn-in-iru).
      </Step>
    </Steps>

    <Note>
      Continue on the [**Iru Compliance**](#iru-compliance) tab to paste the **Role ARN** and finish the wizard ([**Submit the role ARN in Iru**](#submit-the-role-arn-in-iru)).
    </Note>
  </Tab>
</Tabs>

### Troubleshooting

<AccordionGroup>
  <Accordion title="Nothing opens when you turn the source on">
    Check **pop-up blocker** settings for the Iru site and try again.
  </Accordion>

  <Accordion title="AccessDenied on redshift:">
    Serverless requires **`redshift-serverless:`**.
  </Accordion>

  <Accordion title="Missing workgroups">
    **`Resource: "*"`** is typical; scoped ARNs need explicit enumeration.
  </Accordion>

  <Accordion title="AssumeRole denied">
    External ID mismatch.
  </Accordion>
</AccordionGroup>

### Related Articles

<CardGroup cols={2}>
  <Card title="Amazon Redshift Data API" icon="link" href="/en/compliance/sources/amazon-redshift-data-api-source">
    Connect and manage the related source in Compliance.
  </Card>

  <Card title="AWS Redshift" icon="link" href="/en/compliance/sources/amazon-redshift-source">
    Connect and manage the related source in Compliance.
  </Card>

  <Card title="Sources Management" icon="plug" href="/en/compliance/sources-management">
    Browse and manage every Compliance source.
  </Card>

  <Card title="Getting Started With Compliance" icon="rocket" href="/en/compliance/getting-started-with-compliance">
    Frameworks, actions, and **Artifacts**.
  </Card>
</CardGroup>