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

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

## Capabilities

| Resource | Sync                                                          | Provision |
| :------- | :------------------------------------------------------------ | :-------- |
| Accounts | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |           |
| Teams    | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |           |

## Gather Buildkite credentials

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

<Warning>
  **Important**

  A user with **Team with read membership** access in Buildkite must perform this task.
</Warning>

### Step 1: Create a new API access token

<Steps>
  <Step>
    In Buildkite, select your **Account Name** and click **Personal Settings**.
  </Step>

  <Step>
    On the left sidebar, select **API Access Tokens**.
  </Step>

  <Step>
    Click **New API Access Token**.
  </Step>

  <Step>
    Name your token **C1 Integration** and select the following permissions:

    * Organization Access: your org name
    * Read Teams
    * Read Organizations
    * Read User
  </Step>

  <Step>
    Click **Create New API Access Token**, then carefully copy and save the token.
  </Step>
</Steps>

Next, move on to the instructions for your chosen setup method.

## Configure the Buildkite connector

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

  * The **Connector Administrator** or **Super Administrator** role in C1
  * Access to the set of Buildkite 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 **Buildkite** and click **Add**.
      </Step>

      <Step>
        Choose how to set up the new Buildkite 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>
        Paste the API access token into the **API token** 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>

      <Step>
        To finish the configuration, select an organization. On the Buildkite integration page, click **Edit** in the **Organization** section.
      </Step>

      <Step>
        Wait for the UI to populate a list of organizations your API access token has access to, then select the appropriate organization.
      </Step>

      <Step>
        Click **Add Organization** to save the selected organization and then click **Save**.
      </Step>
    </Steps>

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

  <Tab title="Self-hosted">
    Follow these instructions to use the [Buildkite](https://github.com/conductorone/baton-buildkite) 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.

    ### Step 1: Set up a new Buildkite 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 Buildkite 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. You will use them in Step 2.
      </Step>
    </Steps>

    ### Step 2: Create Kubernetes configuration files

    Create two Kubernetes manifest files for your Buildkite connector deployment:

    #### Secrets configuration

    ```yaml expandable theme={"theme":{"light":"css-variables","dark":"css-variables"}}
    # baton-buildkite-secrets.yaml
    apiVersion: v1
    kind: Secret
    metadata:
      name: baton-buildkite-secrets
    type: Opaque
    stringData:
      # C1 credentials
      BATON_CLIENT_ID: <C1 client ID>
      BATON_CLIENT_SECRET: <C1 client secret>

      # Buildkite credentials
      BATON_API_TOKEN: <Your Buildkite API access token>
      BATON_ORGANIZATION: <Your Buildkite organization slug>
    ```

    See the connector's [README](https://github.com/conductorone/baton-buildkite) 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-buildkite.yaml
    apiVersion: apps/v1
    kind: Deployment
    metadata:
      name: baton-buildkite
      labels:
        app: baton-buildkite
    spec:
      selector:
        matchLabels:
          app: baton-buildkite
      template:
        metadata:
          labels:
            app: baton-buildkite
            baton: true
            baton-app: buildkite
        spec:
          containers:
          - name: baton-buildkite
            image: ghcr.io/conductorone/baton-buildkite:latest
            imagePullPolicy: IfNotPresent
            env:
            - name: BATON_HOST_ID
              value: baton-buildkite
            envFrom:
            - secretRef:
                name: baton-buildkite-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 **Applications**. On the **Managed apps** tab, locate and click the name of the application you added the Buildkite connector to. Buildkite data should be found on the **Entitlements** and **Accounts** tabs.
      </Step>
    </Steps>

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