View Source

When you sign up to use , you are provided a default storage environment which you can use to immediately get started using the product. A storage environment is used to store your data assets.

supports multiple storage environments, one of which is the default one. The default storage environment provides all of the storage capabilities of other storage environment, as well as storage for data assets generated by use of the product. In the following table, you can see the types of data assets that are stored in each type of storage environment:

Asset Type	Description	Default Storage	Non-Default Storage
imported datasets	When you upload data to the product, it is stored in the default storage environment. From these uploaded assets, you create imported datasets, which are sources of data for your transformation recipes. You can also import data that is stored in other storage environments.	Yes	Yes
job results	When you run a job to transform your data, the results of the job execution are stored in a storage environment.	Yes	Yes
samples	When you create transformation recipes, you are working on a sample of the source data. When you first open a recipe, an initial sample of the recipe is created for you and stored on the default storage environment. As needed, you can start a job to create a new sample of your data. Ad-hoc samples are also stored on the default storage environment. For more information, see Overview of Sampling.	Yes	No
temporary files	During ingestion of data and job execution, requires storage space in the default storage environment to store temporary files.	Yes	No

For more information on these asset types, see Glossary.

Storage Environment Options

You can use either of the following storage environments as the default or secondary storage environment.

At startup

When the product is first launched, is the default storage environment. You must configure access to your S3 buckets and assets.
S3 connectivity is enabled.

Storage options

One of the following must be set as the default storage environment.

Tip: You can switch between and S3 as your default storage environment at any time without disruption to service or loss of data.

Storage Environment

Description

Short for , this S3-backed storage environment is managed by and requires no additional configuration to manage. It is available as soon as your launch the product for the first time. Details are below.

When is first launched, is defined as the default storage environment. This storage environment provides storage for the above data asset types. is backed by AWS S3 buckets hosted by and secured by IAM policies.

Using is very similar to navigating S3 buckets to find and select assets to import or to locate job results that you have published. For more information, see Using TFS.

S3

Your S3 buckets and their assets.

NOTE: To access your S3 assets, you must provide authentication credentials, policies, and other configuration information to the . Additional information is provided below.

See Using S3.

Configure Storage

By default:

and S3 are both enabled.
is configured as the base storage environment.

Required information for S3

If you are enabling access to S3, you must choose the method of access and acquire information from your S3 administrator to insert into the application to enable access.

Tip: The following section should be shared with your S3 administrator, who can provide the required information.

For more information, see Enable Access to S3 and AWS Resources.

Set Default Storage Environment

You can configure S3 to be the default storage environment, instead of .

NOTE: If you are switching the default storage environment, any data that was written to another default storage environment is still available through the application, as long as you do not disable access to the storage environment. There should be no interruption of service or loss of access to your data.

NOTE: Before you begin, you should verify that you have the appropriate credentials to access S3.

Please complete the following.

Steps:

Locate the following setting and set it to your preferred storage environment:
Default storage environment

The selected environment is now used for storing the asset types listed above. The other storage environment type can be disabled if preferred. See below.

Disable S3

By default, S3 is enabled for access as a storage environment. If needed, you can disable access to S3 when is the default storage environment.

Tip: You can add still use S3 as a secondary storage environment.

NOTE: If S3 has been enabled previously, all access to assets stored on S3 is cut off for the .

To disable S3 access, please complete the following.

Steps:

Login as a workspace administrator.
Locate the following setting and set it to Enabled:
Trifacta File System
Set the following to :
Default storage environment
Locate the following setting and set it to Disabled:
Enable S3 connectivity
Access to S3 is closed. is used as the default storage environment.

Disable

If you wish to disable all access to , please do the following.

Tip: You can add still use as a secondary storage environment.

NOTE: If has been enabled previously, all access to assets stored on is cut off for the .

Steps:

Login as a workspace administrator.
Locate the following setting and set it to Enabled:
Enable S3 connectivity
Set the following to S3:
Default storage environment
Locate the following setting and set it to Disabled:
Trifacta File System
Access to S3 is closed. is used as the default storage environment.

Configure Access to S3

NOTE: Before you complete these steps, please verify that an S3 administrator has provided the required information. See Enable Access to S3 and AWS Resources.

Configure access mode

To enable access to AWS and S3 settings, you must decide your access mode:

Workspace mode: All workspace users use the same credentials to access S3.
- Pro: Easy to set up.
- Con: All users have access to the same resources.
User mode: All workspace users must configure individual credentials to access S3.
- Pro: Finer-grained security.
- Con: Requires configuration for each workspace user.

Steps:

Login as a workspace administrator.
In the , select User menu > Admin console > AWS Settings.
For Mode, select your preferred access mode:
1. All users in the workspace share the same AWS credentials: workspace mode
2. Each user in the workspace can use their own AWS credentials: user mode
For Authentication Method, you must determine your choice:
NOTE: The authentication method requires information from S3. Specific requirements and configuration are covered in later steps.
1. Use a cross-account role (IAM role): An IAM role is an AWS object that contains policies defining permissions and access level to AWS and S3 resources. This object must be created by an AWS or S3 administrator. This method of access is recommended.
2. Use access keys: These key-secret combinations can be used to provide access to S3 buckets.

Configure access by mode

Workspace mode

Continue completing the specification listed in the above page.

For more information, see AWS Settings Page.

Tip: You can also perform this configuration by creating an Amazon S3 connection in the Import Data Page. This connection creates the global connection to S3 for all workspace users. See Amazon S3 Connections.

User mode

If you have enabled per-user access to the workspace:

Workspace administrators who have chosen to use IAM roles must ensure that any IAM role includes the proper trust relationship for the . For more information, see Insert Trust Relationship in AWS IAM Role.
Workspace users must configure their access.
1. For more information on configuring access, see Configure Your Access to S3.
2. Individual users can also configure directories to use in their S3 bucket for storing assets. See Storage Config Page.