> For the complete documentation index, see [llms.txt](https://docs.strongdm.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.strongdm.com/admin/deployment/integrations/gcp.md).

# GCP

The Google Cloud Platform (GCP) can host StrongDM nodes, manage secrets, and manage users. StrongDM can govern access to gcloud and many GCP resource types.

### Secrets Management

StrongDM integrates with the GCP Secret Manager to allow your nodes to proxy access to resources using secrets that are added and maintained in your cloud-native secrets manager.

{% content-ref url="/pages/VdiClAwyQVgmLxLIUQYS" %}
[GCP Secret Manager](/admin/access/secret-stores/gcp-secret-manager.md)
{% endcontent-ref %}

### Node Management

When configuring gateways or relays to proxy client traffic to resources, the GCP Nodes guide can be of use for setup.

{% content-ref url="/pages/FzqqhaWGsVcb89rI6sds" %}
[GCP Nodes](/admin/networking/gateways-and-relays/gcp-nodes.md)
{% endcontent-ref %}

### User Management

StrongDM provides an integration for SSO authentication with Google as well as user provisioning with Google.

{% content-ref url="/pages/akSxHlp9NAKBsx1IAskc" %}
[SSO With Google](/admin/principals/sso/google-oidc.md)
{% endcontent-ref %}

{% content-ref url="/pages/KWBqlSwiRqO76D8pnlI5" %}
[Provisioning With Google Cloud](/admin/principals/provisioning/google-provisioning.md)
{% endcontent-ref %}

### Resources

Additionally, StrongDM offers proxied access to cloud resources using the following resource types.

#### Cloud Resources

* **GCP (Workforce Identity Federation)** - Proxy access to manage your Google Cloud via the CLI or through the web console using Workforce Identity Federation to authenticate. See the [GCP (Workforce Identity Federation) guide](/admin/resources/clouds/gcp-wif.md) for more details.
* GCP CLI/SDK (Service Account) - Proxy access to your Google Cloud for service accounts via the CLI or SDKs. See the [GCP CLI/SDK (Service Account) guide](/admin/resources/clouds/gcp.md) for more details.
* **Google Groups** - Grant and revoke time-bound membership in Google Groups that are bound to Google Cloud IAM roles, without proxying any connection. See the [Google Groups guide](/admin/resources/clouds/google-groups.md) for more details.

#### Cluster Resources

When setting up Kubernetes, it's advisable to use a Helm chart and the Kubernetes (Pod Identity) resource type. If you're manually setting up a Kubernetes resource in the cloud, you can also use the Google-specific GKE resource type.

* [Deploy Kubernetes via the Helm chart](https://github.com/strongdm/charts/blob/main/deployments/sdm-relay/README.md)
* [Kubernetes (Pod Identity) resource guide](/admin/resources/clusters/kubernetes-podidentity.md)
* [GKE resource guide](/admin/resources/clusters/gke.md)

#### Server Resources

Any of StrongDM's SSH resource types (listed on the [Servers](/admin/resources/servers.md) page) can be used to set up AWS server instances as resources in StrongDM.

#### Datasource Resources

A variety of StrongDM's datasource resource types can be used to support Cloud SQL and other GCP resource types, depending on the database protocol used (see the Datasources list to review the available resource types), and there is also a bespoke BigQuery resource type.

* [Datasource guides](/admin/resources/datasources.md)
* [BigQuery](/admin/resources/datasources/bigquery.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.strongdm.com/admin/deployment/integrations/gcp.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.