# Splunk

![Splunk-logo.svg](https://assets.relyanceuat.xyz/images/docs/34927090395277/34927090385293.svg)
Splunk is a software platform that indexes and correlates information in a container that makes it easy to search and monitor. It allows organizations to search, analyze and visualize the machine-generated data gathered from the websites, applications, sensors, devices etc.

In order to integrate Splunk with Relyance AI you will need your **Splunk Url**, and **API Key**. You will also need to provide a **Product** name that your would associate with the integration analysis.

Depending on your Splunk instance, you may need to add the Relyance NAT IP addresses from the article

Relyance AI IP Addresses for Allow Lists to the allow list on the Splunk side.

#### In Splunk:

1. Login to your Splunk account.
2. Click on the **General Settings** tab.
3. The **Splunk Url** is referenced by the value of API tab under Endpoints and in the case below it is
"https://api.us1.signalfx.com"

![Splunk-1.png](https://assets.relyanceuat.xyz/images/docs/34927090395277/34927090386573.png)

![Splunk-2.png](https://assets.relyanceuat.xyz/images/docs/34927090395277/34927090388365.png)

4. In order to generate the **Api Key**, click on the **Access Tokens** link at the bottom right corner.
5. Click on the **New Token** button.
6. Using the Pop up dialog box, create the new token and use that token as the **API Key**.

![Splunk-3.png](https://assets.relyanceuat.xyz/images/docs/34927090395277/34927090388877.png)

#### In the Relyance AI application:

![Screenshot 2025-11-06 160421.png](https://assets.relyanceuat.xyz/images/docs/34927090395277/40917467460877.png)
1. Login to your Relyance AI account.
2. Navigate to the **Settings** (bottom-left corner).
3. Select **Integrations**.
4. Search and locate the **Splunk** integration card and click on it.
5. Click on the **Add Connection** button on the top right.
6. Provide a meaningful name for the integration and click on the **Add** button.
7. In the **Overview** section, select the integration features you wish to enable for the integration, review the **Scope and Permission**, and **Endpoint** details and click on **Continue**. For more details, see[Integration Features](/docs/introduction-to-relyance-ai/integration-features/).
8. In the **Connection** section, provide the appropriate values and click on **Continue**,
    1. **Connection Name**: This property allows you to update the integration specified in Step 6. If you have multiple integrations for the same vendor, you may want to assign distinct names to each. This helps streamline filtering by **Discovery Source** across the **Inventory**, **Visual** **Maps**, **Assets**, and **Data Flow Analysis** pages.
    2. **Rescan Frequency**: This property allows you to configure how often Relyance executes scans against this Vendor connection.
    3. **Business Atlas Associations** (required): the business entities or products that newly discovered third parties, services and assets from this integration are attributed to. Choose at least one from the **Select Associations** dropdown — the wizard will not advance past this step without one. For more details, see [Business Atlas](/docs/other-settings/business-atlas-overview/).
9. In the **Authentication** section, provide the following information retrieved from the **Splunk** section and click on **Authenticate**. - Account Details
10. Review the configuration summary from the **Completion** section and click on **Finish.**

![Screenshot](https://assets.relyanceuat.xyz/images/docs/34927090395277/34927090391053.png)

![Screenshot 2025-11-06 160613.png](https://assets.relyanceuat.xyz/images/docs/34927090395277/40917492023565.png)

![Screenshot](https://assets.relyanceuat.xyz/images/docs/34927090395277/34927104365197.png)

11. Confirm the integration Status reflects **Connected**

<!-- auth-methods:begin (generated from the integration catalog; do not hand-edit) -->

## Authentication methods and fields

Pick one of these under **Authentication Method** on the connection wizard's **Authentication** step. This table is generated from the integration catalog, so it always matches what the form actually asks for.

| Method | Required | Optional |
| --- | --- | --- |
| **Custom** | `Account Details` | — |

<!-- auth-methods:end -->

<!-- terraform-examples:begin (generated from the integration catalog; do not hand-edit) -->

## Manage this integration with Terraform

Connections for this integration can be managed as code with the [Relyance Terraform provider](https://registry.terraform.io/providers/Relyance/relyance/latest). Non-secret fields go in `auth.params`; secret fields go in `auth.secrets_wo`, which is write-only — never stored in Terraform state. Rotate secrets by bumping `auth.secrets_wo_version`.

```hcl
resource "relyance_integration_connection" "splunk" {
  vendor = "splunk"
  name   = "<your connection name>"

  auth = {
    method = "account-credentials"
    params = {
      accounts = jsonencode([
        {
          api-key = ""
          product = ""
          splunk-url = "https://api.us1.signalfx.com"
        }
      ])
      data_storage_location = "us"
    }
  }

  scans = { "property-inspection" = { enabled = true } }
}
```

<!-- terraform-examples:end -->