This install process applies to installing Trifacta® Self-Managed Enterprise Edition 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.
High availability deployments on AWS:
Installation on AWS for high availability utilizes an image-based deployment method. These instructions do not apply.
For more information, see Install for High Availability on AWS.
NOTE: All hardware in use for supporting the platform is maintained within your enterprise infrastructure on AWS.
- Installation of Trifacta Self-Managed Enterprise Edition on an EC2 server in AWS
- Installation of Trifacta databases 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.
The following limitations apply to installations of Trifacta Self-Managed Enterprise Edition on AWS:
- When publishing single files to S3, you cannot apply an
- The following limitations apply to EMR integration only:
- No support for Hive integration
- No support for secure impersonation or Kerberos
For general limitations of Trifacta Self-Managed Enterprise Edition, see Product Limitations in the Planning Guide.
Please acquire the following assets:
- Install Package: Acquire the installation package for your operating system.
- 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.
Depending on which of the following AWS components you are deploying, additional pre-requisites and limitations may apply. Please review these sections as well.
- Configure for EMR in the Configuration Guide
- Enable S3 Access in the Configuration Guide
- Create Redshift Connections in the Configuration Guide
Before you install Trifacta Self-Managed Enterprise Edition on AWS, please verify that you have completed the following:
- Read: Please read this entire document before you create the EMR cluster or install the Trifacta platform.
- VPC: Enable and deploy a working AWS VPC.
- In your VPC. you must define a subnet where you plan to deploy the Trifacta node.
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:
- 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:
These policies must apply to the bucket and its contents. Example:
- See https://console.aws.amazon.com/iam/home#/policies
- EC2 instance role: Create an EC2 instance role for your S3 bucket policy. See https://console.aws.amazon.com/iam/home#/roles.
- EC2 instance: Deploy an AWS EC2 with SELinux where the Trifacta software can be installed.
- EMR cluster: An existing EMR cluster is required.
Cluster sizing: Before you begin, you should allocate sufficient resources for sizing the cluster. For guidance, please contact your Trifacta representative.
- See Deploy the Cluster below.
The platform utilizes a set of databases that must be accessed from the Trifacta node. Databases are installed as part of the workflow described later.
NOTE: If installing databases on Amazon RDS, an admin account to RDS is required. For more information, see Install Databases on Amazon RDS.
Before you begin installation, please acquire the following information from AWS:
- 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 Trifacta node. This configuration is described later.
- Subnet: Subnet within your virtual private cloud (VPC) where you want to launch the Trifacta platform.
- 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.
- Name of the S3 bucket that the platform can use
Path to resources on the S3 bucket
- Instance type for the Trifacta node
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.
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 Trifacta jobs.
- For more information on the supported EMR distributions, see Supported Deployment Scenarios for AWS.
- For more information on suggested sizing, see Sizing Guidelines in the Planning Guide.
NOTE: Cluster information including cluster configuration files must be accessible to the Trifacta node. These requirements are described below.
Deploy the EC2 Node
An EC2 node of the cluster must be deployed to host the Trifacta platform software. Here are some guidelines for deploying the EC2 cluster from the EC2 cluster:
- Instance size: Select the instance size.
- Network: Configure the VPC, subnet, firewall and other configuration settings necessary to communicate with the instance.
- Auto-assigned Public IP: You must create a public IP to access the Trifacta platform.
- EC2 role: Select the EC2 role that you created.
Local storage: Select a local EBS volume. The default volume includes 100GB storage.
NOTE: The local storage environment contains the Trifacta databases, the product installation, and its log files. No source data is ever stored within the product.
- Security group: Use a security group that exposes access to port 3005, which is the default port for the platform.
- 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 your changes.
NOTE: These steps are covered in greater detail later in this section.
The installation and configuration process requires the following steps. To continue, see Next Steps below.
Install software: Install the Trifacta platform software on the Trifacta node. See Install Software.
Install databases: The platform requires several databases for storage.
NOTE: The default configuration assumes that you are installing the databases on a PostgreSQL server on the same edge node as the software using the default ports. If you are changing the default configuration, additional configuration is required as part of this installation process.
For more information, see Install Databases in the Databases Guide.
- Start the platform: For more information, see Start and Stop the Platform.
- Login to the application: After software and databases are installed, you can login to the application to complete configuration:
- See Login.
As soon as you login, you should change the password on the admin account. In the left nav bar, select User menu > Admin console > Admin settings. Scroll down to Manage Users. For more information, see Change Admin Password in the Configuration Guide.
Tip: At this point, you can access the online documentation through the application. In the left nav bar, select Help menu > Documentation. All of the following content, plus updates, is available online. See Documentation below.
- Install configuration: After you are able to successfully login to the Trifacta application, you must configure the product to work with your backend storage layer and the running environment on the cluster. See Install Configuration.
To continue, please install the Trifacta software on the Trifacta node.
NOTE: Please complete the installation steps for the operating system version that is installed on the Trifacta node.
See Install Software.
This page has no comments.