For the complete documentation index, see llms.txt. This page is also available as Markdown.

GCP

Create Teleskope Service Account

Create a Teleskope service account in your GCP project. For BigQuery, we have downloadable Terraform scripts here that create everything below.

Terraform

Variable
Description
Example

project_id

(Required) Your GCP Project ID

"my-project-id"

resource "google_service_account" "teleskope" {
  account_id   = "teleskope"
  display_name = "Teleskope Read Only User"
  project      = "{project_id}"
}

Grant Resource Manager Read Access to Teleskope Service Account

Grant the following resource manager permissions to the Teleskope service account you created above:

  • resourcemanager.projects.list

  • resourcemanager.projects.get

  • resourcemanager.folders.get

  • resourcemanager.folders.list

  • resourcemanager.organizations.get

  • compute.regions.list

Terraform

Variable
Description
Example

org_id

(Required) Your GCP Org ID

"130342390179"

Grant Teleskope Access to the Service Account

How Teleskope authenticates as the service account depends on your deployment model. Follow one of the two sections below.

Teleskope-Managed (GCP) Deployments

If Teleskope runs inside your own GCP project (Teleskope-Managed), the platform authenticates with native GCP service-account impersonation. Do not configure workload identity federation or any AWS trust: that applies to SaaS only, and the workload-federation fields are left blank when the project is enrolled.

Grant Teleskope's application service account permission to impersonate the Teleskope connector service account (your Teleskope account team will confirm the application service account's email, of the form teleskope-<name>-app@<deployment-project>.iam.gserviceaccount.com):

If you created the connector service account inside the Teleskope deployment project itself, this permission is already in place and no grant is needed.

Configure Workload Identity Federation (SaaS Only)

Teleskope SaaS is run in an isolated AWS account. In order to grant Teleskope SaaS the ability to connect to GCP, you will need to configure workload identity federation. Skip this entire section for Teleskope-Managed deployments.

Create Workload Identity Federation Pool

Go to https://console.cloud.google.com/ > Workload Identity Federation > Create Pool

  • Name: teleskope-pool

  • Pool id : teleskope-pool

  • Provider:

    • Select Provider: AWS

    • Provider Name: teleskope-provider

    • AWS Account: {origin_aws_account_id}

Grant Access to Teleskope Service Account

Once pool is created, click Grant Access, and select the Teleskope service account you created above.

Terraform

Variable
Description
Example

origin_aws_account_id

(Required) AWS Account ID where Teleskope is deployed.

"012345678912"

project_id

(Required) Your GCP Project ID

"my-project-id"

Last updated

Was this helpful?