Deploying Polaris on Google Cloud Platform (GCP)

Build and launch Polaris using the AWS Startup Script at the location provided in the command below. This script will start a Cloud SQL for PostgreSQL instance, which will be used as the backend Postgres instance holding all Polaris data. Additionally, Polaris will be bootstrapped to use this database and Docker containers will be spun up for Spark SQL and Trino.

The requirements to run the script below are:

  • Install the gcloud CLI, if it is not already installed on the GCP VM. Instructions to download the gcloud CLI can be found here.
  • Ensure the Cloud SQL Admin API has been enabled in your project and that your VM’s Principal has access to the correct role: roles/cloudsql.admin.
  • Ensure the VM’s Principal has access to at least Read-only scope on Compute Engine: compute.readonly.
chmod +x getting-started/assets/cloud_providers/deploy-gcp.sh
export ASSETS_PATH=$(pwd)/getting-started/assets/
export CLIENT_ID=root
export CLIENT_SECRET=s3cr3t
./getting-started/assets/cloud_providers/deploy-gcp.sh

Next Steps

Congrats, you now have a running instance of Polaris! For further information regarding how to use Polaris, check out the Using Polaris page.

Cleanup Instructions

To shut down the Polaris server, run the following commands:

export ASSETS_PATH=$(pwd)/getting-started/assets/
docker compose -p polaris -f getting-started/eclipselink/docker-compose.yml down

To deploy Polaris in a production setting, please review further recommendations at the Configuring Polaris for Production page.