This section applies to getting started with 

• D s product
  product awspr

• D s product
  product awsst

   

This section provides an overview of how to get started using the product. 

1. Administrators should complete the first section to set up the product for use. 
2. After set up is complete, individual users should complete the second section to get started using the product.

Setup Process

Steps:

1. Before you begin. If you are using your own AWS S3 buckets, you should prepare them and their access policies to ensure that 

   D s product
   product aws

    can integrate with them. 

   Info
   NOTE: If you do not have these AWS resources, they can be created for you. Details are below.

   1. Technical setup: Please share the technical setup section with your S3 administrator.
2. Register. Complete the simple online workflow to license and create your 

   D s product
   product aws

    workspace.
3. Workspace setup. Before you invite other users to your workspace, you should complete a few setup steps.
4. Invite users. If you intend to share the workspace with other users, you can invite them from within it. 
5. Wrangle away! 

Before You Begin

Hosted on Amazon Web Services, 

AWS Overview

Below are the AWS objects that are required for setup. 

Technical Setup

The following sections should be provided to your AWS administrator for setting up access to these resources, if required.

Create policy to grant access to S3 bucket

To use your own S3 bucket(s) with 

• For more information on creating policies, see https://console.aws.amazon.com/iam/home#/policies.

Below is an example policy template. You should use this template to create the policy.

Template Notes:

1. One of the statements grants access to the trifacta-public-datasets bucket, which contains resources used for the onboarding tour.  
2. Replace <my_default_S3_bucket> with the name of your default S3 bucket.
3. To grant access to multiple buckets within your account, you can extend the resources list to accommodate the additional buckets.

Policy Template

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "VisualEditor0",
            "Effect": "Allow",
            "Action": [
                "s3:PutObject",
                "s3:GetObject",
                "s3:ListBucket",
                "s3:DeleteObject",
                "s3:GetBucketLocation"
            ],
            "Resource": [
                "arn:aws:s3:::<my_default_S3_bucket>",
                "arn:aws:s3:::<my_default_S3_bucket>/*"
            ]
        },
        {
            "Sid": "VisualEditor1",
            "Effect": "Allow",
            "Action": [
                "s3:GetObject",
                "s3:ListBucket"
            ],
            "Resource": [
                "arn:aws:s3:::trifacta-public-datasets",
                "arn:aws:s3:::trifacta-public-datasets/*"
            ]
        }
    ]
}

Update policy to accommodate SSE-KMS if necessary

If any accessible bucket is encrypted with SSE-KMS, another policy must be deployed. See https://docs.aws.amazon.com/kms/latest/developerguide/iam-policies.html.

Add policy for Redshift access

If you are connecting to Redshift databases through your workspace, you can enable access by creating a GetClusterCredentials policy. This policy is additive to the the S3 access policies. All of these policies can be captured in a single IAM role. 

Example:

{
"Version": "2012-10-17",
  "Statement": [
    {
     "Sid": "GetClusterCredsStatement",
      "Effect": "Allow",
      "Action": [
        "redshift:GetClusterCredentials"
      ],
      "Resource": [
        "arn:aws:redshift:us-west-2:123456789012:dbuser:examplecluster/${redshift:DbUser}",
        "arn:aws:redshift:us-west-2:123456789012:dbname:examplecluster/testdb",
        "arn:aws:redshift:us-west-2:123456789012:dbgroup:examplecluster/common_group"
      ],
        "Condition": {
            "StringEquals": {
           "aws:userid":"AIDIODR4TAW7CSEXAMPLE:${redshift:DbUser}@yourdomain.com"
                            }
                      }
    },
  }
}

For more information on these permissions, see Required AWS Account Permissions.

Whitelist the IP address range of the 

D s item
item Service

, if necessary

If you are enabling any relational source, including Redshift, you must whitelist the IP address range of the 

35.245.35.240/28

For Redshift:

For Redshift, there are two ways to whitelist the IP range depending on if you are using EC2-VPC or EC2-Classic (not common).

• EC2-VPC (Security group): Add the IP address range to the inbound rule for the security group associated with the cluster. For more information, see https://docs.aws.amazon.com/redshift/latest/gsg/rs-gsg-authorize-cluster-access.html#rs-gsg-how-to-authorize-access-vpc-security-group.
• EC2-Classic: Add the IP address range to the inbound rule for the security group associated with the EC2 instance. For more information, see https://docs.aws.amazon.com/redshift/latest/gsg/rs-gsg-authorize-cluster-access.html#rs-gsg-how-to-authorize-access-cluster-security-group.

For details on this process with RDS in general, see https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Overview.RDSSecurityGroups.html

For more information, please contact 

Register for 

D s product
product aws

To begin the registration process, please visit https://www.trifacta.com/start-wrangling.

Workspace Setup

After you have completed registration, please login to the application.

Review Workspace Settings

As the first registered user, you are assigned the workspace admin role, which provides control over workspace-level settings. Before you invite members to the workspace, you should review and modify the basic configuration for the workspace. See Workspace Settings Page.

Verify Operations

Invite Members

1. You can invite other people to join your workspace. 
   1. When members initially join your workspace, they are assigned a non-admin role. Through the Workspace Members page, you can assign roles.
   2. For more information, see Workspace Users Page.
2. The workspace administrators must provide credentials for each workspace member account. See Workspace Users Page.

Getting Started for Workspace Members

This section walks through the process of getting started as a new member of a

Steps:

1. You should have received an email like the following:
   
   
   

   D caption
   Welcome email

2. Click the link. If you see a Missing Storage Settings error message, then you must provide your individual user storage credentials and default bucket. To do so, click the Here link.
3. In your Storage Settings page, you may be required to enter your S3 credentials. After the credentials have been entered, you can begin using the product. 
4. Access documentation: To access the full customer documentation, from the left nav bar, select Help menu > Documentation.

The following resources can assist workspace members in getting started with wrangling.

• If product walkthroughs have been enabled, each new member can step through an onboarding tour of the product after first login. 

• For an overview of the product, see Product Overview.
• Check out the 

  D s item
  item Community

  : https://community.trifacta.com
• Try the free Wrangler certification course. See https://community.trifacta.com/s/academywelcome.
• For a basic summary of each step of the wrangling process, see Workflow Basics.