Set up a CloudAMQP connector

C1 provides identity governance and just-in-time provisioning for CloudAMQP. Integrate your CloudAMQP instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access.

Capabilities

Resource	Sync	Provision
Accounts
Roles

Additional functionality: The CloudAMQP connector supports automatic account provisioning.

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

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 “C1 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.

Done. 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 C1
• Access to the set of CloudAMQP credentials generated by following the instructions above

Cloud-hosted

Follow these instructions to use a built-in, no-code connector hosted by C1.

1. In C1, navigate to Apps > Connectors and click Add connector.

2. Search for CloudAMQP and click Add.

3. Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).

   If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.

4. Set the connector’s Name and, optionally, a Description.

5. Click the pencil icon next to Owners to choose who can configure and manage this connector.

6. Click Add. The connector is created and its configuration page opens.

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

8. In the Access token field, enter the API key.

9. Click Save.

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

Done. Your CloudAMQP connector is now pulling access data into C1.

Self-hosted

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 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: Access the source code, report issues, or contribute to the project.

Step 1: Set up a new CloudAMQP connector

1. In C1, navigate to Apps > Connectors and click Add connector.

2. Search for Baton and click Add.

3. Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).

   If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.

4. Set the connector’s Name and, optionally, a Description.

5. Click the pencil icon next to Owners to choose who can configure and manage this connector.

6. Click Add. The connector is created and its configuration page opens.

7. In the Settings area of the page, click Edit.

8. 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:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 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: public.ecr.aws/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

1. Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.

2. 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 CloudAMQP connector to. CloudAMQP data should be found on the Entitlements and Accounts tabs.

Done. Your CloudAMQP connector is now pulling access data into C1.