Documentation Index

Fetch the complete documentation index at: https://kb.vastdata.com/llms.txt

Use this file to discover all available pages before exploring further.

Provisioning Source Views for Element Type Triggers

  • Updated on Aug 7, 2026
  • Published on Aug 5, 2026
  • 2 minute(s) read
Prev Next

Overview

In order to enable DataEngine users to create element type triggers, which watch for events related to elements in a source view, you must provision source views for these triggers.

Application users cannot create source views. This must be done in VMS by a manager user (a tenant admin or cluster admin user).

Supported Types of Source Views

Each element trigger is configured with one of the following source types:

  • S3. Watches a source view for events related to creation and deletion of S3 objects or S3 object tags.

  • NFS. Watches a source view for events related to creation and deletion of NFSv4 files.

Configuration Requirements per Source Type

Source views must meet the following configuration requirements:

  • S3:

    • The view must have the S3 Bucket protocol enabled.

    • The view policy must have S3 Native security flavor.

  • NFS:

    • The view must have both S3 Bucket and NFSv4 protocols enabled.

    • The view policy can have Mixed Last Wins, S3 Native, or NFS security flavor.

    • NFSv4 file delegations, which may be subject to inherited tenant-level policy, must be disabled for the view.

Creating Source Views

To create a source view, follow the instructions for creating a view and configure the view according to the following settings:

VAST Web UI Field Name

Requirement

Path

Specify the path in the tenant's Element Store.

Create directory

Enable this.

Policy name

Select or create a view policy on the same tenant with the correct security flavor:

  • For S3 source type, S3 Native security flavor.

  • For NFS source type, NFS, Mixed Last Wins, or S3 Native security flavor.

To ensure that all application users can access the bucket, add the same user group that you are using to provision application users to the S3 bucket listing permission field in the policy configuration.

Protocols

  • For S3 source type, select S3 Bucket.

  • For NFS source type, select S3 Bucket and NFSv4.

S3 bucket name

Enter a name for the bucket.

Bucket Owner

Provide a user belonging to the tenant's DataEngine user group with permission to create buckets, such as created in when you enabled DataEngine. Click to enter the name and start typing and then select a name from the list.

Access Delegation Policy

This is important and relevant only for the source view for triggers with NFS source type.

Source views for NFS type element triggers must have NFSv4 file delegations disabled on the view. Action may be needed or not, depending on the tenant-level policy:

  • It is possible that the tenant-level policy blocks the ability to enable delegations on any view on the tenant. This would be indicated under Access Delegation Policy. In this case, there is no action to take.

  • It is possible that the tenant-level policy allows you to enable delegations but does not enable them by default. This would be indicated under Access Delegation Policy. In this case, you also need not take any action.

  • It is possible that the tenant-level policy enables read and/or write delegations by default on all views. If this is the case, under Access Delegation Policy, deselect any selected checkboxes for read and/or write delegations to make sure that they are disabled on the view.