# Google Cloud Storage

**URL:** <https://forum.tiledb.com/t/google-cloud-storage/24>\
**Category:** Uncategorized\
**Created:** [November 4, 2018, 8:27pm UTC](https://forum.tiledb.com/t/google-cloud-storage/24 "2018-11-04T20:27:29Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![tino](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.tiledb.com/tino/32/11_2.png) [@tino](https://forum.tiledb.com/u/tino)\
**Post date:** [November 4, 2018, 8:27pm UTC](https://forum.tiledb.com/t/google-cloud-storage/24/1 "2018-11-04T20:27:30Z")

</div>

Any idea when to expect this?

Context: I’m looking to move a process that does DEM processing over to Google Cloud Functions. Storing the DEM in TileDB sounds like a really great idea 😄

---

<div class="post-metadata">

**Author:** ![stavros](https://avatars.discourse-cdn.com/v4/letter/s/51bf81/32.png) [@stavros](https://forum.tiledb.com/u/stavros)\
**Post date:** [November 5, 2018, 3:23pm UTC](https://forum.tiledb.com/t/google-cloud-storage/24/2 "2018-11-05T15:23:03Z")

</div>

Hi there, thanks for reaching out! This is in our TODO list. We are aiming for early 2019.

---

<div class="post-metadata">

**Author:** ![rabernat](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.tiledb.com/rabernat/32/35_2.png) [@rabernat](https://forum.tiledb.com/u/rabernat)\
**Post date:** [April 15, 2019, 7:49pm UTC](https://forum.tiledb.com/t/google-cloud-storage/24/3 "2019-04-15T19:49:00Z")

</div>

👍 to this. We would really need GCS support in order to try out tiledb in Pangeo.

---

<div class="post-metadata">

**Author:** ![jakebolewski](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.tiledb.com/jakebolewski/32/28_2.png) [@jakebolewski](https://forum.tiledb.com/u/jakebolewski)\
**Post date:** [April 15, 2019, 9:39pm UTC](https://forum.tiledb.com/t/google-cloud-storage/24/4 "2019-04-15T21:39:29Z")

</div>

Untested, but Google provides S3 API compatibility so the following _may_ work just through setting the the `vfs.s3.endpoint`, `vfs.s3.region` configs: [https://cloud.google.com/storage/docs/migrating](https://cloud.google.com/storage/docs/migrating) (simple migration).

---

<div class="post-metadata">

**Author:** ![ihnorton](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.tiledb.com/ihnorton/32/23_2.png) [@ihnorton](https://forum.tiledb.com/u/ihnorton)\
**Post date:** [April 16, 2019, 4:33pm UTC](https://forum.tiledb.com/t/google-cloud-storage/24/5 "2019-04-16T16:33:02Z")

</div>

I tested this, and it does work for read/list/etc. Unfortunately, it doesn’t work for writes because we use the multi-part upload API, which GCS S3 emulation does not support.

---

<div class="post-metadata">

**Author:** ![ihnorton](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.tiledb.com/ihnorton/32/23_2.png) [@ihnorton](https://forum.tiledb.com/u/ihnorton)\
**Post date:** [May 1, 2019, 2:36pm UTC](https://forum.tiledb.com/t/google-cloud-storage/24/6 "2019-05-01T14:36:11Z")

</div>

Hi @tino, @rabernat, we’ve added experimental support for GCS by providing a configuration mode that disables the S3 multi-part upload API and uses a single `PUT` instead:

> <https://github.com/TileDB-Inc/TileDB/pull/1219>

This requires using the bucket in [S3 compatibility mode](https://cloud.google.com/storage/docs/interoperability).