Set up a Vultr connector

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

Capabilities

Resource	Sync	Provision
Accounts	✅
Access control lists (ACLs)	✅

Gather Vultr credentials

Each setup method requires you to pass in credentials generated in Vultr. Gather these credentials before you move on.

Generate an API key

Log into Vultr and navigate to API in the settings menu.
Click Enable API, if necessary.
Click Generate new API key.
Carefully copy and save the API key.

That’s it! Next, move on to the connector configuration instructions.

Configure the Vultr connector

To complete this task, you’ll need:
The Connector Administrator or Super Administrator role in ConductorOne
Access to the set of Vultr credentials generated by following the instructions above

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

In ConductorOne, navigate to Admin > Connectors and click Add connector.
Search for Vultr and click Add.
Don’t see the Vultr connector? Reach out to support@conductorone.com to add Vultr to your Connectors page.
Choose how to set up the new Vultr 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
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.
Click Next.
Find the Settings area of the page and click Edit.
Enter your Vultr API key into the API key field.
Click Save.
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 Vultr connector is now pulling access data into ConductorOne.

Follow these instructions to use the Vultr connector, hosted and run in your own environment.

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.

Step 1: Configure the Vultr connector

In ConductorOne, navigate to Connectors > Add connector.
Search for Baton and click Add.
Choose how to set up the new Vultr 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
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.
Click Next.
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 Vultr connector deployment:

Secrets configuration

# baton-vultr-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-vultr-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # Vultr credentials
  BATON_BEARER_TOKEN: <Vultr API key>

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

Deployment configuration

# baton-vultr.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-vultr
  labels:
    app: baton-vultr
spec:
  selector:
    matchLabels:
      app: baton-vultr
  template:
    metadata:
      labels:
        app: baton-vultr
        baton: true
        baton-app: vultr
    spec:
      containers:
      - name: baton-vultr
        image: ghcr.io/conductorone/baton-vultr:latest
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-vultr-secrets

Step 3: Deploy the connector

Create a namespace in which to run ConductorOne connectors (if desired), then apply the secret config and deployment config files.
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 Vultr connector to. Vultr data should be found on the Entitlements and Accounts tabs.

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