> ## Documentation Index
> Fetch the complete documentation index at: https://www.c1.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up a Datadog connector

> C1 provides identity governance for Datadog. Integrate your Datadog instance with C1 to run user access reviews (UARs) and enable just-in-time access requests.

<Tip>
  **This is an updated and improved version of the Datadog connector!** If you're setting up Datadog with C1 for the first time, you're in the right place.
</Tip>

## Capabilities

| Resource           | Sync                                                            | Provision                                                     |
| :----------------- | :-------------------------------------------------------------- | :------------------------------------------------------------ |
| Accounts           | <Icon icon="square-check" iconType="solid" color="#c937ae" />   |                                                               |
| Roles              | <Icon icon="square-check" iconType="solid" color="#c937ae" />   | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |
| Teams              | <Icon icon="square-check" iconType="solid" color="#c937ae" />   | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |
| Schedules          | <Icon icon="square-check" iconType="solid" color="#c937ae" />\* |                                                               |
| Secrets - API keys | <Icon icon="square-check" iconType="solid" color="#c937ae" />   |                                                               |

[This connector can sync secrets](/product/admin/inventory) and display them on the **Inventory** page.

\*Schedules are not synced by default, but you can opt into syncing them when configuring the connector.

## Gather Datadog credentials

Configuring the connector requires you to pass in credentials generated in Datadog. Gather these credentials before you move on.

<Warning>
  A user with the **Connector Administrator** or **Super Administrator** role in C1 and the **Datadog Admin** or **Datadog standard** role in Datadog must perform this task.

  If your user has a custom Datadog role, make sure it includes the **User App Keys** and **API Keys Read** permissions.
</Warning>

### Locate your Datadog site

<Steps>
  <Step>
    Navigate to the Datadog login screen and make a note of your Datadog site:
  </Step>
</Steps>

### Create an API key

<Steps>
  <Step>
    Log into Datadog account and click **User Account** > **Organizational Settings**.
  </Step>

  <Step>
    Click **API Keys** and then click **+ New Key**.
  </Step>

  <Step>
    Enter a name for your new key, such as "C1", and click **Create Key**.
  </Step>

  <Step>
    Copy and save the newly created API key.
  </Step>
</Steps>

### Create an application key

<Steps>
  <Step>
    Navigate back to **Organization Settings**.
  </Step>

  <Step>
    Click **Application Keys** and then click **+ New Key**.
  </Step>

  <Step>
    Enter a name for your new key, such as "C1", and click **Create Key**.
  </Step>

  <Step>
    Copy and save the newly created application key.
  </Step>
</Steps>

**Done.** Next, move on to the connector configuration instructions.

## Configure the Datadog connector

<Warning>
  To complete this task, you'll need:

  * The **Connector Administrator** or **Super Administrator** role in C1
  * Access to the set of Datadog credentials generated by following the instructions above
</Warning>

<Tabs>
  <Tab title="Cloud-hosted">
    **Follow these instructions to use a built-in, no-code connector hosted by C1.**

    <Steps>
      <Step>
        In C1, navigate to **Integrations** > **Connectors** and click **Add connector**.
      </Step>

      <Step>
        Search for **Datadog v2** and click **Add**.
      </Step>

      <Step>
        Choose how to set up the new Datadog connector:

        * Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren't yet managed with C1)
        * Add the connector to a managed app (select from the list of existing managed apps)
        * Create a new managed app
      </Step>

      <Step>
        Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of C1 users. Setting multiple owners is allowed.

        If you choose someone else, C1 will notify the new connector owner by email that their help is needed to complete the setup process.
      </Step>

      <Step>
        Click **Next**.
      </Step>

      <Step>
        Find the **Settings** area of the page and click **Edit**.
      </Step>

      <Step>
        Select your Datadog site from the list.
      </Step>

      <Step>
        Paste the API key into the **API key** field.
      </Step>

      <Step>
        Paste the application key into the **Application key** field.
      </Step>

      <Step>
        **Optional.** Enable **Sync secrets** to display them on the [Inventory page](/product/admin/inventory).
      </Step>

      <Step>
        **Optional.** Enable **Sync schedules**.
      </Step>

      <Step>
        Click **Save**.
      </Step>

      <Step>
        The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing.
      </Step>
    </Steps>

    **Done.** Your Datadog connector is now pulling access data into C1.
  </Tab>

  <Tab title="Self-hosted">
    **Follow these instructions to use the Datadog connector, hosted and run in your own environment.**

    When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1 UI for access reviews and access requests.

    ### Resources

    * [Official download center](https://dist.conductorone.com/ConductorOne/baton-datadog): For stable binaries (Windows/Linux/macOS) and container images.

    * [GitHub repository](https://github.com/conductorone/baton-datadog): Access the source code, report issues, or contribute to the project.

    ### Step 1: Set up a new Datadog connector

    <Steps>
      <Step>
        In C1, navigate to **Integrations** > **Connectors** > **Add connector**.
      </Step>

      <Step>
        Search for **Baton** and click **Add**.
      </Step>

      <Step>
        Choose how to set up the new Datadog connector:

        * Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren't yet managed with C1)
        * Add the connector to a managed app (select from the list of existing managed apps)
        * Create a new managed app
      </Step>

      <Step>
        Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of C1 users. Setting multiple owners is allowed.

        If you choose someone else, C1 will notify the new connector owner by email that their help is needed to complete the setup process.
      </Step>

      <Step>
        Click **Next**.
      </Step>

      <Step>
        In the **Settings** area of the page, click **Edit**.
      </Step>

      <Step>
        Click **Rotate** to generate a new Client ID and Secret.

        Carefully copy and save these credentials. We'll use them in Step 2.
      </Step>
    </Steps>

    ### Step 2: Create Kubernetes configuration files

    Create two Kubernetes manifest files for your Datadog connector deployment:

    #### Secrets configuration

    ```yaml expandable theme={"theme":{"light":"css-variables","dark":"css-variables"}}
    # baton-datadog-secrets.yaml
    apiVersion: v1
    kind: Secret
    metadata:
      name: baton-datadog-secrets
    type: Opaque
    stringData:
      # C1 credentials
      BATON_CLIENT_ID: <C1 client ID>
      BATON_CLIENT_SECRET: <C1 client secret>
      
      # Datadog credentials
      BATON_API_KEY: <Datadog API key>
      BATON_APP_KEY: <Datadog app key>
      BATON_SITE: <Your Datadog site ID>

      # Optional: include if you want C1 to provision access using this connector
      BATON_PROVISIONING: true

      # Optional: include if you want to sync schedule data from Datadog
      BATON_SYNC_SCHEDULES: true
    ```

    See the connector's README or run `--help` to see all available configuration flags and environment variables.

    #### Deployment configuration

    ```yaml expandable theme={"theme":{"light":"css-variables","dark":"css-variables"}}
    # baton-datadog.yaml
    apiVersion: apps/v1
    kind: Deployment
    metadata:
      name: baton-datadog
      labels:
        app: baton-datadog
    spec:
      selector:
        matchLabels:
          app: baton-datadog
      template:
        metadata:
          labels:
            app: baton-datadog
            baton: true
            baton-app: datadog
        spec:
          containers:
          - name: baton-datadog
            image: ghcr.io/conductorone/baton-datadog:latest
            imagePullPolicy: IfNotPresent
            env:
            - name: BATON_HOST_ID
              value: baton-datadog
            envFrom:
            - secretRef:
                name: baton-datadog-secrets
    ```

    ### Step 3: Deploy the connector

    <Steps>
      <Step>
        Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.
      </Step>

      <Step>
        Check that the connector data uploaded correctly. In C1, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Datadog connector to. Datadog data should be found on the **Entitlements** and **Accounts** tabs.
      </Step>
    </Steps>

    **Done.** Your Datadog connector is now pulling access data into C1.
  </Tab>
</Tabs>