Set up a Google AlloyDB connector

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

Capabilities

The Google AlloyDB connector syncs the following resources:

Resource	Sync	Provision
Accounts

Gather Google AlloyDB credentials

To configure the Google AlloyDB connector, you need administrator permissions in Google AlloyDB.

1. Navigate to the Google AlloyDB admin console or API settings.

2. Create API credentials for C1:

   1. Create a new API key or token named C1
   2. Grant the required scopes or permissions
   3. Copy the credentials and save them securely

Configure the Google AlloyDB connector

Cloud-hosted

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

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

2. Search for Google AlloyDB and click Add.

3. Choose how to set up the new Google AlloyDB connector:

   • Add the connector to a currently unmanaged app
   • Add the connector to a managed app
   • Create a new managed app
4. Set the owner for this connector.

5. Click Next.

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

7. Enter the required configuration:

   • API Key: Your Google AlloyDB 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.

Done. Your Google AlloyDB connector is now pulling access data into C1.

Self-hosted

Follow these instructions to use the Google AlloyDB 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.

Step 1: Set up a new Google AlloyDB connector

1. In C1, navigate to Integrations > Connectors > Add connector.

2. Search for Baton and click Add.

3. Choose how to set up the new Google AlloyDB connector:

   • Add the connector to a currently unmanaged app
   • Add the connector to a managed app
   • Create a new managed app
4. Set the owner for this connector.

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.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your Google AlloyDB connector deployment:

Secrets configuration

# baton-alloydb-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-alloydb-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>

  # Google AlloyDB credentials
  # Add connector-specific credentials here

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

Deployment configuration

# baton-alloydb.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-alloydb
  labels:
    app: baton-alloydb
spec:
  selector:
    matchLabels:
      app: baton-alloydb
  template:
    metadata:
      labels:
        app: baton-alloydb
        baton: "true"
        baton-app: alloydb
    spec:
      containers:
      - name: baton-alloydb
        image: public.ecr.aws/conductorone/baton-alloydb:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-alloydb
        envFrom:
        - secretRef:
            name: baton-alloydb-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 Applications. On the Managed apps tab, locate and click the name of the application you added the Google AlloyDB connector to. Google AlloyDB data should be found on the Entitlements and Accounts tabs.

Done. Your Google AlloyDB connector is now pulling access data into C1.

---

All versions of this connector are available at dist.conductorone.com.