Checking the Storage Array Requirements for HyperScale Flex

To ensure compatibility and optimal performance with HyperScale Flex, verify that the connected storage arrays meet the minimum supported software and API versions.

Note

If you use an existing user for the HyperScale Flex installation, the same username is used for both the storage pool and S3 storage.

Review the minimum required software version, API version, and product type for the supported storage vendors: Pure Storage and VAST Data.

Pure Storage

  • Vendor: Pure

  • Product Type: FlashBlade

  • Minimum Software Version: 4.5.3

  • Minimum API Version: 2.16

  • Minimum User Permissions/Roles: S3 Superuser

VAST Data

  • Vendor: VAST Data

  • Product Type: VAST Cluster

  • Minimum Software Version: 5.1.0

  • Minimum API Version: v5

  • Minimum User Permissions/Roles: S3 Superuser

Default Tenant Requirement for VAST

The default tenant on the VAST array must be present before starting the HSFlex installation (FR40). The installation process uses the default tenant during setup, and the installation fails if the default tenant does not exist. Therefore, the default tenant is a mandatory prerequisite.

On VAST, a tenant is a logical container used to isolate S3 resources such as:

  • Buckets
  • Users
  • Access keys
  • Policies

The default tenant is a system-created tenant that ensures the S3 service functions even when no custom tenants are configured. If S3 users or buckets are created without explicitly selecting a tenant, they are typically created under the default tenant.

Prerequisites for First-Time VAST Configuration

If you are configuring the VAST array for the first time, complete the following steps before starting the HSFlex installation:

  1. Create a tenant (if you plan to use a custom tenant).
  2. Configure DNS.
  3. Configure the S3 endpoint (if not already configured).

These steps must be completed in advance.

Steps Automatically Performed by HSFlex Installation

During the HSFlex installation, the following tasks are automatically handled by the installer:

  • Create user
  • Create S3 policy
  • Attach policy to user
  • Generate access keys
  • Create bucket
  • Validate access

You do not need to manually perform these steps as part of the HSFlex installation process.

Impact if the Default Tenant Is Missing

If the default tenant is deleted or does not exist:

  • S3 operations may fail if clients or tools assume the default tenant exists.
  • Integrations or scripts that do not explicitly specify a tenant may fail authentication.
  • Errors may occur during:
  • Bucket creation
  • User or access key creation
  • S3 access from tools that expect a default tenant

To avoid installation failures and authentication issues, do not delete the default tenant, even if you primarily use custom tenants.

×

Loading...