Each MinIO AIStor release publishes a set of artifacts alongside the server and client binaries. These artifacts support compliance auditing, dependency tracking, and automated release monitoring. AIStor Server artifacts Every AIStor Server release includes the following artifacts: Artifact Format Description Release notes Markdown Changes, bug fixes, security updates, and new features SBOM (CycloneDX) JSON Software Bill of Materials in CycloneDX format SBOM (SPDX) JSON Software Bill of Materials in SPDX format Go modules Text Complete list of Go module dependencies and versions All artifacts for past and current releases are available at the server release notes index.

This guide covers configuring Microsoft Entra ID (formerly Azure Active Directory) as an OpenID Connect (OIDC) identity provider for MinIO AIStor. For general OIDC configuration, see OpenID Connect Identity Management. Prerequisites An active Azure subscription with access to the Azure Portal. A MinIO AIStor deployment with network connectivity to Microsoft identity endpoints. The mc CLI installed and configured with an alias for your MinIO AIStor deployment. Microsoft Graph API permissions MinIO AIStor uses the Microsoft Graph API to query group memberships for authenticated users. The following Application permissions are required (not Delegated):

Object tiering is the moving of the data of an object from one set of hardware to another set of hardware. This is often done as a cost-saving measure, keeping more expensive and performant hardware for the newest or most accessed objects while placing other objects to less expensive and less performant storage solutions. Retrieve a tiered object When MinIO AIStor moves an object to another tier, the object’s metadata remains on the primary tier while the object’s data moves to the secondary tier. When MinIO AIStor needs to serve a tiered object, it transparently retrieves the object from the secondary tier.

MinIO AIStor supports compressing objects to reduce disk usage. Objects are compressed on PUT before writing to disk, and uncompressed on GET before they are sent to the client. This makes the compression process transparent to client applications and services. Depending on the type of data, compression may also increase overall throughput. Write throughput for a production deployment is generally 500MB per second or greater per available CPU core in the system. Decompression is approximately 1 GB per second or greater for each CPU core.

MinIO AIStor supports publishing bucket notification events to a Kafka service endpoint. MinIO AIStor relies on the https://github.com/Shopify/sarama project for Kafka connectivity and shares that project’s Kafka support. See the sarama Compatibility and API stability section for more details. Prerequisites Kafka minimum versions and supported versions.

You can apply bucket rate limiting and concurrency rules to any of the following APIs: S3 Bucket metadata operations s3.GetBucketLocation s3.GetBucketPolicy s3.GetBucketEncryption s3.GetBucketLifecycleConfiguration s3.GetBucketVersioning s3.GetBucketTagging s3.GetBucketACL s3.GetBucketCORS s3.GetBucketWebsite s3.GetBucketNotificationConfiguration s3.GetObjectLockConfiguration s3.GetBucketReplicationConfiguration Bucket configuration operations s3.PutBucket s3.PutBucketPolicy s3.PutBucketEncryption s3.PutBucketLifecycleConfiguration s3.PutBucketVersioning s3.PutBucketTagging s3.PutBucketACL s3.PutBucketNotificationConfiguration s3.PutObjectLockConfiguration s3.PutBucketReplicationConfiguration Bucket deletion operations s3.DeleteBucket s3.DeleteBucketPolicy s3.DeleteBucketTagging s3.DeleteBucketWebsite s3.DeleteBucketLifecycleConfiguration s3.DeleteBucketEncryption s3.DeleteBucketReplicationConfiguration Object read operations s3.GetObject s3.GetObjectAttributes s3.GetObjectACL s3.GetObjectTagging s3.GetObjectRetention s3.GetObjectLegalHold s3.HeadObject Object write operations s3.PutObject s3.PutObjectExtract s3.PutObjectACL s3.PutObjectTagging s3.PutObjectRetention s3.PutObjectLegalHold s3.CopyObject Object deletion operations s3.DeleteObject s3.DeleteObjects s3.DeleteObjectTagging Object listing operations s3.ListObjectsV2 s3.ListObjectVersions s3.ListobjectsV1 s3.ListBuckets Multipart upload operations s3.NewMultipartUpload s3.UploadPart s3.UploadPartCopy s3.CompleteMultipartUpload s3.AbortMultipartUpload s3.ListMultipartUploads s3.ListObjectParts Other operations s3.SelectObjectContent s3.RestoreObject s3.PostPolicy s3.ListenNotification s3.ReplicationResyncStatus s3.ReplicationResyncStart SFTP operations sftp.GET sftp.PUT sftp.LIST sftp.STAT sftp.MKDIR sftp.RMDIR sftp.REMOVE

Best-effort enforcement Bucket quota enforcement is best-effort and not real-time. MinIO AIStor evaluates quota usage periodically through its internal scanner, so a bucket may temporarily exceed its configured quota between scanner cycles. Do not rely on bucket quotas as a hard ceiling for safety-critical storage limits. MinIO AIStor supports setting hard quotas on buckets to limit the total amount of data a bucket can store. When a bucket reaches its configured quota, MinIO AIStor rejects further write operations to that bucket until data is removed to bring usage below the limit.

MinIO AIStor includes built-in performance testing tools to measure object operations, drive I/O, network bandwidth, site replication throughput, and client-to-server bandwidth. For OS-level tuning recommendations, see Performance Tuning. mc support perf The mc support perf command runs performance tests against a MinIO AIStor deployment.

AIStor Server publishes cluster and node metrics using the Prometheus Data Model. InfluxDB supports scraping MinIO AIStor metrics data for monitoring and alerting. The procedure on this page documents the following: Configuring an InfluxDB service to scrape and display metrics from an MinIO AIStor deployment Configuring an Alert on an MinIO AIStor metric This tutorial uses metrics version 2. You can also use metrics version 3, which is recommened for new deployments. For more information about version 3, see Metrics and alerts.

You can use the MinIO AIStor Console to perform many of the deployment monitoring and management functions available in MinIO AIStor, such as: License to monitor the status and expiration of the MinIO Software License used for the MinIO 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: