Remove an existing set of configurations for an OIDC provider. Example and syntax Example The following example removes the oidc-config settings for the myaistor deployment.

The mc idp ldap policy entities command displays a list of mappings for a user, group, and/or policy. Syntax EXAMPLE The following example lists all mappings for a specific policy, a set of groups, and a selection of users on the myaistor deployment.

The mc idp openid enable command starts using an existing set of configurations for an OIDC provider with your AIStor deployment. Example and syntax Example The following example enables the server configurations defined as test_config on the myaistor deployment.

The mc idp ldap rm command removes an AD/LDAP IDP server configuration from an AIStor deployment. Syntax Example The following example removes the default AD/LDAP configuration for the myaistor deployment.

The mc version suspend command disables versioning on the specified bucket. Syntax Example The following command disables versioning for the mybucket bucket on the myaistor AIStor deployment:

The mc retention clear command removes the Write-Once Read-Many (WORM) locking settings for an object or object(s) in a bucket. You can also remove the default object lock settings for a bucket. To change the retention status of an object under legal hold, use mc legalhold clear. Syntax Example The following command removes the default object lock configuration for the mydata bucket on the myaistor AIStor deployment:

The mc replicate update command modifies an existing bucket replication rule. Syntax Example The following command modifies an existing replication rule for the mydata bucket on the myaistor AIStor deployment:

AIStor Key Manager supports installation on Linux hosts running AMD64 or ARM64 architectures. This procedure downloads and installs the Key Manager onto a single host machine. You can then expand the cluster with additional nodes to increase availability and resiliency. For production environments, ensure a minimum of 3 key manager hosts. Procedure The commands in this procedure may require sudo permissions to succeed depending on the level of access you have when accessing the host machine. If you do not have sudo or similar permissions, contact your systems administrator for assistance with completing the steps in this procedure.

Entrust KeyControl is a proprietary KMS which KES supports using for storing secrets. K E S C l i e n t K E S S e r v e r E n t r u s t K e y C o n t r o l Prerequisites This procedure was written and tested against Entrust KeyControl v10.1. The provided instructions may work against other KeyControl versions. This procedure assumes you have prior experience with Entrust products and have followed their documentation, best practices, and other published materials in deploying the KeyControl service.

The mc ilm tier add command creates a new remote storage tier to a supported storage services. See Object Transition for a complete list. Syntax Example The following example creates a new remote tier called WARM-MINIO-TIER on the myaistor deployment. The command creates a tier for a remote AIStor deployment located at the hostname https://warm-minio.example.com.