This tutorial explains how to setup a KES Server to use Azure Key Vault as the persistent key store: K E S C l i e n t K E S S e r v e r A z u r e K e y V a u l t Azure Key Vault Azure Key Vault is a managed KMS service that provides a secret store that can be used by KES.

AWS Secrets Manager works as a key-value store for secrets like passwords, access tokens, and cryptographic keys. AWS encrypts these secrets with the AWS Key Management Service (AWS-KMS). This tutorial shows how to set up a KES server that uses AWS Secrets Manager as a persistent key store protected by AWS-KMS: K E S C l i e n t K E S S e r v e r A W S S e c A r W e S t - s K - M M S a n a g e r AWS Secrets Manager Prerequisite You need an AWS access key and AWS secret key pair with sufficient IAM policy permissions to create, retrieve, and delete secrets with AWS Secrets Manager. Create AWS Access/Secret Key Pair.

AIStor Key Manager AIStor Key Manager is a robust key management server (KMS) designed to store cryptographic keys. K...

This section provides documentation on the AIStor Key Encryption Service (KES). AIStor KES is a maintained fork of the MinIO KES project under MinIO’s enterprise license. For new or long-term deployments, consider using AIStor Key Manager to replace KES. Migrate from KES Community Edition to AIStor KES on Linux The following procedure describes how to migrate from the deprecated KES Community Edition (KES CE) to the latest stable AIStor KES release. This procedure assumes an existing KES CE cluster running latest available release.

The mc idp openid ls command lists all OIDC configurations for your AIStor deployment. Example and syntax Example The following example outputs a list of all OIDC configuration sets defined for the myaistor deployment.

Description The mc inventory commands allow you to configure and manage inventory jobs on an AIStor deployment. Inventory jobs generate reports of objects in a bucket based on specified filters and schedules. Added in RELEASE.2025-12-20T04-58-37Z mc inventory and its subcommands require AIStor Client RELEASE.2025-12-19T20-11-44Z or later and AIStor Server RELEASE.2025-12-20T04-58-37Z or later. Subcommands mc inventory includes the following subcommands:

The mc cors remove command removes the Cross-Origin Resource Sharing (CORS) configuration from a bucket. CORS is a browser security mechanism that controls which web domains can access your object storage from client-side JavaScript. When a web application running on one domain attempts to access objects in AIStor from a different domain, the browser checks CORS policies to determine if the request should be allowed. See the Mozilla CORS documentation for more information.

The mc diff mc computes the differences between two filesystem directories or AIStor buckets. mc diff lists only those objects which are missing or which differ in size. mc diff does not compare the contents of objects. Syntax Example The following command computes the difference between the contents in the mydata folder on a local filesystem and the contents in the mydata bucket on the myaistor AIStor deployment:

Syntax Example The following command applies the JSON-formatted anonymous policy to the mydata bucket on the myaistor AIStor deployment: mc anonymous set-json ~/mydata-anonymous.json myaistor/mydata Syntax The command has the following syntax:

Description The mc alias commands provide a convenient interface for managing the list of S3-compatible hosts that mc can connect to and run operations against. Subcommands mc alias includes the following subcommands: