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.

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.

Capabilities

Resource	Sync	Provision
Accounts
Roles
Teams
Schedules	*
Secrets - API keys

This connector can sync secrets 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.

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.

Locate your Datadog site

Your Datadog site determines which regional API endpoint the connector uses. Identify your site from your Datadog URL:

Datadog URL	Site value
https://app.datadoghq.com	datadoghq.com
https://app.datadoghq.eu	datadoghq.eu
https://app.us3.datadoghq.com	us3.datadoghq.com
https://app.us5.datadoghq.com	us5.datadoghq.com
https://app.ddog-gov.com	ddog-gov.com
https://app.ap1.datadoghq.com	ap1.datadoghq.com

1. Navigate to the Datadog login screen and make a note of your Datadog site from the URL.

Create an API key

The API key authenticates requests to the Datadog API.

1. Log into Datadog account and click User Account > Organizational Settings.

2. Click API Keys and then click + New Key.

3. Enter a name for your new key, such as “C1”, and click Create Key.

4. Copy and save the newly created API key.

Create an application key

The application key works with the API key to control which API endpoints are accessible. Application keys inherit the permissions of the user who creates them by default, but you can restrict them to specific scopes.

1. Navigate back to Organization Settings.

2. Click Application Keys and then click + New Key.

3. Enter a name for your new key, such as “C1”, and click Create Key.

4. Copy and save the newly created application key.

If you configure scopes on the application key, the connector requires the following scopes at minimum:

• Access Management — read and manage users and roles
• Teams — read team information and membership

If scopes are not configured, the application key inherits all permissions of the user who created it.

Validate your credentials

After creating your keys, verify they work before configuring the connector.

1. Run the following command, replacing the placeholders with your API key, application key, and site:

   curl -s -X GET "https://api.<your-site>/api/v1/validate" \
     -H "DD-API-KEY: <your-api-key>" \
     -H "DD-APPLICATION-KEY: <your-app-key>"
   

   For example, if your site is datadoghq.com:

   curl -s -X GET "https://api.datadoghq.com/api/v1/validate" \
     -H "DD-API-KEY: <your-api-key>" \
     -H "DD-APPLICATION-KEY: <your-app-key>"
   
2. A successful response returns:

   {"valid": true}
   

   If you see {"valid": false} or an authentication error, verify:

   • The API key and application key are correct and have not been revoked
   • The site value matches your Datadog instance
   • The application key has the required scopes (Access Management and Teams)

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

Configure the Datadog connector

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

Cloud-hosted

Follow these instructions to use a built-in, no-code connector hosted by C1.

1. In C1, navigate to Integrations > Connectors and click Add connector.

2. Search for Datadog v2 and click Add.

3. 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
4. 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.

5. Click Next.

6. Find the Settings area of the page and click Edit.

7. Select your Datadog site from the list.

8. Paste the API key into the API key field.

9. Paste the application key into the Application key field.

10. Optional. Enable Sync secrets to display them on the Inventory page.

11. Optional. Enable Sync schedules.

12. Click Save.

13. The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

Done. Your Datadog connector is now pulling access data into C1.

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: For stable binaries (Windows/Linux/macOS) and container images.

• GitHub repository: Access the source code, report issues, or contribute to the project.

Step 1: Set up a new Datadog connector

1. In C1, navigate to Integrations > Connectors > Add connector.

2. Search for Baton and click Add.

3. 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
4. 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.

5. Click Next.

6. In the Settings area of the page, click Edit.

7. Click Rotate to generate a new Client ID and Secret.

   Carefully copy and save these credentials. We’ll use them in Step 2.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your Datadog connector deployment:

Secrets configuration

# 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

# 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: public.ecr.aws/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

1. Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.

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

Done. Your Datadog connector is now pulling access data into C1.

Troubleshooting Datadog authentication

The connector reports “API key not valid”

The connector validates both the API key and application key at startup. If you see this error:

1. Verify the API key has not been revoked. In Datadog, go to Organization Settings > API Keys and check that the key is still listed.
2. Verify the application key has not been revoked. Go to Organization Settings > Application Keys and check that the key is still listed.
3. Confirm the site value matches your Datadog instance. An incorrect site causes API calls to reach the wrong regional endpoint, resulting in authentication failures.

The connector syncs users but not teams or roles

If the connector authenticates successfully but fails to sync certain resources, the application key may lack the required scopes:

1. In Datadog, go to Organization Settings > Application Keys.
2. Click the application key used by the connector.
3. Verify that the Access Management and Teams scopes are included. If scopes are not configured, the key inherits all permissions of the user who created it — verify that user has the Datadog Admin or Datadog Standard role.