This is an updated and improved version of the Datadog connector! If you’re setting up Datadog with ConductorOne for the first time, you’re in the right place.

Capabilities

Available hosting methods

Choose the hosting method that best suits your needs:

Gather Datadog credentials

Each setup method 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 ConductorOne and System Admin access in Datadog must perform this task.

Locate your Datadog site

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

   

Create an API key

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 “ConductorOne”, and click Create Key.

4. Copy and save the newly created API key. We’ll use this in Step 4.

   

Create an application key

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 “ConductorOne”, and click Create Key.

4. Copy and save the newly created application key. We’ll use this in Step 4.

   

That’s it! Next, move on to the instructions for your chosen setup method.

Set up a Datadog cloud-hosted connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in ConductorOne
• Access to the set of Datadog credentials generated by following the instructions above

1. In ConductorOne, click Connectors > 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 ConductorOne)

   • 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 ConductorOne users. Setting multiple owners is allowed.

   If you choose someone else, ConductorOne 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. Click Save.

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

That’s it! Your Datadog connector is now pulling access data into ConductorOne.

Set up a Datadog cloud-hosted connector using Terraform

As an alternative to the cloud-hosted setup process described above, you can use Terraform to configure the integration between Datadog and ConductorOne.

See the ConductorOne Datadog v2 integration resource page in the ConductorOne Terraform registry for example usage and the full list of required and optional parameters.

Set up a Datadog self-hosted connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in ConductorOne
• Access to the set of Datadog credentials generated by following the instructions above

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

Why use Kubernetes? Kubernetes provides automated deployment, scaling, and management of your connectors. It ensures high availability and reliable operation of your connector services.

Step 1: Configure the Datadog connector

1. In ConductorOne, navigate to 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 ConductorOne)

   • 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 ConductorOne users. Setting multiple owners is allowed.

   If you choose someone else, ConductorOne 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:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne 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 ConductorOne to provision access using this connector
  BATON_PROVISIONING: 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: ghcr.io/conductorone/baton-datadog:latest
        args: ["service"]
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-datadog-secrets

Step 3: Deploy the connector

1. Create a namespace in which to run ConductorOne connectors (if desired):

   kubectl create namespace baton-datadog
   

2. Apply the secret configuration:

   kubectl -n baton-datadog apply -f baton-datadog-secrets.yaml
   

3. Apply the deployment:

   kubectl -n baton-datadog apply -f baton-datadog.yaml
   

Step 4: Verify the deployment

1. Check that the deployment is running:

   kubectl -n c1 get pods
   

2. View the connector logs:

   kubectl -n c1 logs -l app=baton-${baton-datadog}
   

3. Check that the connector data uploaded correctly. In ConductorOne, click Applications. 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.

That’s it! Your Datadog connector is now pulling access data into ConductorOne.