We recommend launching a Cloud SQL PostgreSQL instance for run and events data. You can configure the webserver to use Cloud SQL to run and events data by setting blocks in your $DAGSTER_HOME/dagster.yaml appropriately:
In this case, you'll want to ensure you provide the right connection strings for your Cloud SQL instance, and that the node or container hosting the webserver is able to connect to Cloud SQL.
Be sure that this file is present, and DAGSTER_HOME is set, on the node where the webserver is running.
Note that using Cloud SQL for run and event log storage does not require that the webserver be running in the cloud. If you are connecting a local webserver instance to a remote Cloud SQL storage, double check that your local node is able to connect to Cloud SQL.
You'll probably also want to configure a GCS bucket to store op outputs via persistent IO Managers. This enables reexecution, review and audit of op outputs, and cross-node cooperation (e.g., with the multiprocess_executor or celery_executor).