Brainboard's documentation
Website 🏛️Go to the app ↗
  • Welcome
  • Getting started
    • Fast track
    • Start with a template
    • Start with AI
    • Use cases videos
    • Brainboard philosophy
  • Cloud design
    • Left bar
      • Cloud resources
      • Input & output
    • Design area
      • Node
      • ID card
      • Connectors
      • Versioning
      • Graphical options
    • One action
    • Code Edition
  • Data
    • Data structure
      • Project
      • Environment
      • Cloud architecture
        • Terraform files
        • Readme file
        • Architecture Synchronization
        • Remote backend
      • Template
    • Cloud providers
      • Supported cloud providers
      • Customize provider configuration
      • Unsupported cloud providers
    • Terraform / OpenTofu
      • Modules
        • Module
        • Import modules
        • Manage module
        • Terraform registry credentials
        • Use modules
    • Disaster recovery
  • Automation
    • CI/CD engine
    • Supported plugins
      • Terraform
      • Security
        • Trivy
        • Tfsec
        • Terrascan
        • OPA
        • Checkov
      • Infracost
      • Notifications
        • Email
        • Slack
        • Microsoft Teams
      • Webhooks
    • Pipelines
    • Workflow templates
    • Drift detection
      • Types of drift
      • Remediation
    • Self-Hosted Runner
      • Deploy runner with Kubernetes
      • Deploy runner with docker-compose
  • Settings
    • Overview
    • Authentication
      • Login into Brainboard
      • Single sign-on (SSO)
    • Account management
    • Organization
    • Members
    • Teams
    • Roles & Permissions (RBAC)
      • Level of access
      • Organization RBAC
      • Project RBAC
    • Integrations
      • Git configuration
        • GitHub
        • Azure DevOps (ADO)
        • Bitbucket
        • GitLab
        • How to use
      • Cloud providers
        • AWS
        • Azure
        • GCP
        • OCI
  • Security
    • Data managed by Brainboard
    • SOC 2 Type II
    • Role Based Access Control
  • Help & FAQ
    • Shortcuts
    • FAQ
    • Migration
      • Import from cloud provider
    • Support
    • Glossary
  • Changelog
Powered by GitBook
On this page
  • Configure access
  • Generate GCP credentials
  • Set the scope

Was this helpful?

Edit on GitHub
  1. Settings
  2. Integrations
  3. Cloud providers

GCP

PreviousAzureNextOCI

Last updated 20 days ago

Was this helpful?

Brainboard allows you to connect to your GCP environments, whether you want to provision resources, import existing infrastructure or simply manage your architecture on a daily basis.

Configure access

To connect Brainboard to your GCP account:

  1. Go to the settings page.

  2. Click on Google Cloud Platform

  3. Click on New connection

  4. This will open the new connection page where you can add your project id and upload your JSON file for your credentials

Generate GCP credentials

To generate GCP credentials, you will need to create a service account in the Google Cloud Console.

Here are the steps to generate GCP credentials:

  1. Go to the Google Cloud Console (https://console.cloud.google.com) and select your project.

  2. In the navigation menu, click on the hamburger icon (≡) and then select "IAM & admin" and then "Service accounts"

  3. Click on the "Create Service Account" button.

  4. In the "Create service account" form, give a name to the service account and provide a brief description.

  5. Under "Role", select the role that you want to assign to the service account. This role will determine the actions that Terraform can perform with the service account.

  6. Click on "Create" to create the service account.

  7. Once the service account is created, you will see the option to create a key. Select "JSON" as the key type and click on "Create"

  8. The JSON key file will be downloaded to your local machine. This file contains the credentials for the service account and it should be kept secure.

  9. Once you have the JSON key file, you can use it to authenticate the Terraform GCP Provider to GCP.

Set the scope

Once your credentials are added you can specify where exactly they will be used

This allows you to specify whether you want:

  1. Make the credentials the default to use within your organization: which means any architecture created in Brainboard will use these credentials if it doesn't have its own ones.

  2. Use in a specific project

  3. Use in a specific environment

  4. Use in a specific architecture

Cloud providers integration