> ## 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 CloudAMQP connector
> C1 provides identity governance for CloudAMQP. Integrate your CloudAMQP instance with C1 to run user access reviews (UARs) and enable just-in-time access requests.
## 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 "C1 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.
**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
**Follow these instructions to use a built-in, no-code connector hosted by C1.**
In C1, navigate to **Integrations** > **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 C1)
* 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 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.
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.
**Done.** Your CloudAMQP connector is now pulling access data into C1.
**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](https://github.com/conductorone/baton-cloudamqp): Access the source code, report issues, or contribute to the project.
### Step 1: Set up a new CloudAMQP connector
In C1, navigate to **Integrations** > **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 C1)
* 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 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.
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
```yaml expandable theme={"theme":{"light":"css-variables","dark":"css-variables"}}
# baton-cloudamqp-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
name: baton-cloudamqp-secrets
type: Opaque
stringData:
# C1 credentials
BATON_CLIENT_ID:
BATON_CLIENT_SECRET:
# CloudAMQP credentials
BATON_TOKEN:
```
See the connector's README 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-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 C1 connectors (if desired), then apply the secret config and deployment config files.
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.