The mc admin scanner trace command displays scanner-specific API operations occurring on the target AIStor deployment. Syntax Example The following example returns a list of API operations related to the scanner on the myaistor deployment.

You can use the AIStor Console to perform many of the deployment monitoring and management functions available in AIStor, such as: License to monitor the status and expiration of the MinIO Commercial License used for the AIStor deployment. Monitor the health and activity of the deployment by reviewing metrics, server or audit logs, trace history, S3 events, or drive health. Configure alerts by adding or managing a notification target. Set up site replication to synchronize datacenters for timely access across geographically dispersed workforces or for disaster preparedness. Configure deployment settings. Overview The Overview page displays summary information for a deployment including:

This page documents upgrade procedures for AIStor Server deployments on Baremetal Linux infrastructure. All AIStor software supports non-disruptive upgrades with zero downtime. In optimal environments, cluster-wide upgrades typically complete in under 500 milliseconds with large clusters (1000+ nodes) completing in less than 5 seconds. Upgrade AIStor using DEB or RPM Use these steps to upgrade an AIStor deployment where the server process is managed by systemctl, such as those created using the AIStor DEB/RPM packages.

The mc admin kms key command performs cryptographic key management operations through the AIStor Key Encryption Service (KES). Syntax mc admin kms key create Creates a new master key on a Key Management System (KMS).

The following procedure adds a server pool to an existing AIStor deployment running on baremetal infrastructure. Each pool expands the total available storage capacity of the cluster while maintaining the overall availability of the cluster. All commands provided below use example values. Replace these values with those appropriate for your deployment. Deploy AIStor on new hardware Follow the installation guide to install AIStor onto the new hardware. Do not start the new deployment - stop at the step Review the environment file

The mc encrypt set encrypt command sets or updates the default bucket Server-Side Encryption (SSE) mode. AIStor automatically encrypts objects written to that bucket using the specified SSE mode. mc encrypt set supports only SSE-KMS and SSE-S3 encryption types. Syntax Example The following command sets the default encryption configuration for a bucket:

The mc idp ldap accesskey commands allow you to list, delete, or display information about LDAP access key pairs on the AIStor deployment. This command works against access keys created by an AD/LDAP user after authenticating to AIStor. Create AD/LDAP service accounts with the mc idp ldap accesskey create command. Authenticated users can manage their own long-term Access Keys using the AIStor Console. AIStor supports using AssumeRoleWithLDAPIdentity to generate temporary access keys using the Security Token Service.

The mc admin user command and its subcommands manage AIStor users. Clients must authenticate to the AIStor deployment with the access key and secret key associated to a user on the deployment. AIStor users constitute a key component in AIStor Identity and Access Management. To manage users who authenticate using a third-party IDP, use the command for the appropriate provider: For AD/LDAP, use mc idp ldap For OpenID Connect (OIDC) compatible providers, use mc idp openid Subcommands mc admin user includes the following subcommands:

The mc admin cluster iam export command exports IAM metadata for use with the mc admin cluster iam import command. The command saves the output as ALIAS-iam-metadata.zip, where ALIAS is the alias of the AIStor deployment. Syntax Example The following command exports all IAM metadata for the myaistor deployment.

The mc admin user enable command enables an AIStor user on the target AIStor deployment. Clients can only use enabled users to authenticate to the AIStor deployment. Users created using mc admin user add are enabled by default. To manage external Identity Provider users, see OIDC or AD/LDAP. Syntax Example The following command enables user myuser on the myaistor AIStor deployment: