Page tree

 

Contents:


This guide steps through the requirements and process for installing  Trifacta® Data Preparation for Amazon Redshift and S3 through the AWS Marketplace.

Product Limitations

  • Connectivity to sources other than S3 and Redshift is not supported.
  • Jobs must be executed in the Trifacta Photon running environment. No other running environment integrations are supported.
  • Anomaly and stratified sampling are not supported in this deployment.
  • When publishing single files to S3, you cannot apply an append publishing action.
  • Trifacta Data Preparation for Amazon Redshift and S3 must be deployed into an existing Virtual Private Cloud (VPC). 

  • The EC2 instance, S3 buckets, and any connected Redshift databases must be located in the same Amazon region. Cross-region integrations are not supported at this time.

    NOTE: HDFS integration is not supported for Amazon Marketplace installations.

  • The S3 bucket automatically created by the Marketplace CloudFormation template is not automatically deleted when you delete the stack in CloudFormation. You must empty the bucket and delete it, which can be done through the AWS Console.

Internet access

From AWS, the Trifacta platform requires Internet access for the following services:

NOTE: Depending on your AWS deployment, some of these services may not be required.

 

  • AWS S3
  • Key Management System [KMS] (if sse-kms server side encryption is enabled)
  • Secure Token Service [STS] (if temporary credential provider is used)
  • EMR (if integration with EMR cluster is enabled)

NOTE: If the Trifacta platform is hosted in a VPC where Internet access is restricted, access to S3, KMS and STS services must be provided by creating a VPC endpoint. If the platform is accessing an EMR cluster, a proxy server can be configured to provide access to the AWS ElasticMapReduce regional endpoint.

SELinux

By default,  Trifacta Data Preparation for Amazon Redshift and S3 is installed on a server with SELinux enabled. Security-enhanced Linux (SELinux) provides a set of security features for, among other things, managing access controls. 

Tip: The following may be applied to other deployments of the Trifacta platform on servers where SELinux has been enabled.

 

In some cases, SELinux can interfere with normal operations of platform software. If you are experiencing connectivity problems related to SELinux, you can do either one of the following:

  1. Disable SELinux on the server. For more information, please see the CentOS documentation.
  2. Apply the following commands on the server, as root:
    1. Open ports on the server for listening. 
      1. By default, the Trifacta application listens on port 3005. The following opens that port when SELinux is enabled:

        semanage port -a -t http_port_t -p tcp 3005
      2. Repeat the above step for any other ports that you wish to open on the server.
    2. Permit nginx, the proxy on the Trifacta node, to open websockets:

      setsebool -P httpd_can_network_connect 1

Install

Desktop Requirements

  • All desktop users of the platform must have the latest version of Google Chrome installed on their desktops.
  • All desktop users must be able to connect to the EC2 instance over the port on which Trifacta Data Preparation for Amazon Redshift and S3 is listening. Default is 3005.

NOTE: Trifacta Data Preparation for Amazon Redshift and S3 enforces a maximum limit of 30 users.

Pre-requisites

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. SSH Key-pair. Please verify that there is an SSH key pair available to assign to the Trifacta node.

Install Steps - CloudFormation template

This install process creates the following:

  • Trifacta node on an EC2 instance
  • An S3 bucket to store data
  • IAM roles and policies to access the S3 bucket from the Trifacta node.

Steps:

  1. In the Marketplace listing, click Deploy into an existing VPC.
  2. Select Template: The template path is automatically populated for you.
  3. Specify Details:
    1. Stack Name: Display name of the application

      NOTE: Each instance of the Trifacta platform should have a separate name.

    2. Instance Type: Only one instance type is enabled.

    3. Key Pair: Select the SSH pair to use for Trifacta Instance access.

    4. Allowed HTTP Source: Please specify the IP address or range of address from which HTTP/HTTPS connections to the application are permitted.

    5. Allowed SSH Source: Please specify the IP address or range of address from which SSH connections to the EC2 instance are permitted.

  4. Options: None of these is required for installation. Specify your options as needed for your environment.
  5. Review: Review your installation and configured options.
    1. Select the checkbox at the end of the page.
    2. To launch the configured instance, click Create.
  6. In the Stacks list, select the name of your application. Click the Outputs tab and collect the following information. Instructions in how to use this information is provided later.
    1. No outputs appear until the stack has been created successfully.

       

      ParameterDescriptionUse
      TrifactaUrl value

      URL and port number to which to connect to the Trifacta application

      Users must connect to this IP address and port number to access.
      TrifactaBucketThe address of the default S3 bucketThis value must be applied through the application.
      TrifactaInstanceIdThe identifier for the instance of the platform

      This value is the default password for the admin account.

      NOTE: This password must be changed immediately.

  7. When the instance is spinning up for the first time, performance may be slow. When the instance is up, please navigate to the TrifactaUrl location:

    http://<public_hostname>:3005
  8. When the login screen appears, enter the following:
    1. Username: admin@trifacta.local
    2. Password: (the TrifactaInstanceId value)

      NOTE: As soon as you login as an admin for the first time, you should change the password.

  9. From the application menu, select the Settings menu. Then, click Settings > Admin Settings
  10. 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:

      aws.s3.bucket.name
    2. Set the value of this setting to be the TrifactaBucket value that you collected from the Outputs tab.

  11. Click Save.

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

SSH Access

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

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

Path to the key file stored on your local computer.

<userId>The user ID is always centos.
<tri_node_DNS_or_IP>

DNS or IP address of the Trifacta node

Upgrade

For more information, see Upgrade for AWS Marketplace.

Documentation

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

This page has no comments.