Scenario Description

CloudFormation templates enable you to install with a minimal amount of effort.


Install

The CloudFormation template creates a complete working instance of , including the following:


Pre-requisites

If you are integrating the with an EMR cluster, you must acquire a license first. Additional configuration is required. For more information, please contact aws-marketplace@trifacta.com.

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 https://docs.trifacta.com/display/PUB/End-User+License+Agreement+-+Trifacta+Wrangler+Enterprise.

  3. If you have not done so already, please acquire a  from your .

Internet access

SELinux

By default,  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 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  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 , to open websockets:

      setsebool -P httpd_can_network_connect 1


Product Limitations

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

Install Steps - CloudFormation Template


Steps:

 

  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 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 and the EMR cluster instances.

    4. Allowed HTTP Source: This range of addresses are permitted access to the on port 80, 443, and 3005.

      1. Port numbers 80 and 443 do not have any services by default, but you may modify the to enable access via these ports.

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

    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.

    ParameterDescriptionUse

    URL and port number to which to connect to the

    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.

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

    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 has been created, you must add a license file before starting the . 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:

      sudo su



    3. Add your license:

      /opt/trifacta/license/license.json


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

    5. Verify permissions on the file:

      chown trifacta:trifacta /opt/trifacta/license/license.json
      chmod 644 /opt/trifacta/license/license.json


  9. Start the :

    service trifacta start


  10. It may take some time for the server to finish coming online. Navigate to the .
  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 and EMR content. Search for:

    "aws.s3.bucket.name"

     

    1. Update the value with the 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:

    "spark.version"

     

    1. Update its value to 2.3.0, if necessary.

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


  17. "webapp.runinEMR"

     

    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. Verify that there are no extra spaces in any copied value.
    2. AWS Region: Enter the region where your EMR cluster is located.
    3. Resource Bucket: you may use the already created .
      1. Verify that there are no extra spaces in any copied value.
    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.

Verify

Start and Stop the Platform

Verify Operations

Upgrade

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

Documentation

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 .

Related Topics