As needed, the Trifacta® databases can be installed as PostgreSQL DBs on Amazon RDS. Amazon Relational Database Service (Amazon RDS) makes it easy to set up, operate, and scale a relational database in the cloud.
- SSL connectivity is not supported.
NOTE: You can use the suggested defaults below for sizing your RDS instance. If you have questions or concerns about sizing recommendations, please contact Alteryx Support.
- Admin access to an Amazon RDS account
Initialize RDS instance
In your RDS dashboard, click Launch a DB instance.
NOTE: The RDS instance must be launched in the same Amazon region as the Trifacta node.
- For Select Engine: Select PostgresSQL.
- For Production?: Choose Yes if you are deploying the database for a production instance of the Designer Cloud powered by Trifacta platform . Otherwise, select No.
- DB Engine:
For the DB details, see below:
NOTE: Except as noted below, properties should be specified according to your enterprise requirements.
- License Model:
- DB Engine Version: For more information on the supported versions of PostgreSQL, see System Requirements.
Allocated Storage: at least
- License Model:
For Advanced Settings, please apply the following settings:
Network and Security:
VPC security group must allow for access from the Designer Cloud powered by Trifacta platform .
The port number can be changed as needed. See System Ports.
Populate other properties according to your enterprise requirements.
To complete the set up click Launch DB Instance.
Configure the Designer Cloud powered by Trifacta platform for RDS
Please complete the following steps to integrate the Designer Cloud powered by Trifacta platform with the DB instance you just created.
In the RDS console, you must find the Public DNS endpoint for the RDS instance you created:
Under Instances, expand the name of the instance you created.
The DNS endpoint should be listed under the name in the Endpoint section.
Set the host for each database to the Public DNS endpoint for the RDS instance:
Database Property Main database webapp.db.host Jobs database batch-job-runner.db.host Scheduling database scheduling-service.database.host Time-based Trigger database time-based-trigger-service.database.host
To set custom database names, usernames, and passwords:
For each database below, you can review the database name, username, and password.
Database Property Main database webapp.db.name webapp.db.username webapp.db.password Jobs database batch-job-runner.db.name batch-job-runner.db.username batch-job-runner.db.password Scheduling database scheduling-service.database.name scheduling-service.database.user scheduling-service.database.password Time-Based Trigger database time-based-trigger-service.database.name time-based-trigger-service.database.user time-based-trigger-service.database.password
- Make changes in the file as needed and save.
Install the Databases
Run the following script, which builds the four databases and specifies the appropriate roles for each database, based on the parameters you have specified in
NOTE: This script must be run as the root user or via sudo superuser.
- Login to the application.
- Create a flow and import a dataset into it. If you are able to wrangle the dataset, the integration is working.
- To review database logs in RDS, locate the Instance details page in the RDS console.
- Click Recent Events and Logs.
- If your account has the appropriate permissions, all Trifacta database logs are available here.
This page has no comments.