> For the complete documentation index, see [llms.txt](https://docs.shadow.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shadow.xyz/integrations/gcs-s3.md).

# GCS / S3

Set up a fully managed data pipeline to export data to a GCS / S3 bucket in a one-off or recurring fashion.

{% hint style="info" %}
The GCS / S3 integration is included on paid [Shadow Fork plans](https://www.shadow.xyz/pricing).
{% endhint %}

The GCS / S3 integration is available for [One-off Exports](/getting-data/one-off-exports.md) and [Recurring Exports](/getting-data/recurring-exports.md). It's ideal for teams who need historical blockchain data for analytics or research use cases that don’t require real-time data freshness. Data exports to GCS / S3 offer the highest flexibility, allowing you to upload data into tools that you already use such as Snowflake, Metabase, etc.

When you set up a data export to GCS / S3, you’ll be able to specify:

1. Which contracts and events to export
2. The file format (CSV or Parquet)
3. How often you want the data delivered to your bucket (daily, hourly, every 15 min)
4. How to partition the data (daily, hourly, or no partitioning)

<figure><img src="https://4112099338-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FS7wZ4G2hJbxyJhrQE8Kz%2Fuploads%2Frj8u3HyFPSMvLsMf9IOo%2FScreenshot%202024-09-23%20at%204.09.41%E2%80%AFPM.png?alt=media&amp;token=193aeb06-da64-4f96-a428-be764625be07" alt=""><figcaption></figcaption></figure>

See the [One-off Exports](/getting-data/one-off-exports.md) or [Recurring Exports](/getting-data/recurring-exports.md) pages for additional information.


---

# 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.shadow.xyz/integrations/gcs-s3.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.