Access management and policies MinIO AIStor uses the built-in access management where a user’s attached policies determines the operations and data paths to which they have access. The mc table share commands require the following permissions: admin:DeltaSharingCreateShare admin:DeltaSharingGetShare admin:DeltaSharingListShares admin:DeltaSharingUpdateShare admin:DeltaSharingDeleteShare The user must also have s3:GetObject and s3:ListBucket permissions on all buckets and paths in which they must manage table shares.

MinIO AIStor supports publishing an audit log of all operations to a remote receiver. The audit logging feature meets security and compliance requirements around granular tracking of operations within an MinIO AIStor deployment. MinIO AIStor does not by default publish audit logs to any destination. Audit logs can contain private and internal details such as hostnames, IP addresses, and object names. The remote receiver takes responsibility for processing, storing, and securing all incoming audit logs.

Removes an IAM policy from the target MinIO AIStor deployment. Syntax Example The following command removes the policy readonly from the deployment at alias myaistor.

Java Platform, Standard Edition Java Scripting Programmer's Guide Release 11 E94834-03 October 2020 Java Platform, Standard Edition Java Scripting Programmer's Guide, Release 11 E94834-03 Copyright...

Java Platform, Standard Edition Java Language Updates Release 11 E94884-05 January 2025 Java Platform, Standard Edition Java Language Updates, Release 11 E94884-05 Copyright © 2017, 2025, Oracle an...

This page provides guidance for upgrading MinIO AIStor Helm clusters on Kubernetes infrastructure. Overview MinIO AIStor Helm installations consist of two primary components: Operator Chart - Controls resources like CustomResourceDefinitions and core operator functionality Object Store Chart - Deploys and manages MinIO AIStor instances Upgrades involve updating these charts and deploying new container images. The exact procedure depends on your cluster environment’s network configuration and registry access.

The mc admin info command displays information on an MinIO AIStor server. For distributed MinIO AIStor deployments, mc admin info displays information for each node in the deployment. The output of the command resembles the following for a four-node cluster: ● node1.example.com:9000 Uptime: 3 days Version: 2025-01-01T00-00-00Z Network: 4/4 OK Drives: 4/4 OK Pool: 1 ● node2.example.com:9000 Uptime: 3 days Version: 2025-01-01T00-00-00Z Network: 4/4 OK Drives: 4/4 OK Pool: 1 ● node3.example.com:9000 Uptime: 3 days Version: 2025-01-01T00-00-00Z Network: 4/4 OK Drives: 4/4 OK Pool: 1 ● node4.example.com:9000 Uptime: 3 days Version: 2025-01-01T00-00-00Z Network: 4/4 OK Drives: 4/4 OK Pool: 1 Pools: 1st, Erasure sets: 1, Drives per erasure set: 16 1.5 TiB Used, 12 Buckets, 48000 Objects 16 drives online, 0 drives offline, EC:4 Syntax Example The following command displays MinIO AIStor server information for the alias myaistor:

Java Platform, Standard Edition Java Accessibility Guide Release 11 E94832-03 December 2020 Java Platform, Standard Edition Java Accessibility Guide, Release 11 E94832-03 Copyright © 1993, 2020, Or...

The mc admin name command and its subcommands manage the cluster name for an MinIO AIStor deployment. The cluster name identifies the deployment in SUBNET registration and other administrative contexts. If you do not set a cluster name, MinIO AIStor automatically generates one at startup using the format <MythicalCreature><Element> (for example, “GriffinWave”, “UnicornFrost”, “KrakenStone”). The auto-generated name persists across restarts. You can also set the cluster name using the MINIO_SITE_NAME environment variable. When set with the environment variable, the name cannot be changed with mc admin name set.

Returns the specified policy in JSON format if it exists on the target MinIO AIStor deployment. Syntax Example The following command returns the policy readonly in JSON format from the deployment at alias myaistor.