Deploying Polaris on Amazon Web Services (AWS)

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.
• 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”

chmod +x getting-started/assets/cloud_providers/deploy-aws.sh
./getting-started/assets/cloud_providers/deploy-aws.sh

Also, set the following static credentials for interacting with the Polaris server in the following exercises:

export CLIENT_ID=root
export CLIENT_SECRET=s3cr3t

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

docker compose -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.