Managing S3 Request-Initiated Bucket Creation

When a bucket is created via an S3 API request, a view is created for the bucket. That view is manageable via VMS.

Views that are created this way are configured based on an S3 Endpoint-enabled view. S3 Endpoint can be selected as a protocol when creating a view. An S3 Endpoint view acts as a template for creating a view on a bucket. The S3 Endpoint view provides the view policy and the Element Store path under which the bucket is created.

You can create multiple S3 Endpoint views and use them to manage the path placement of new buckets in the Element Store.

S3 Endpoint views specify bucket creator users and groups. When a user creates a bucket by S3 API request, the view is created using an S3 Endpoint view that specifies the user as a bucket creator or specifies a group to which the user belongs as a bucket creator group.

If the requesting user is not specified in any S3 Endpoint view as a bucket creator, the bucket is placed directly under the root path, '/' of the Element Store and configured with a default view policy called S3_default_policy.

There is a cluster setting that enables you to restrict bucket creation via S3 API requests to S3 Endpoint views. The setting is called S3 Force Endpoint Bucket Creation. If you enable this setting, requests to create buckets fail if the user is not specified as a bucket owner for an S3 Endpoint-view.  

It is possible to enable NFSv3, NFSv4.1 and SMB protocols on the same view as S3 Endpoint protocol. The NFS and SMB protocols are then able to access the Element Store path into which the buckets are placed.

To create an S3 Endpoint view, follow the VAST Web UI or VAST CLI procedure in Creating Views to create a view and choose the following configurations: