> ## Documentation Index
> Fetch the complete documentation index at: https://www.c1.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up a Vultr connector

> C1 provides identity governance for Vultr. Integrate your Vultr instance with C1 for unified visibility and governance over user access.

## Capabilities

| Resource                    | Sync                                                          | Provision |
| :-------------------------- | :------------------------------------------------------------ | :-------- |
| Accounts                    | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |           |
| Access control lists (ACLs) | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |           |

## 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

<Steps>
  <Step>
    Log into Vultr and navigate to **API** in the settings menu.
  </Step>

  <Step>
    Click **Enable API**, if necessary.
  </Step>

  <Step>
    Click **Generate new API key**.
  </Step>

  <Step>
    Carefully copy and save the API key.
  </Step>
</Steps>

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

## Configure the Vultr connector

<Warning>
  To complete this task, you'll need:

  * The **Connector Administrator** or **Super Administrator** role in C1
  * Access to the set of Vultr credentials generated by following the instructions above
</Warning>

<Tabs>
  <Tab title="Cloud-hosted">
    **Follow these instructions to use a built-in, no-code connector hosted by C1.**

    <Steps>
      <Step>
        In C1, navigate to **Integrations** > **Connectors** and click **Add connector**.
      </Step>

      <Step>
        Search for **Vultr** and click **Add**.
      </Step>

      <Step>
        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 C1)

        * Add the connector to a managed app (select from the list of existing managed apps)

        * Create a new managed app
      </Step>

      <Step>
        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.
      </Step>

      <Step>
        Click **Next**.
      </Step>

      <Step>
        Find the **Settings** area of the page and click **Edit**.
      </Step>

      <Step>
        Enter your Vultr API key into the **API key** field.
      </Step>

      <Step>
        Click **Save**.
      </Step>

      <Step>
        The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing.
      </Step>
    </Steps>

    **Done.** Your Vultr connector is now pulling access data into C1.
  </Tab>

  <Tab title="Self-hosted">
    **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 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

    * [GitHub repository](https://github.com/conductorone/baton-vultr): Access the source code, report issues, or contribute to the project.

    ### Step 1: Configure the Vultr connector

    <Steps>
      <Step>
        In C1, navigate to **Integrations** > **Connectors** > **Add connector**.
      </Step>

      <Step>
        Search for **Baton** and click **Add**.
      </Step>

      <Step>
        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 C1)

        * Add the connector to a managed app (select from the list of existing managed apps)

        * Create a new managed app
      </Step>

      <Step>
        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.
      </Step>

      <Step>
        Click **Next**.
      </Step>

      <Step>
        In the **Settings** area of the page, click **Edit**.
      </Step>

      <Step>
        Click **Rotate** to generate a new Client ID and Secret.

        Carefully copy and save these credentials. We'll use them in Step 2.
      </Step>
    </Steps>

    ### Step 2: Create Kubernetes configuration files

    Create two Kubernetes manifest files for your Vultr connector deployment:

    #### Secrets configuration

    ```yaml theme={"theme":{"light":"css-variables","dark":"css-variables"}}
    # baton-vultr-secrets.yaml
    apiVersion: v1
    kind: Secret
    metadata:
      name: baton-vultr-secrets
    type: Opaque
    stringData:
      # C1 credentials
      BATON_CLIENT_ID: <C1 client ID>
      BATON_CLIENT_SECRET: <C1 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

    ```yaml expandable theme={"theme":{"light":"css-variables","dark":"css-variables"}}
    # 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
            env:
            - name: BATON_HOST_ID
              value: baton-vultr
            envFrom:
            - secretRef:
                name: baton-vultr-secrets
    ```

    ### Step 3: Deploy the connector

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

      <Step>
        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 Vultr connector to. Vultr data should be found on the **Entitlements** and **Accounts** tabs.
      </Step>
    </Steps>

    **Done.** Your Vultr connector is now pulling access data into C1.
  </Tab>
</Tabs>