> For the complete documentation index, see [llms.txt](https://docs.e6data.com/product-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.e6data.com/product-documentation/setup/gcp-setup/configure-gcs-access-for-serverless-compute-gcp.md).

# Configure GCS Access for Serverless Compute (GCP)

**Overview**

To analyze your data using e6data’s serverless platform, you'll need to grant **read-only** access to your Google Cloud Storage (GCS) buckets. This guide walks you through the recommended configuration, ensuring secure and minimal access aligned with best practices.

### Security: Principle of Least Privilege

E6Data strictly adheres to the **principle of least privilege**. This means:

* **Read-only access** via Storage Object Viewer role
* **No permission to write, delete, or modify** your data
* **Bucket-specific access is supported and preferred**
* **No admin or bucket configuration permissions**

This ensures your data remains secure while allowing e6data to analyze it.

-> [Prerequisties](/product-documentation/setup/gcp-setup/configure-gcs-access-for-serverless-compute-gcp/prerequisites.md)

->[ FAQ's and Troubleshooting](/product-documentation/setup/gcp-setup/configure-gcs-access-for-serverless-compute-gcp/faqs-and-troubleshooting.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.e6data.com/product-documentation/setup/gcp-setup/configure-gcs-access-for-serverless-compute-gcp.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.