Set up an Elastic connector

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

Capabilities

Resource	Sync	Provision
Accounts
Organizations
Deployment users
Deployment roles
Role mappings

Gather Elastic credentials

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

A user with the Organization owner role in Elastic must perform this task.

Generate an Elastic Cloud API key

1. In the Elasticsearch Service Console, click your avatar in the upper right corner and select Organization.

2. Navigate to the API keys tab and click Create API key.

3. Give the new API key a name, such as “C1 integration”.

4. Select an expiration for the API key.

5. In the Assign roles area, give the API key the Organization owner role.

6. Click Create API key.

7. Carefully and copy and save the new API key.

(Optional) Generate an Elastic deployment API key and look up the deployment’s endpoint

The credentials generated in this step are required for C1 to sync information on Elastic deployment users and deployment roles, and to provision Elastic deployment role assignments. If you do not want to sync or provision deployment users or deployment roles, skip this section.

1. Back on the Elasticsearch Service Console homepage, find the Hosted deployments area of the page and click the name of the deployment you want to integrate.

2. On the deployment’s page, click Manage permissions.

3. In the sidebar, click API keys > Create API key.

4. Give the new API key a name, such as “C1 deployment info integration”.

5. Select the Personal API key option.

6. Click Create API key.

7. Carefully and copy and save the new API key.

8. We also need to look up the deployment’s Elasticsearch endpoint. Click the Elastic logo to return to your deployment’s home page.

9. Click Add integrations.

10. In the upper right corner of the screen, click Connection details.

11. Carefully copy and save the Elasticsearch endpoint.

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

Configure the Elastic connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in C1
• Access to the set of Elastic 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 Apps > Connectors and click Add connector.

2. Search for Elastic and click Add.

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

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

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

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

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

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

9. Optional. If you want to sync information on Elastic deployment users and deployment roles, paste the Deployment API key and Deployment endpoint into their respective fields.

10. Optional. By default, C1 will sync information about all users in all organizations. If you want to limit the sync to a single organization, paste that organization’s ID into the Organization ID field.

11. Click Save.

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

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

Self-hosted

Follow these instructions to use the Elastic 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

Contact C1’s support team to download the latest version of the connector.

Step 1: Set up a new Elastic connector

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

2. Search for Baton and click Add.

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

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

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

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

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

8. 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 Elastic connector deployment:

Secrets configuration

# baton-elastic-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-elastic-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>
  
  # Elastic credentials
  BATON_API_KEY: <Elastic API key>
  BATON_DEPLOYMENT_API_KEY: <Elasticsearch deployment API key>
  BATON_DEPLOYMENT_ENDPOINT: <Elasticsearch deployment endpoint>

  # Optional: include if you want C1 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-elastic.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-elastic
  labels:
    app: baton-elastic
spec:
  selector:
    matchLabels:
      app: baton-elastic
  template:
    metadata:
      labels:
        app: baton-elastic
        baton: true
        baton-app: elastic
    spec:
      containers:
      - name: baton-elastic
        image: public.ecr.aws/conductorone/baton-elastic:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-elastic
        envFrom:
        - secretRef:
            name: baton-elastic-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 Elastic connector to. Elastic data should be found on the Entitlements and Accounts tabs.

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