Page tree

 

Contents:


AWS Deployment Scenarios

The following are the basic AWS deployment scenarios.

Deployment Scenario

Trifacta node installation

Base Storage LayerStorage - S3Storage - RedshiftClusterNotes

Trifacta® Wrangler Enterprise on-premises install with S3 read access

On-premisesHDFSread onlyNot supportedHadoopWhen HDFS is the base storage layer, the only accessible AWS resources is read-only access to S3.

Trifacta Wrangler Enterprise AWS install with S3 read access

EC2HDFSread onlyNot supportedHadoopWhen HDFS is the base storage layer, the only accessible AWS resources is read-only access to S3.

Trifacta Wrangler Enterprise AWS install with S3 read/write access

EC2S3read/writeread/write Hadoop or EMR  

Trifacta Data Preparation for Amazon Redshift and S3 AWS install through Amazon Marketplace

EC2S3read/writeread/write None

Trifacta Data Preparation for Amazon Redshift and S3 does not support integration with any running environment clusters. All job execution occurs on the Trifacta Server. This scenario is suitable for smaller user groups and data volumes.

Trifacta Wrangler Enterprise AWS install through Amazon Marketplace with integration to EMR cluster

EC2S3read/writeread/write EMR

This deployment scenario integrates by default with an EMR cluster.

It does not support integration with a Hadoop cluster.

Microsoft Azure     Integration with AWS-based resources is not supported. See Install from Azure Marketplace.

Legend and Notes:

ColumnNotes
Deployment ScenarioDescription of the AWS-connected deployment

Trifacta node installation

Location where the Trifacta node is installed in this scenario.

All AWS installations are installed on EC2 instances.

Base Storage Layer

When the Trifacta platform is first installed, the base storage layer must be set.

NOTE: In marketplace deployments, the base storage layer is set for you. After you have begun using the product, you cannot change the base storage layer.

NOTE: Read/write access to AWS-based resources requires that S3 be set as the base storage layer.

Storage - S3

Trifacta Wrangler Enterprise supports read access to S3 when the base storage layer is set to HDFS.

For read/write access to S3, the base storage layer must be set to S3.

Storage - RedshiftFor access to Redshift, the base storage layer must be set to S3.
Cluster

List of cluster types that are supported for integration and job execution at scale.

  • The Trifacta platform can integrate with at most one cluster. It cannot integrate with two different clusters at the same time.
  • Access to an EMR cluster requires S3 to be the base storage layer.
  • Smaller jobs can be executed on the Trifacta Server running environment, which is hosted on the Trifacta node itself.
  • For more information, see Running Environment Options.
NotesAny additional notes

AWS Installations

Trifacta Wrangler Enterprise on EC2 Instance

When the Trifacta platform is installed on AWS, it is deployed on an EC2 instance. Through the EC2 console, there are a few key parameters that must be specified. 

NOTE: After you have created the instance, you should retain the instanceId from the console, which must be applied to the configuration in the Trifacta platform.

For more information, see Install from Amazon Marketplace.

Trifacta Wrangler Enterprise on Amazon Marketplace (AMI)

Through the Amazon Marketplace, you can license and deploy an AMI of  Trifacta Data Preparation for Amazon Redshift and S3, a self-contained version of  Trifacta Wrangler Enterprise that does not require integration with a clustered running environment. All job execution happens within the AMI on the EC2 instance that you deploy. 

Trifacta Wrangler Enterprise with EMR

You can deploy an AMI of the Trifacta platform onto an EC2 instance and then integrate it with your pre-configured EMR cluster for Spark-based job execution. 

AWS Integrations

The following table describes the different AWS components that can host or integrate with the Trifacta platform. Combinations of one or more of these items constitute one of the deployment scenarios listed in the following section.

AWS ServiceDescriptionBase Storage LayerOther Required AWS Services
EC2

Amazon Elastic Compute Cloud (EC2) can be used to host the Trifacta node in a scalable cloud-based environment. The following deployments are supported:

  • Trifacta Wrangler Enterprise with or without access to an EMR cluster
  • Trifacta Data Preparation for Amazon Redshift and S3 on an AMI

Base storage layer can be S3 or HDFS.

If set to HDFS, only read access to S3 is permitted.

 
S3

Amazon Simple Storage Service (S3) can be used for reading data sources, writing job results, and hosting the Trifacta databases.

Base storage layer can be S3 or HDFS.

If set to HDFS, only read access to S3 is permitted.

 
Redshift

Amazon Redshift provides a scalable data warehouse platform, designed for big data analytics applications. The Trifacta platform can be configured to read and write from Amazon Redshift database tables.

Base Storage Layer = S3

S3
AMI

Through the Amazon Marketplace, you can license and install an Amazon Machine Image (AMI) instance of Trifacta Data Preparation for Amazon Redshift and S3. This product is intended for smaller user groups that do not need large-scale processing of Hadoop-based clusters.

Base Storage Layer = S3

NOTE: HDFS is not supported.

EC2 instance
EMRThrough the Amazon Marketplace, you can license and install an AMI specifically configured to work with Amazon Elastic Map Reduce (EMR), a Hadoop-based data processing platform.

Base Storage Layer = S3

EC2 instance, AMI

Amazon RDS

Optionally, the Trifacta databases can be installed on Amazon RDS. For more information, see Install Databases on Amazon RDS.

Base Storage Layer = S3 

This page has no comments.