This install process applies to installing  on an AWS infrastructure that you manage. 

AWS Marketplace deployments:

NOTE: Content in this section does not apply to deployments from the AWS Marketplace. For more information on installing from the Marketplace, see the AWS Marketplace listing.


Scenario Description

NOTE: All hardware in use for supporting the platform is maintained within your enterprise infrastructure on AWS.

  • Installation of  on an EC2 server in AWS
  • Installation of  on AWS
  • Integration with a supported EMR cluster.
  • Base storage layer and backend datastore of S3

For more information on deployment scenarios, see Supported Deployment Scenarios for AWS.

Limitations

Deployment Limitations

The following limitations apply to installations of  on AWS:

  • 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.
  • The following limitations apply to EMR integration only:
    • No support for Hive integration
    • No support for secure impersonation or Kerberos

Product Limitations

For general limitations of , see Product Limitations in the Planning Guide.

Pre-requisites

Please acquire the following assets:

  • Install Package: Acquire the installation package for your operating system.
    • License Key: As part of the installation package, you should receive a license key file. See License Key for details.
    • For more information, contact .
  • Offline system dependencies: If you are completing the installation without Internet access, you must also acquire the offline versions of the system dependencies. See Install Dependencies without Internet Access.

AWS desktop requirements

  • All desktop users must be able to connect to the EC2 instance through the enterprise infrastructure.

AWS pre-requisites

Depending on which of the following AWS components you are deploying, additional pre-requisites and limitations may apply. Please review these sections as well.

Preparation

Before you install on AWS, please verify that you have completed the following:

  1. Read: Please read this entire document before you create the EMR cluster or install the .
  2. VPC: Enable and deploy a working AWS VPC.
    1. In your VPC. you must define a subnet where you plan to deploy the .

  3. S3: Enable and deploy an AWS S3 bucket to use as the base storage layer for the platform. In the bucket, the platform stores metadata in the following location:

    <S3_bucket_name>/trifacta

    See https://s3.console.aws.amazon.com/s3/home.

  4. 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:

      "arn:aws:s3:::my-trifacta-bucket-name"
"arn:aws:s3:::my-trifacta-bucket-name/*"
    • See https://console.aws.amazon.com/iam/home#/policies
  5. EC2 instance role: Create an EC2 instance role for your S3 bucket policy. See https://console.aws.amazon.com/iam/home#/roles.
  6. EC2 instance: Deploy an AWS EC2 with SELinux where the  can be installed.

    1. The required set of ports must be enabled for listening. See System Ports in the Planning Guide.

    2. This node should be dedicated for .

      NOTE: The EC2 node must meet the system requirements for installing the platform. For more information, see System Requirements in the Planning Guide.

  7. EMR cluster: An existing EMR cluster is required. 

    1. Cluster sizing: Before you begin, you should allocate sufficient resources for sizing the cluster. For guidance, please contact your .

    2. See Deploy the Cluster below.
  8. Databases: 
    1. The platform utilizes a set of databases that must be accessed from the . Databases are installed as part of the workflow described later.
    2. If installing databases on Amazon RDS, an admin account to RDS is required. For more information, see Install Databases on Amazon RDS.

AWS Information

Before you begin installation, please acquire the following information from AWS:

  • EMR:
    • AWS region for the EMR cluster, if it exists.
    • ID for EMR cluster, if it exists
      • If you are creating an EMR cluster as part of this process, please retain the ID.
      • The EMR cluster must allow access from the . This configuration is described later.
  • Subnet: Subnet within your virtual private cloud (VPC) where you want to launch the .
    • This subnet should be in the same VPC as the EMR cluster.
    • Subnet can be private or public.
    • If it is private and it cannot access the Internet, additional configuration is required. See below.
  • S3:
    • Name of the S3 bucket that the platform can use

    • Path to resources on the S3 bucket

  • EC2: 
    • Instance type for the 

Internet access

Deploy the Cluster

In your AWS infrastructure, you must deploy a supported version of EMR across a recommended number of nodes to support the expected data volumes of your .

NOTE: Cluster information including cluster configuration files must be accessible to the . These requirements are described below.

Deploy the EC2 Node

An EC2 node of the cluster must be deployed to host the  software. Here are some guidelines for deploying the EC2 cluster from the EC2 cluster:

  1. Instance size: Select the instance size.
  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 the product.

  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.

  8. Save your changes.

Install Workflow

NOTE: These steps are covered in greater detail later in this section.

Next Steps

To continue, please install the  on the .

NOTE: Please complete the installation steps for the operating system version that is installed on the .

See Install Software.