# How to host Data Docs on GCS?

**URL:** <https://discourse.greatexpectations.io/t/how-to-host-data-docs-on-gcs/107>\
**Category:** Archive\
**Created:** [May 5, 2020, 11:35pm UTC](https://discourse.greatexpectations.io/t/how-to-host-data-docs-on-gcs/107 "2020-05-05T23:35:43Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![aylr](https://avatars.discourse-cdn.com/v4/letter/a/8797f3/32.png) [@aylr](https://discourse.greatexpectations.io/u/aylr)\
**Post date:** [May 5, 2020, 11:35pm UTC](https://discourse.greatexpectations.io/t/how-to-host-data-docs-on-gcs/107/1 "2020-05-05T23:35:43Z")

</div>

I’m trying to setup GCS-hosting for datadocs. I know there’s a tutorial for AWS. I saw GCS support mentioned a few times in the docs, but couldn’t find a tutorial. Could anyone point me towards a good place to start?

---

<div class="post-metadata">

**Author:** ![aylr](https://avatars.discourse-cdn.com/v4/letter/a/8797f3/32.png) [@aylr](https://discourse.greatexpectations.io/u/aylr)\
**Post date:** [May 6, 2020, 4:43pm UTC](https://discourse.greatexpectations.io/t/how-to-host-data-docs-on-gcs/107/2 "2020-05-06T16:43:05Z")

</div>

A few things:

1. You’ll need credentials configured correctly

2. You’ll need to configure a data docs site as follows in your great\_expectations.yml:

3. You’ll then probably run into this bug that I’m fixing now: [https://github.com/great-expectations/great\_expectations/issues/1393](https://github.com/great-expectations/great_expectations/issues/1393)

4. Then you may notice that some of the links between data docs pages don’t work. I will file this and begin work on these bugs as well.

5. Once these bugs are worked out I plan on making a “how to” guide in our official docs.

---

<div class="post-metadata">

**Author:** ![anordin](https://avatars.discourse-cdn.com/v4/letter/a/a5b964/32.png) [@anordin](https://discourse.greatexpectations.io/u/anordin)\
**Post date:** [May 6, 2020, 5:34pm UTC](https://discourse.greatexpectations.io/t/how-to-host-data-docs-on-gcs/107/3 "2020-05-06T17:34:25Z")

</div>

> [@aylr](#):
>
> - You’ll need credentials configured correctly

How did you configure credentials?

I presume via `gcloud auth` on the command line. I’m not sure how permissions are typically saved in GE, but GCS commonly relies on service accounts that you can authenticate as JSON key files. Service accounts in GCS are specially made accounts designated for programmatic usage of a specific task.

---

<div class="post-metadata">

**Author:** ![aylr](https://avatars.discourse-cdn.com/v4/letter/a/8797f3/32.png) [@aylr](https://discourse.greatexpectations.io/u/aylr)\
**Post date:** [May 7, 2020, 12:15am UTC](https://discourse.greatexpectations.io/t/how-to-host-data-docs-on-gcs/107/4 "2020-05-07T00:15:33Z")

</div>

So, the nice thing about GE in this case is that it doesn’t even know about your credentials - it uses the `google-cloud` library service accounts. You might need to create a service account, download the key, and set the environment variable like this:

```auto
 export GOOGLE_APPLICATION_CREDENTIALS=path/to/sevice-account-key-sdfjwefsdf.json

```

---

<div class="post-metadata">

**Author:** ![aylr](https://avatars.discourse-cdn.com/v4/letter/a/8797f3/32.png) [@aylr](https://discourse.greatexpectations.io/u/aylr)\
**Post date:** [May 7, 2020, 12:16am UTC](https://discourse.greatexpectations.io/t/how-to-host-data-docs-on-gcs/107/5 "2020-05-07T00:16:07Z")

</div>

Side note. The first bug is fixed and merged, and a colleague has fixes for the other bugs I’m hoping to ship tomorrow!

---

<div class="post-metadata">

**Author:** ![aylr](https://avatars.discourse-cdn.com/v4/letter/a/8797f3/32.png) [@aylr](https://discourse.greatexpectations.io/u/aylr)\
**Post date:** [May 7, 2020, 4:39pm UTC](https://discourse.greatexpectations.io/t/how-to-host-data-docs-on-gcs/107/6 "2020-05-07T16:39:48Z")

</div>

Alright I have some good news! In the upcoming 0.10.9 release which is shipping this morning GCS data docs is verified working with a small caveat!

The caveat is that if you have a `prefix` configured your site will not have the correct urls so until this bug is fixed you will need to operate with a `prefix: ""`: [https://github.com/great-expectations/great\_expectations/issues/1398](https://github.com/great-expectations/great_expectations/issues/1398)

---

<div class="post-metadata">

**Author:** ![ayirpsc](https://avatars.discourse-cdn.com/v4/letter/a/e274bd/32.png) [@ayirpsc](https://discourse.greatexpectations.io/u/ayirpsc)\
**Post date:** [May 15, 2020, 2:20pm UTC](https://discourse.greatexpectations.io/t/how-to-host-data-docs-on-gcs/107/7 "2020-05-15T14:20:03Z")

</div>

0.10.11 also has related fixes.