Set up a CloudAMQP connector

Capabilities
Gather CloudAMQP credentials
Create a CloudAMQP API token
Configure the CloudAMQP connector

Capabilities

Resource	Sync	Provision
Accounts
Roles

Gather CloudAMQP credentials

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

Create a CloudAMQP API token

In CloudAMQP, log in using an account with team admin permissions and click the team name in the top menu bar.

Click Team Settings.

On the team page, click API Access.

In the Full access keys area of the page, enter a label for the new API key (such as “ConductorOne integration”) in the Comment text box.

Click Generate New Key. The new key is added to the list of API keys.

Carefully copy and save the API key.

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

Configure the CloudAMQP connector

To complete this task, you’ll need:

The Connector Administrator or Super Administrator role in ConductorOne
Access to the set of CloudAMQP credentials generated by following the instructions above

Cloud-hosted
Self-hosted

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 CloudAMQP and click Add.

Choose how to set up the new CloudAMQP 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.

In the API key field, enter the API key.

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 CloudAMQP connector is now pulling access data into ConductorOne.

Follow these instructions to use the CloudAMQP 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: Set up a new CloudAMQP connector

In ConductorOne, navigate to Connectors > Add connector.

Search for Baton and click Add.

Choose how to set up the new CloudAMQP 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

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 CloudAMQP connector deployment:

Secrets configuration

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

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

Deployment configuration

# baton-cloudamqp.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-cloudamqp
  labels:
    app: baton-cloudamqp
spec:
  selector:
    matchLabels:
      app: baton-cloudamqp
  template:
    metadata:
      labels:
        app: baton-cloudamqp
        baton: true
        baton-app: cloudamqp
    spec:
      containers:
      - name: baton-cloudamqp
        image: ghcr.io/conductorone/baton-cloudamqp:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-cloudamqp
        envFrom:
        - secretRef:
            name: baton-cloudamqp-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 CloudAMQP connector to. CloudAMQP data should be found on the Entitlements and Accounts tabs.

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

Set up ClickHouse connector

Set up a Cloudflare connector

⌘I

Welcome

Build connectors

Configure connectors

Deploy connectors

Upload connector data

Connector library

Set up a CloudAMQP connector

Capabilities

Gather CloudAMQP credentials

Create a CloudAMQP API token

Configure the CloudAMQP connector

Step 1: Set up a new CloudAMQP connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

Welcome

Build connectors

Configure connectors

Deploy connectors

Upload connector data

Connector library

​Capabilities

​Gather CloudAMQP credentials

​Create a CloudAMQP API token

​Configure the CloudAMQP connector

​Step 1: Set up a new CloudAMQP connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Capabilities

Gather CloudAMQP credentials

Create a CloudAMQP API token

Configure the CloudAMQP connector

Step 1: Set up a new CloudAMQP connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector