Capabilities

Available hosting methods

Choose the hosting method that best suits your needs:

Gather CloudAMQP credentials

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

Create a CloudAMQP API token

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

2. Click Team Settings.

3. On the team page, click API Access.

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

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

6. Carefully copy and save the API key.

That’s it! Next, move on to the instructions for your chosen setup method.

Set up a CloudAMQP cloud-hosted 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

1. In ConductorOne, click Connectors > Add connector.

2. Search for CloudAMQP and click Add.

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

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. In the API key field, enter the API key.

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.

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

Set up a CloudAMQP cloud-hosted connector using Terraform

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

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

Set up a CloudAMQP self-hosted 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

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.

Why use Kubernetes? Kubernetes provides automated deployment, scaling, and management of your connectors. It ensures high availability and reliable operation of your connector services.

Step 1: Configure the CloudAMQP connector

1. In ConductorOne, navigate to Connectors > Add connector.

2. Search for Baton and click Add.

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

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. In the Settings area of the page, click Edit.

7. 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
        args: ["service"]
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-cloudamqp-secrets

Step 3: Deploy the connector

1. Create a namespace in which to run ConductorOne connectors (if desired):

   kubectl create namespace baton-cloudamqp
   

2. Apply the secret configuration:

   kubectl -n baton-cloudamqp apply -f baton-cloudamqp-secrets.yaml
   

3. Apply the deployment:

   kubectl -n baton-cloudamqp apply -f baton-cloudamqp.yaml
   

Step 4: Verify the deployment

1. Check that the deployment is running:

   kubectl -n c1 get pods
   

2. View the connector logs:

   kubectl -n c1 logs -l app=baton-${baton-cloudamqp}
   

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