Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space DEV and version next


D s install marketplace

Scenario Description

Using CloudFormation will allow you to get Trifacta up and running with a minimal amount of effort. Additional customizations can be done after the install is done by tweaking the resources that were created by the CloudFormation process. If you have additional requirements or a complicated environment please contact Trifacta Sales so we can help you design a solution that will fit your environment.

Please note that you will need a license for Trifacta before you start the service.


The CloudFormation template will create a complete working instance of Trifacta including

  • VPC and all required networking infrastructure
  • EC2 instance with all supporting policies/roles
  • S3 bucket
  • EMR cluster
    • Configurable autoscaling instance groups
    • All supporting policies/roles



If you are integrating the

D s platform
with an EMR cluster, you must acquire a license first. Additional configuration is required. For more information, please contact

Before you begin:

  1. Read: Please read this entire document before you begin.

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

  3. D s item
    itemlicense file
    If you have not done so already, please acquire a 
    D s item
    itemlicense file
     from your 
    D s item

Internet access

D excerpt include
pageConfigure for AWS


By default, 

D s product
 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

D s 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 

        D s webapp
         listens on port 3005. The following opens that port when SELinux is enabled:

        Code Block
        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 

      D s item
      , to open websockets:

      Code Block
      setsebool -P httpd_can_network_connect 1

Product Limitations

  • 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.
  • No support for Hive integration
  • No support for secure impersonation or Kerberos
  • No support for high availability and failover
  • Job cancellation is not supported on EMR.
  • When publishing single files to S3, you cannot apply an append publishing action.



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 through the enterprise infrastructure.

Install Steps - CloudFormation Template



  1. In the Marketplace listing, click Deploy into a new VPC.
  2. Choose a Template: The template path is automatically populated for you.
  3. Specify Details:
    1. Stack Name: Display name of the stack is used in the names of resources created by the stack and as an identifier for the stack.


      NOTE: Each instance of the

      D s platform
      must have a separate name.

    2. Instance Type: Please select the appropriate instance depending on the number of users and data volumes of your environment. For more information, see the Sizing Guide above.

    3. Key Pair: This SSH key pair is used to access the

      D s item
      and the EMR cluster instances.

    4. Allowed HTTP Source: This range of addresses are permitted access to the

      D s item
      on port 80, 443, and 3005.

      1. Port numbers 80 and 443 do not have any services by default, but you may modify the

        D s item
        to enable access via these ports.

    5. Allowed SSH Source: This range of addresses is permitted access to port 22 on the

      D s item

    6. EMR Cluster Node Configuration: Allows you to customize the configuration of the deployed EMR nodes
      1. Reasonable values are used as defaults.
      2. If you do customize these values, you should upsize. Avoid downsizing these values.
    7. EMR Cluster Autoscaling Configuration: Allows you to customize the autoscaling settings used by the EMR cluster.
      1. Reasonable values are used as defaults.
  4. Options: None of these is required for installation. Specify any 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 stack, click Create.
  6. Please wait while the stack creates all required resources.
  7. In the Stacks list, select the name of your application. Click the Outputs tab and collect the following information. Instructions on how to use this information are provided later.


    D s item
    itemURL value

    URL and port number to which to connect to the

    D s item

    Users must connect to this IP address and port number to access. By default, it is set to 3005. The access port can be moved to 80 or 443 if desired. Please contact us for more details.

    D s item

    The address of the default S3 bucketThis value must be applied through the application after it has been deployed.

    D s item
    itemInstance Id

    The identifier for the instance of the platform

    This value is the default password for the admin account.


    NOTE: You must change this password on the first login to the application.

  8. After the

    D s item
    has been created, you must add a license file before starting the
    D s item
    . Here we will SSH into the server and create the license file and paste the license file content in, plus update the ownership and permissions of that file:

    1. SSH into the server as the centos user and using the key you specified.

    2. Change to root user:

      Code Block
      sudo su

    3. Add your license by creating the following file.

      Code Block
    4. Into the above file, paste the contents of the license.json file that was provided to you by your

      D s item

    5. Verify permissions on the file:

      Code Block
      chown trifacta:trifacta /opt/trifacta/license/license.json
      chmod 644 /opt/trifacta/license/license.json
  9. Start the

    D s item

    Code Block
    service trifacta start
  10. It may take some time for the server to finish coming online. Navigate to the
    D s webapp
  11. When the login screen appears, enter the following:
    1. Username: admin@trifacta.local
    2. Password: (the TrifactaInstanceId value)


      NOTE: After you login as an admin for the first time, you must change the password.

  12. From the application menu, select the Settings menu. Then, click Settings >Admin Settings
  13. In the Admin Settings page, you can configure many aspects of the platform, including user management tasks, and perform restarts to apply the changes.

  14. Add the S3 bucket that was automatically created to store

    D s item
    and EMR content. Search for:

    Code Block


    1. Update the value with the
      D s item
      itemBucket value
      provided when you created the stack in AWS.
  15. Verify your Spark version. If the cluster was launched from AWS, this value should be set to 2.3.0. Search for:

    Code Block


    1. Update its value to 2.3.0, if necessary.

  16. Enable the "Run in EMR" option within the platform. Search for:

  17. Code Block


    1. Select the checkbox to enable it.
  18. Click Save underneath the Platform Settings section.

  19. In the Admin Settings page, locate the External Service Settings section.

    1. AWS EMR Cluster ID: Paste the value for the EMR Cluster ID for the cluster to which the platform is connecting.

      1. Make sure to remove any extra spaces that may have been copied
    2. AWS Region: Enter the region where your EMR cluster is located.
    3. Resource Bucket: you may use the already created
      D s item
      1. Make sure to remove any extra spaces that may have been copied
    4. Resource Path: you should use something like EMRLOGS.
  20. Click Save underneath the External Service Settings section.

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

Note about deleting the CloudFormation stack


If you must delete the CloudFormation stack, please be aware of the following.

  1. The S3 bucket that was created for the stack is not removed. If you want to delete it, you must empty it first and then delete it.
  2. Any EMR security groups created for the stack cannot be deleted, due to circular references. The stack deletion process informs you of the security groups that it failed to delete. To complete the deletion:
    1. Remove all rules from the security groups.
    2. Delete the security groups manually.
    3. Re-run the stack deletion, which should complete successfully.


Start and Stop the Platform

D excerpt include
pageInstall Start Platform

Verify Operations

D excerpt include
pageInstall Verify


For more information, see Upgrade for AWS Marketplace with EMR.


You can access complete product documentation in online and PDF format. After the platform has been installed, select Help menu > Product Docs from the menu in the 

D s webapp


Related Topics

D s also