Deploying Polaris on Cloud Providers on Apache Polaris

Deploying Polaris on Amazon Web Services (AWS)

Mon, 01 Jan 0001 00:00:00 +0000

Build and launch Polaris using the AWS Startup Script at the location provided in the command below. This script will start an Amazon RDS 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:

There must be at least two subnets created in the VPC and region in which your EC2 instance reside. The span of subnets MUST include at least 2 availability zones (AZs) within the same region.
Your EC2 instance must be enabled with IMDSv1 or IMDSv2 with 2+ hop limit.
The AWS identity that you will use to run this script must have the following AWS permissions:
- “ec2:DescribeInstances”
- “rds:CreateDBInstance”
- “rds:DescribeDBInstances”
- “rds:CreateDBSubnetGroup”
- “sts:AssumeRole” on the same role as the Instance Profile role of the EC2 instance on which you are running this script. Additionally, you should ensure that the Instance Profile contains a trust policy that allows the role to trust itself to be assumed.

1export ASSETS_PATH=$(pwd)/getting-started/assets/
2export CLIENT_ID=root
3export CLIENT_SECRET=s3cr3t
4export POSTGRES_PASSWORD=your_secure_password # Optional: If not set, a random password will be generated
5./getting-started/assets/cloud_providers/deploy-aws.sh

Environment Variables🔗

The deployment script accepts the following environment variables:

Deploying Polaris on Azure

Mon, 01 Jan 0001 00:00:00 +0000

Build and launch Polaris using the Azure Startup Script at the location provided in the command below. This script will start an Azure Database for PostgreSQL - Flexible Server 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:

Deploying Polaris on Google Cloud Platform (GCP)

Mon, 01 Jan 0001 00:00:00 +0000

Build and launch Polaris using the GCP 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.

1export ASSETS_PATH=$(pwd)/getting-started/assets/
2export CLIENT_ID=root
3export CLIENT_SECRET=s3cr3t
4export POSTGRES_PASSWORD=your_secure_password # Optional: If not set, a random password will be generated
5./getting-started/assets/cloud_providers/deploy-gcp.sh

Environment Variables🔗

The deployment script accepts the following environment variables: