# Deploying Great Expectations with Google Cloud Composer (Hosted Airflow)

**URL:** <https://discourse.greatexpectations.io/t/deploying-great-expectations-with-google-cloud-composer-hosted-airflow/379>\
**Category:** Archive\
**Tags:** airflow, how-to\
**Created:** [September 10, 2020, 6:14pm UTC](https://discourse.greatexpectations.io/t/deploying-great-expectations-with-google-cloud-composer-hosted-airflow/379 "2020-09-10T18:14:01Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![anthony](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.greatexpectations.io/anthony/32/68_2.png) [@anthony](https://discourse.greatexpectations.io/u/anthony)\
**Post date:** [September 10, 2020, 6:14pm UTC](https://discourse.greatexpectations.io/t/deploying-great-expectations-with-google-cloud-composer-hosted-airflow/379/1 "2020-09-10T18:14:01Z")

</div>

This article is for comments to: [Deploying Great Expectations with Google Cloud Composer (Hosted Airflow) — great\_expectations documentation](https://docs.greatexpectations.io/en/latest/guides/workflows_patterns/deployment_google_cloud_composer.html)  
Please comment +1 if this How-to Guide is important to you.

---

<div class="post-metadata">

**Author:** ![pedroi](https://avatars.discourse-cdn.com/v4/letter/p/839c29/32.png) [@pedroi](https://discourse.greatexpectations.io/u/pedroi)\
**Post date:** [November 18, 2020, 9:45am UTC](https://discourse.greatexpectations.io/t/deploying-great-expectations-with-google-cloud-composer-hosted-airflow/379/2 "2020-11-18T09:45:27Z")

</div>

This guide is really useful, but there is something I couldn’t find yet and it is how to pass the (service\_account) credentials for both GCS buckets and BigQuery using the airflow connections when instantiating the DataContextConfig, if that is possible at all.

---

<div class="post-metadata">

**Author:** ![eugene.mandel](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.greatexpectations.io/eugene.mandel/32/22_2.png) [@eugene.mandel](https://discourse.greatexpectations.io/u/eugene.mandel)\
**Post date:** [November 24, 2020, 10:38pm UTC](https://discourse.greatexpectations.io/t/deploying-great-expectations-with-google-cloud-composer-hosted-airflow/379/3 "2020-11-24T22:38:22Z")

</div>

Great Expectations has its own configuration of connections to GCS buckets, databases and other resources. As of now, we don’t support Airflow connections for this configuration, but will look into this and evaluate if this is helpful and feasible.

---

<div class="post-metadata">

**Author:** ![almiavicas](https://avatars.discourse-cdn.com/v4/letter/a/73ab20/32.png) [@almiavicas](https://discourse.greatexpectations.io/u/almiavicas)\
**Post date:** [July 30, 2021, 6:59pm UTC](https://discourse.greatexpectations.io/t/deploying-great-expectations-with-google-cloud-composer-hosted-airflow/379/4 "2021-07-30T18:59:56Z")

</div>

For Great Expectations Stores, Great Expectations uses the GOOGLE\_APPLICATION\_CREDENTIALS env variable. This variable should point to your GCP credentials json file. Inside Cloud Composer this variables is already set and you don’t have to worry about it.

For Bigquery Credentials it’s different. You can provide in the `connection_string` the credentials path. For example, `bigquery://<your-project>/<your-dataset>?credentials_path=<path-to-credentials>`  
That way you can tell Great Expectations where to fetch your credentials from. But I think that if you do not set this variable, GE will try to fetch your credentials from the same env variable I pointed before.