Integrations / Google Cloud Platform

Google Cloud Platform

Google Cloud Platform (GCP) is a suite of cloud computing services providing infrastructure, data analytics, machine learning, and application services.

OAuth 2.0

Indexes

Actions

What Telara does

Capability matrix

Indexes Yes Tracks spend No Discovers shadow AI No Runs actions Yes Real-time events No

Before you connect

Prerequisites

A Google Cloud project.

Permission to create a service account and download its key.

Vendor setup

Get the credential

Create a service account

In IAM & Admin → Service Accounts, create an account for Telara.

Grant project roles

Attach the roles you want Telara to use, then create a JSON key if the Connect form asks for one.

Paste in Telara

Settings → Integrations → GCP. Upload or paste what the form asks for — not a user password.

Permissions Telara requests

https://www.googleapis.com/auth/cloud-platform
OAuth 2.0
https://www.googleapis.com/auth/cloud-platform
Service account

In Telara

Connect in Telara

OAuth 2.0

Delegated Google OAuth 2.0 connection for Google Cloud APIs. Requests offline access so Telara receives a refresh token; the existing service-account method remains available for organization-managed automation.

In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.

Service account

Google service account key (JSON) with appropriate IAM roles. The Go runtime exchanges a JWT assertion for a bearer token.

In Telara, open Settings → Integrations, choose this connector, and complete the fields Telara shows.

Fields Telara asks for

Service Account Json
Project Id

Knowledge

What gets indexed

Resource	Coverage
Resource inventory	Partial — not every record the vendor holds is synced
Iam policy	Partial — not every record the vendor holds is synced

Sync

Freshness & sync

Resource	Lag	Deletions
Resource inventory	Up to 1 day	Removed records disappear on the next full sync
Iam policy	Up to 1 day	Removed records disappear on the next full sync

Data handling

Permissions & data handling

The scopes above are the permissions this connector requests. They come from the catalog, not from a hand-written page.

Excluded from semantic search: Resource inventory, Iam policy.

After connect

Verify it worked

This connector does not declare a credential probe yet. A saved connection means Telara stored the credential, not that the vendor accepted it.

Honesty

Known limitations

The service account only sees projects it was granted. A successful connect with zero resources usually means the wrong project or role.

User OAuth is not a substitute for a service account on this connector.