Set up a Datadog connector

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.

Connector actions

Connector actions are custom capabilities that extend C1 automations with app-specific operations. You can use connector actions in the Perform connector action automation step.

Action name	Additional fields	Description
enable_user	`user_id` (string, required)	Re-enables a previously disabled Datadog user.
disable_user	`user_id` (string, required)	Disables a Datadog user. Datadog has no permanent delete, so the account is retained and can be re-enabled later.
update_user	`user_id` (string, required), `name` (string, optional), `email` (string, optional), `title` (string, optional)	Updates the user’s display name, email and/or job title. At least one optional field must be provided.

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, plus User Access Invite and User Access Manage to create, update, enable, and disable users from C1.

Locate your Datadog site

Navigate to the Datadog login screen and make a note of your Datadog site. Valid Datadog sites are datadoghq.com, us3.datadoghq.com, us5.datadoghq.com, datadoghq.eu, ddog-gov.com, and ap1.datadoghq.com.

Create an API key

Log into your Datadog account and navigate to User Account > Organizational Settings.

Click API Keys and then click + New Key.

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

Copy and save the newly created API key.

Create an application key

Navigate back to Organization Settings.

Click Application Keys and then click + New Key.

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

Copy and save the newly created application key.

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
Self-hosted

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

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

Search for Datadog v2 and click Add.

Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.

Set the connector’s Name and, optionally, a Description.

Click the pencil icon next to Owners to choose who can configure and manage this connector.

Click Add. The connector is created and its configuration page opens.

Find the Settings area of the page and click Edit.

Select your Datadog site from the list.

Paste the API key into the API key field.

Paste the application key into the Application key field.

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

Optional. Enable Sync schedules.

Click Save.

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.

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

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

Search for Baton and click Add.

Set the connector’s Name and, optionally, a Description.

Click the pencil icon next to Owners to choose who can configure and manage this connector.

Click Add. The connector is created and its configuration page opens.

In the Settings area of the page, click Edit.

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

  # Optional: include if you want to sync secrets (API keys) from Datadog
  BATON_SYNC_SECRETS: 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

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

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.

Welcome

Manage connectors

Deploy connectors

Upload connector data

Configurable connectors

Pre-built connectors

Set up a Datadog connector

Capabilities

Connector actions

Gather Datadog credentials

Locate your Datadog site

Create an API key

Create an application key

Configure the Datadog connector

Resources

Step 1: Set up a new Datadog connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

​Capabilities

​Connector actions

​Gather Datadog credentials

​Locate your Datadog site

​Create an API key

​Create an application key

​Configure the Datadog connector

​Resources

​Step 1: Set up a new Datadog connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Capabilities

Connector actions

Gather Datadog credentials

Locate your Datadog site

Create an API key

Create an application key

Configure the Datadog connector

Resources

Step 1: Set up a new Datadog connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector