Skip to main content
Version: 15.2.1

Google Cloud Connector

The Google Cloud connector ingests cloud resources from a Google Cloud Platform organization, folder, or project into the Catalog. It runs through the ibdm binary in one of two modes:

  • Sync — pull-based: enumerates resources via the Cloud Asset API and exits. Only resource metadata is retrieved (the RESOURCE content type) — IAM policies, org policies, and other Cloud Asset content types are not synced.
  • Run — push-based: subscribes to a Pub/Sub subscription fed by a Cloud Asset Feed. On delete events, the emitted item carries the last-known (priorAsset) resource snapshot, since there is no current asset to report.

Commands​

ibdm sync gcp --include-internal-mappings=all
ibdm run gcp --include-internal-mappings=all

The commands use every internal mapping of the source. To select only some of them, or to add mappings of your own, see Mappings.

Configuration​

VariableRequiredDescription
GOOGLE_CLOUD_SYNC_PARENTSyncName of the organization, folder, or project containing the resources to sync. Must be one of organizations/{org-number}, folders/{folder-number}, projects/{project-id}, or projects/{project-number}.
GOOGLE_CLOUD_PUBSUB_PROJECTRunProject hosting the Pub/Sub subscription.
GOOGLE_CLOUD_PUBSUB_SUBSCRIPTIONRunName of the Pub/Sub subscription the source consumes events from.
GOOGLE_APPLICATION_CREDENTIALSOptionalPath to a service-account key file, used by Application Default Credentials.

Authentication​

The source authenticates through Application Default Credentials (ADC). You can supply credentials in any of the standard ADC ways, including pointing GOOGLE_APPLICATION_CREDENTIALS at a service-account key file. The principal must have read access to the resources you intend to ingest.

Internal mappings​

ibdm mappings list gcp prints the internal mappings of this source, and the Internal Mappings reference lists the Item Type each one writes.

The source ships one internal mapping per supported asset type: buckets, clusters, computeinstances, firewallrules, folders, jobs, networks, projects, services and sqlinstances. Every mapping is independent: the sync asks the Cloud Asset API for the asset types of the selected mappings only, and the Pub/Sub stream keeps only the events of those asset types. No internal mapping creates relationships to another one.

See also​