Each MinIO AIStor server process exposes unauthenticated endpoints for probing server uptime and deployment high availability for simple healthchecks. These endpoints return an HTTP status code indicating whether the underlying resource is healthy or satisfies read/write quorum. The server exposes no other data through these endpoints. MinIO AIStor liveness Use the following endpoint to test if the specified MinIO AIStor server is up and ready to serve requests:

The MinIO AIStor Batch Framework allows you to create, manage, monitor, and execute jobs using a YAML-formatted job definition file (a “batch file”). Batch jobs run directly on the MinIO AIStor deployment to take advantage of the server-side processing power without constraints of the local machine where you run the AIStor Client. The keyrotate batch job type performs the following operations on objects in an MinIO AIStor deployment: Encrypts plaintext (unencrypted) objects using SSE-KMS. Rotates encryption keys for objects already encrypted with SSE-S3 or SSE-KMS using SSE-KMS. Rotates encryption keys for internal MinIO AIStor subsystems (IAM configuration, server configuration, tier configuration, and bucket metadata). The YAML configuration supports filters to restrict key rotation to a specific set of objects by creation date, tags, metadata, KMS key, or encryption status. You can also define retry attempts or set a notification endpoint and token.

This page describes how to upgrade MinIO AIStor Helm clusters that use public registries and have direct internet access to helm.min.io and quay.io. If your cluster uses a private container registry or is in an airgapped environment, see: Upgrade with Private Registry Upgrade in Airgapped Environment Overview MinIO AIStor Helm upgrades involve updating two components:

This page describes how to upgrade MinIO AIStor Helm clusters in completely airgapped environments with no direct internet access. If your cluster has internet access, see: Upgrade with Public Registries Upgrade with Private Registry Overview MinIO AIStor Helm upgrades involve updating two components:

Upgrade MinIO Operator and Tenant clusters on Kubernetes to MinIO AIStor using Helm charts while preserving existing data and configurations.

Removes one or more IAM policies from an AIStor-managed user or group. This command is intended for managing policy associations for AIStor-managed users only. For detaching policies to OpenID-managed users, see OpenID Connect Access Management.

Description The mc admin scanner commands provide information about the scanner process. Subcommands mc admin scanner includes the following subcommands:

Attaches one or more IAM policies to either an AIStor-managed user or a group. Exactly one --user or one --group is required. This command is intended for managing policy associations for MinIO-managed users only. For attaching policies to OpenID-managed users, see OpenID Connect Access Management.

Prints Prometheus metrics for a cluster. The output includes additional information about each metric, such as if its value is a counter or gauge. Syntax Example The following command prints v3 Prometheus metrics for the deployment at alias myaistor:

The AIStor Client command line tool includes the mc admin subcommand tree for performing administrative tasks on your MinIO AIStor deployments. mc admin target MinIO AIStor deployments exclusively and do not support any other S3-compatible service. The command has the following top-level syntax. Use the --help parameter to view the CLI help. mc admin [FLAGS] COMMAND [ARGUMENTS] Global options mc admin supports the same global options as mc. See Global Options.