This guide steps through the requirements and process for installing  through the Amazon Marketplace.

Product Limitations


This document assumes that you are setting up  to use Amazon's preferred EC2 role-based authentication for access to AWS resources. 

Tip: Using EC2 role-based authentication is recommended by AWS. For more information, see


 also supports the following authentication methods:

If you are using one of these two access methods, please do the following:

  1. Specify an EC2 role without any permissions. Specifically, it should have no data access permissions, as this role cannot be changed at a later time. 
  2. Complete the following sequence through the Install Steps. Specify the above EC2 role as part of the configuration. 
  3. When you launch the product, you can specify the appropriate access mode through the platform. For more information, see Configure for AWS in the Install Guide.
    1. This content is also available through the online Documentation referenced at the end of this document.
  4. Complete any related configuration through AWS as needed.

Tip: If you want to use EC2 roles at a later time, you can just apply AWS policies to the empty role you created here. Additional configuration is required in the platform to use this role.


Desktop Requirements

  • All desktop users of the platform must have the latest version of Google Chrome installed on their desktops.
    • Google Chrome must have the PNaCl client installed and enabled.
    • PNaCl Version:  0.50.x.y or later
  • All desktop users must be able to connect to the EC2 instance through the enterprise infrastructure.

Sizing Guide

NOTE: The following guidelines apply only to .

Use the following guidelines to select your instance size:

NOTE: enforces a maximum limit of 30 users.

Sizemax recommended users

Avg. size of jobs on (GB)

Small55 GB
Medium1520 GB
Large3040 GB


Before you install the platform, please verify that the following steps have been completed.

  1. EULA. Before you begin, please review the End-User License Agreement. See End-User License Agreement.

  2. S3 bucket. Please create an S3 bucket to store . In the bucket, the platform stores metadata in the following location:



  3. IAM policies. Create IAM policies for access to the S3 bucket. Required permissions are the following: 
    • The system account or individual user accounts must have full permissions for the S3 bucket:

      Delete*, Get*, List*, Put*, Replicate*, Restore*
    • These policies must apply to the bucket and its contents. Example:

    • See
  4. EC2 instance role. Create an EC2 instance role for this policy. See

Internet access

Install Steps

  1. Launch  from AMI.
  2. In the EC2 Console:
    1. Instance size: Select the instance size. See Sizing Guide.
    2. Network: Configure the VPC, subnet, firewall and other configuration settings necessary to communicate with the instance. 
    3. Auto-assigned Public IP: You must create a public IP to access the .
    4. EC2 role: Select the EC2 role that you created.
    5. Local storage: Select a local EBS volume. The default volume includes 100GB storage.

      NOTE: The local storage environment contains the , the product installation, and its log files. No source data is ever stored within .

    6. Security group: Use a security group that exposes access to port 3005, which is the default port for the platform. 
    7. Create an AWS key-pair for access:This key is used to provide SSH access to the platform, which may be required for some admin tasks. Save key file to your local computer for later use.
    8. Save your changes.
  3. Launch the configured version of .

    NOTE: From the EC2 Console, please acquire the instanceId, which is needed in a later step.

  4. When the instance is spinning up for the first time, performance may be slow. When the instance is up, please navigate to the following:

  5. When the login screen appears, enter the following:
    1. Username:  admin@trifacta.local
    2. Password: (the instanceId value)

      NOTE: As soon as you login as an admin for the first time, you should immediately change the password. Select the User Profile menu item in the upper-right corner. Change the password and click Save to restart the platform.

  6. From the application menu, select Settings menu > Admin Settings
  7. In the Admin Settings page, you can configure many aspects of the platform, including user management tasks, and perform restarts to apply the changes.
    1. In the Search bar, enter the following:
    2. Set the value of this setting to be the bucket that you created for .

  8. The following setting must be specified.


    You can set the above value to either of the following:

    aws.mode valueDescription
    systemSet the mode to system to enable use of EC2 instance-based authentication for access.
    userSet the mode to user to utilize user-based credentials. This mode requires additional configuration.

    Details on the above configuration are described later.

  9. Click Save.

  10. When the platform restarts, you can begin using the product.

SSH Access

If you need to SSH to the , you can use the following command:

ssh -i <path_to_key_file> <userId>@<tri_node_DNS_or_IP>

Path to the key file stored on your local computer.

<userId>The user ID is always centos.

DNS or IP address of the


Please complete the instructions in this section if you are upgrading from a previous version of 

NOTE: These instructions apply only to  available the Amazon Marketplace. If you are upgrading , please follow the upgrade instructions provided to you by your .


Backup data from platform instance

Before you begin, you should backup your current instance.

  1. SSH to your current Marketplace AMI instance. See instructions in the Install section.

  2. Stop the  on your current Marketplace AMI instance:

    sudo service trifacta stop
  3. Update the backup script with a more current version.
    1. Download 5.0.0 backup script from the following location:
    2. Example command to download the script:

      curl --output
    3. Overwrite the downloaded script to the following location:

    4. Verify that this script is executable: 

      sudo chmod 775 /opt/trifacta/bin/setup-utils/
  4. Run the backup script:

    sudo /opt/trifacta/bin/setup-utils/


    1. When the script is complete, the output identifies the location of the backup. Example:

  5. Store the backup in a safe location. If needed, you can store this backup in the S3 bucket used by the platform. Example:

    aws s3 cp /opt/trifacta-backups/trifacta-backup-4.2.1+126.20171217124021.a8ed455-20180514213601.tgz s3://<my-trifacta-s3-bucket>/trifacta-backups/

Spin up upgraded platform instance and restore data

In this section, you spin up the upgraded instance and then restore the data that you have backed up into the instance.


  1. Spin up the new instance from the Amazon Marketplace AMI. For more information on installation, please see the instructions earlier in this document.
  2. Verify that the instance has successfully started. If you can connect to the login page, the platform has started.
  3. SSH to the new Amazon Marketplace AMI instance. See previous instructions in the Install section.
  4. Stop the  on the instance:

    sudo service trifacta stop
  5. Download the restore script from the following location:
    1. Example command to download the script:

      curl --output
    2. Place the restore script in the following location in the instance:

    3. Verify that this script is executable:

      sudo chmod 775 /opt/trifacta/bin/setup-utils/
  6. Download the backup from your storage location and extract its contents. Example:

    sudo mkdir -p /root/trifacta-restore-files
    sudo cd /root/trifacta-restore-files
    sudo aws s3 cp \
      s3://<my-trifacta-s3-bucket>/trifacta-backups/trifacta-backup-4.2.1+126.20171217124021.a8ed455-20180514213601.tgz .
    sudo tar xzf trifacta-backup-4.2.1+126.20171217124021.a8ed455-20180514213601.tgz
  7. The backup contents should be located in a directory with a path similar to the following:

  8. Execute the restore script. Pass in the path to your unzipped backup as a parameter, as in the following example:

    sudo /opt/trifacta/bin/setup-utils/ \
      -r /root/trifacta-restore-files/trifacta-backup-4.2.1+126.20171217124021.a8ed455-20180514213601


The upgrade is complete. To verify:


  1. Restart the platform:

    sudo service trifacta start
  2. Run a simple job with profiling. 
  3. Verify that the job has successfully completed. 
    1. In the Jobs page, locate the job results. See Jobs Page.
    2. Click View Details next to the job to review the profile.


You can access complete product documentation online and in PDF format. From within the product, select Help menu > Product Docs.

Related Topics