> For the complete documentation index, see [llms.txt](https://docs.elimity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elimity.com/reference-manual/v3.46.6/built-in-connectors/google-cloud.md).

# Google Cloud

The Google Cloud connector for Elimity Insights fetches user accounts, service accounts, roles, permissions and buckets from Google Cloud so you can keep in control of your environment. Follow the instructions below to set up the connector for your environment.

## 1. Setting up a dedicated service account in Google Cloud

As usual, we recommend creating a dedicated service account in Google Cloud:

1. In the Google Cloud console, open the navigation menu from the top-left corner, and click on the 'IAM & Admin > Service accounts' item.
2. Create a new service account by pressing the 'CREATE SERVICE ACCOUNT' button at the top of the page.
3. Provide a descriptive name (e.g. `elimity-insights`) and generate or choose a unique identifier for the service account.
4. Press 'CREATE AND CONTINUE'.
5. Grant the service account read rights to all information in the project by granting it the role 'Security Reviewer'.
6. Press 'CONTINUE' and skip the last optional step by pressing 'DONE'.

Note down the unique identifier of your Google Cloud project for later use. You can find it by opening the project selector in the top-left corner of your console.

## 2. Generating a key for the service account

Having created a dedicated service account, we now need to generate a private key for it:

1. Open the menu in the 'Actions' column for the newly created service account, and click on the 'Manage keys' item.
2. Click the 'ADD KEY' button and select 'Create new key'.
3. Ensure the key type is 'JSON' and press the 'CREATE' button.

Securely store the downloaded private key for later use.

## 3. Creating a source in Elimity Insights

In Elimity Insights you can now create a new Google Cloud source providing the following configuration options:

<table data-full-width="true"><thead><tr><th>Configuration option</th><th>Description</th></tr></thead><tbody><tr><td>Credentials JSON</td><td>Private key you generated in step 2.</td></tr><tr><td>Project ID</td><td>Project identifier you noted down in step 1.</td></tr></tbody></table>


---

# 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.elimity.com/reference-manual/v3.46.6/built-in-connectors/google-cloud.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.