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

# AWS Lambda

> Connect AWS Lambda to Iru Compliance with a cross-account IAM role to collect function inventory, runtime, IAM role binding, and layer configuration metadata.

### About AWS Lambda

The **AWS Lambda** connector collects **function configuration**, **layers**, **event source mappings**, **concurrency settings**, and related metadata across Regions without invoking functions or downloading deployment packages. Iru uses **`sts:AssumeRole`** into a role you create, gated by an **external ID** from the wizard.

### How It Works

Iru runs in its own AWS account. To read **Lambda** configuration in your account, you create an **IAM role** that trusts Iru’s principal (**`sts:AssumeRole`** + wizard **External ID**) with read-only **`lambda:`** permissions. Paste the role’s **ARN** back into Iru.

Create an IAM role that trusts Iru’s principal and attach **`AWSLambda_ReadOnlyAccess`**, or use the tighter inline policy below if your security team prefers least privilege.

| Detail             | Value                  |
| ------------------ | ---------------------- |
| **Category**       | Compute / serverless   |
| **Authentication** | Cross-account IAM role |

References: [AWSLambda\_ReadOnlyAccess](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AWSLambda_ReadOnlyAccess.html), [Lambda security](https://docs.aws.amazon.com/lambda/latest/dg/lambda-security.html).

### Prerequisites

* IAM permission to **create roles** and attach policies.
* **Principal** and **external ID** values copied from **your** live connector (samples like account `753695775620` may differ per tenant).

### Connect AWS Lambda 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 in AWS**](#create-the-iam-role-in-aws). 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 AWS Lambda">
        Find **AWS Lambda** (use **Category** or **Search by name or description**). On that card, turn on the **toggle**. Keep the 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 in AWS**](#create-the-iam-role-in-aws).
      </Step>
    </Steps>

    #### Submit the role ARN in Iru

    <Note>
      Finish the [**AWS**](#aws) tab first (through [**Create the IAM role in AWS**](#create-the-iam-role-in-aws)) 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 **AWS Lambda** 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**.
    </Note>

    #### Create the IAM role in AWS

    <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`** unless the wizard differs. Enable **Require external ID** and paste the external ID from Iru.
      </Step>

      <Step title="Attach Lambda read permissions">
        Attach **`AWSLambda_ReadOnlyAccess`**, **or** attach this **inline policy**:

        ```json lines theme={null}
        {
          "Version": "2012-10-17",
          "Statement": [
            {
              "Effect": "Allow",
              "Action": [
                "lambda:Get*",
                "lambda:List*"
              ],
              "Resource": "*"
            }
          ]
        }
        ```

        The managed policy covers actions such as `GetFunction`, `ListFunctions`, `GetFunctionConfiguration`, layers, aliases, and mappings; the inline variant relies on `Get*` / `List*` wildcards.
      </Step>

      <Step title="Name the role and copy the ARN">
        Name the role (for example **`IruLambdaReadOnly`**), create it, and copy its **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>

      <Step title="Verify the trust relationship">
        Confirm **Trust relationships** matches 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="AssumeRole denied">
    External ID or principal mismatch - re-copy from Iru.
  </Accordion>

  <Accordion title="Empty Regional lists">
    Confirm functions exist in enabled Regions and the role targets the right account.
  </Accordion>

  <Accordion title="Encrypted env vars opaque">
    Read-only APIs may not expose ciphertext details - metadata still evidences configuration presence.
  </Accordion>
</AccordionGroup>

### Considerations

<CardGroup cols={2}>
  <Card title="Lambda is Regional; first scans walk every enabled…" icon="circle-info">
    Lambda is **Regional**; first scans walk every enabled Region.
  </Card>

  <Card title="Iru does not invoke functions or extract ZIP…" icon="shield">
    Iru **does not invoke** functions or extract ZIP artifacts - configuration evidence only.
  </Card>
</CardGroup>

### Related Articles

<CardGroup cols={2}>
  <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>

  <Card title="Iru Overview" icon="layer-group" href="/en/iru/platform-overview/iru-overview">
    How Endpoint, Compliance, and Identity fit together.
  </Card>

  <Card title="Artifacts Management" icon="folder-open" href="/en/compliance/artifacts-management">
    Upload, review, and organize evidence from sources and actions.
  </Card>
</CardGroup>