Inside DigitalOcean’s SOX Compliance Playbook

ConductorOne docs

Set up a Buildkite connector

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

Capabilities

ResourceSyncProvision
Accounts
Teams

Available hosting methods

Choose the hosting method that best suits your needs:

MethodAvailabilityNotes
Cloud hostedA built-in, no-code connector hosted by ConductorOne.
Self-hostedA connector hosted and run in your own environment.

Gather Buildkite credentials

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

A user with Team with read membership access in Buildkite must perform this task.

Step 1: Create a new API access token

  1. In Buildkite, select your Account Name and click Personal Settings.

  2. On the left sidebar, select API Access Tokens.

  3. Click New API Access Token.

  4. Name your token ConductorOne Integration and select the following permissions:

    • Organization Access: your org name
    • Read Teams
    • Read Organizations
    • Read User
    • GraphQL API: Enable GraphQL API Access
  5. Click Create New API Access Token, then carefully copy and save the token.

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

Set up a Buildkite cloud-hosted connector

To complete this task, you’ll need:

  • The Connector Administrator or Super Administrator role in ConductorOne
  • Access to the set of Buildkite credentials generated by following the instructions above
  1. In ConductorOne, click Connectors > Add connector.

  2. Search for Buildkite and click Add.

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

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

    • Create a new managed app

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

  5. Click Next.

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

  7. Paste the API access token into the API token field.

  8. Click Save.

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

  10. To finish the configuration, select an organization. On the Buildkite integration page, click Edit in the Organization section.

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

  12. Click Add Organization to save the selected organization and then click Save.

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

Set up a Buildkite cloud-hosted connector using Terraform

As an alternative to the cloud-hosted setup process described above, you can use Terraform to configure the integration between Buildkite and ConductorOne.

See the ConductorOne Buildkite integration resource page in the ConductorOne Terraform registry for example usage and the full list of required and optional parameters.