D toc |
---|
As needed, the
D s item | ||||
---|---|---|---|---|
|
Limitations
- SSL connectivity is not supported.
Pre-requisites
Info | |
---|---|
NOTE: You can use the suggested defaults below for sizing your RDS instance.If you have questions or concerns about sizing recommendations, please contact
|
- Admin access to an Amazon RDS account
Initialize RDS instance
Steps:
In your RDS dashboard, click Launch a DB instance.
Info NOTE: The RDS instance must be launched in the same Amazon region as the
.D s item item node - For Select Engine: Select PostgresSQL.
- For Production?: Choose Yes if you are deploying the database for a production instance of the
. Otherwise, select No.D s platform - DB Engine:
postgres
For the DB details, see below:
Info NOTE: Except as noted below, properties should be specified according to your enterprise requirements.
Instance Specifications:
- License Model:
postresql-license
- DB Engine Version: For more information on the supported versions of PostgreSQL, see System Requirements.
Allocated Storage: at least
10 GB
- License Model:
For Advanced Settings, please apply the following settings:
Network and Security:
VPC security group must allow for access from the
.D s platform
Database Options:
Database Name:
trifacta
Database Port:
5432
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
D s platform |
---|
Please complete the following steps to integrate the
D s platform |
---|
Steps:
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:
Edit
.D s triconf path true 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
Steps:
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
:D s triconf Info NOTE: This script must be run as the root user or via sudo superuser.
Code Block /opt/trifacta/bin/setup-utils/db/trifacta-create-postgres-roles-dbs.sh
- 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.
Logging
- 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
logs are available here.D s item item database