mc qos rule remove

The mc qos rule remove command removes one or more Quality of Service (QoS) rules from an AIStor deployment.

The command can also be invoked with the short name rm.

For more information, see Bucket-level Quality of Service.

Syntax

Parameters

TARGET

Required

The The alias and bucket from which to remove QoS rules.

For example:

mc qos rule remove myaistor/mybucket --id "rule1"

--all

Optional

Remove all QoS rules from the deployment.

Must be used with the --force flag.

For example:

mc qos rule remove myaistor/mybucket --all --force

--api

Optional

Remove all QoS rules for the specified API operation.

This parameter can be combined with --id to remove a specific rule for a specific API.

For example:

mc qos rule remove myaistor/mybucket --api "s3.ListObjectsV2"

--force

Optional

Force the removal of all QoS rules.

Must be used with the --all flag.

The --all --force option removes all QoS rules from the bucket. This action cannot be undone.

--id

Optional

The identifier of the QoS rule to remove.

This parameter can be combined with --api to remove a specific rule for a specific API.

For example:

mc qos rule remove myaistor/mybucket --id "rule1"
Duplicate ID values
If you provide duplicate ID values, mc qos rule remove --id "DUPLICATED_VALUE" deletes all rules with the same ID.

Global flags

This command supports any of the global flags.

Example

Remove a specific rule by ID and API

The following command removes the QoS rule with ID rule2 for the s3.ListObjectsV2 API:

mc qos rule remove myaistor/mybucket --id "rule2" --api "s3.ListObjectsV2"

Behavior

Required parameters

You must specify one of the following:

  • --id to remove a specific rule
  • --api to remove all rules for an API
  • --id and --api together to remove a specific rule for an API
  • --all and --force together to remove all rules

S3 compatibility

The mc commandline tool is built for compatibility with the AWS S3 API and is tested with AIStor and AWS S3 for expected functionality and behavior.

MinIO provides no guarantees for other S3-compatible services, as their S3 API implementation is unknown and therefore unsupported.

While mc commands may work as documented, any such usage is at your own risk.

Permissions

You must have appropriate permissions on the deployment to remove QoS rules.