Capabilities
The Google AlloyDB connector syncs the following resources:
Gather Google AlloyDB credentials
To configure the Google AlloyDB connector, you need administrator permissions in Google AlloyDB.
Navigate to the Google AlloyDB admin console or API settings.
Create API credentials for C1:
- Create a new API key or token named
C1
- Grant the required scopes or permissions
- Copy the credentials and save them securely
Follow these instructions to use a built-in, no-code connector hosted by C1.In C1, navigate to Apps > Connectors and click Add connector.
Search for Google AlloyDB and click Add.
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.
Set the connector’s Name and, optionally, a Description.
Click the pencil icon next to Owners to choose who can configure and manage this connector.
Click Add. The connector is created and its configuration page opens.
Find the Settings area of the page and click Edit.
Enter the required configuration:
- API Key: Your Google AlloyDB API key
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. 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
In C1, navigate to Apps > Connectors and click Add connector.
Search for Baton and click Add.
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.
Set the connector’s Name and, optionally, a Description.
Click the pencil icon next to Owners to choose who can configure and manage this connector.
Click Add. The connector is created and its configuration page opens.
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.
Step 2: Create Kubernetes configuration files
Create two Kubernetes manifest files for your Google AlloyDB connector deployment:Secrets configuration
See the connector’s README or run --help to see all available configuration flags and environment variables.Deployment configuration
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 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.