---
title: "Creating a QoS Policy"
slug: "creating-a-qos-policy"
tags: ["5.4"]
updated: 2026-10-28T01:53:34Z
published: 2026-10-28T01:53:34Z
canonical: "docs.vastdata.com/creating-a-qos-policy"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vastdata.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Creating a QoS Policy

- [Creating a QoS Policy in VAST Web UI](/docs-5-4/docs/en/creating-a-qos-policy#creating-a-qos-policy-invast-web-ui)
- [Creating a QoS Policy in VAST CLI](/docs-5-4/docs/en/creating-a-qos-policy#creating-a-qos-policy-invast-cli)

## Creating a QoS Policy in VAST Web UI

1. From the left navigation menu, select Element Store and then QoS Policies.
2. Click Create QoS Policy to open the Add QoS Policy dialog.
3. In the General tab:

  - Enter a name for the QoS policy in the Name field.
  - Select the QoS policy type:

    - If you are going to create a QoS policy for views, choose View and proceed to [step 4](/docs-5-4/docs/en/creating-a-qos-policy).
    - If you are creating a QoS policy for users, choose User and proceed to [step 5](/docs-5-4/docs/en/creating-a-qos-policy).

Depending on your choice, either View or User tab is now available, where you can make further settings.
4. To create a QoS policy for a view, complete the fields in the View tab:

  - Select a tenant in the Tenant field to associate the QoS policy with a tenant.
  - (For view QoS policies only) If you want to [prioritize](/docs-5-4/docs/en/qos-overview#prioritizing-workloads) the workloads served under this QoS policy, set the Prioritize policy over cluster or tenant limitations flag.
  - In Limit QoS by, leave Read/Write (default) to be able to set different QoS limits per operation type (one for reads and another for writes), or select Total if you want to set QoS limits that cap the total amount of read, write and metadata operations.
  - Under Static Limits, specify [static QoS limits](/docs-5-4/docs/en/qos-overview) per view.QoS Overview

For each of the limits , '0' means no limit is set.

    - Select an appropriate unit of measurement in the Units field.
    - To restrict the bandwidth, fill in the fields following the BW column:

      - Max. The maximum allowed bandwidth.
      - Burst. The maximum [burst](/docs-5-4/docs/en/qos-overview) bandwidth that can be provided while there are accumulated bandwidth credits.QoS Overview
      - Credit. The maximum amount of bandwidth [credits](/docs-5-4/docs/en/qos-overview) that can be accumulated.QoS Overview
    - To restrict the amount of IOPS, fill in the fields following the IOPS column:

      - Max. The maximum allowed IOPS.
      - Burst. The maximum [burst](/docs-5-4/docs/en/qos-overview) IOPS that can be provided while there are accumulated IOPS credits.QoS Overview
      - Credit. The maximum amount of IOPS [credits](/docs-5-4/docs/en/qos-overview) that can be accumulated.QoS Overview

> [!NOTE]
> **Note**
> 
> If no credits are explicitly defined, setting a maximum static limit will cause the corresponding credits to accept a default value. The credit default value will be the maximum limit multiplied by 4.
  - Under Capacity Limits, specify [capacity-based QoS limits](/docs-5-4/docs/en/qos-overview) per unit of used or provisioned logical capacity. QoS Overview

    - Choose whether you want to limit Used Capacity or Provisioned Capacity.

> [!NOTE]
> **Note**
> 
> Leaving the default value of None means no capacity-based limits are used.
    - Enter the limits in the fields below.

For each of the limits , '0' means no limit is set.

      - Read BW per GB. Maximum read bandwidth (in MB/s) to provision per GB of used or provisioned logical capacity.
      - Read IOPS per GB. Maximum read IOPS to provision per GB of used or provisioned logical capacity.
      - Write BW per GB. Maximum write bandwidth (in MB/s) to provision per GB of used or provisioned logical logical capacity.
      - Write IOPS per GB. Maximum write IOPS to provision per GB of used or provisioned logical capacity.
5. To create a QoS policy for one or more users, complete the fields in the User tab:

  - Determine the scope of the user QoS policy:

    - Set Use as default QoS policy if you want the policy to apply to all users under the tenant specified in the Tenant field.
    - Select Users or IAM Roles to attach the policy to individual users or IAM roles. In the pane that opens:

      1. Select a tenant in the Tenant field.
      2. In the User or IAM Role field, choose User or IAM Role.
      3. Start typing a user name in the Select users or Select IAM roles field to look up and auto-populate users or IAM roles. Select an entry in the dropdown and click Add User or Add Role to add the entry to the list of users below.
  - Under Static Performance Limits, specify [static QoS limits](/docs-5-4/docs/en/qos-overview) for user(s): QoS Overview

    - Select an appropriate unit of measurement in the Units field,
    - Enter the limits in the fields below.

For each of the limits , '0' means no limit is set.

      - To restrict the bandwidth, fill in the fields following the BW column, separately for Read and Write operations:

        - Max. The maximum allowed bandwidth.
        - Burst. The maximum [burst](/docs-5-4/docs/en/qos-overview) bandwidth that can be provided while there are accumulated bandwidth credits.QoS Overview
        - Credit. The maximum amount of bandwidth [credits](/docs-5-4/docs/en/qos-overview) that can be accumulated.QoS Overview
      - To restrict the amount of IOPS, fill in the fields following the IOPS column, separately for Read and Write operations:

        - Max. The maximum allowed IOPS.
        - Burst. The maximum [burst](/docs-5-4/docs/en/qos-overview) IOPS that can be provided while there are accumulated IOPS credits.QoS Overview
        - Credit. The maximum amount of IOPS [credits](/docs-5-4/docs/en/qos-overview) that can be accumulated.QoS Overview
      - Under ​**S3 Client Connections Limits**​​, optionally set the ​[overall limit on S3 connections for the user](/docs-5-4/docs/qos-overview#s3-connection-limit)​​. This limit restricts the total number of S3 connections that can be opened by the user to the VAST cluster (across all CNodes).
        - To set the limit, click **​Set Manually**​​ and enter the maximum allowed number of S3 connections to the cluster in the field provided.
        - If you do not want to set the limit, use the default of ​**Unlimited**​​.
      - Under ​**S3 Client Connections Limit per CNode**​​, optionally set the [​CNode percentage limit on S3 connections for the user](/docs-5-4/docs/qos-overview#s3-connection-limit)​​. This limit restricts the amount of CNode connection capacity that the user is allowed to consume, for any CNode in the cluster. **NOTE**: The CNode percentage limit can be set with VAST Cluster 5.4.6 and later.
        - To set the limit, click ​**Set Manually**​​ and enter the maximum allowed percentage of the CNode connection capacity in the field provided.
        - If you do not want to set the limit, use the default of ​**Unlimited**​​.
6. Click Create.

The QoS policy is created and can be assigned to views or users respectively.

## Creating a QoS Policy in VAST CLI

To create a view QoS policy:

- Run the `qospolicy create` command with `--policy-type VIEW`.

To create a user QoS policy:

1. Run the `qospolicy create` command with `--policy-type USER`.
2. Run the `qospolicy attach-user` command for the newly created QoS policy.