MinIO AIStor brings the first native implementation of Delta Sharing to S3-compatible storage in private, public, and hybrid cloud environments.

AIStor Server publishes its server logs to the system console. These logs can include errors, information output, or other information useful during troubleshooting or debugging. Server logs do not emit for all operations and cannot support audit trail or similar compliance requirements. If you require such a trail, configure and use audit logging instead. You can read the server logs using any of the following methods: Run journalctl -u minio from any host machine. Run mc admin logs against the MinIO AIStor deployment. Record logs to disk New feature — opt-in only Disk-based log recording is a new feature that is disabled by default. Enable it only after thorough testing at scale with your application workload. MinIO is actively optimizing this feature in subsequent releases. MinIO AIStor can record API, error, and audit logs directly to disk as compressed JSON files. This complements webhook-based logging for compliance, forensics, and offline analysis. Logs are stored internally and managed automatically by MinIO AIStor.

MinIO AIStor Tables uses standard MinIO AIStor policy-based access control (PBAC) to define authorized actions on warehouses, namespaces, and tables. For more information about PBAC in MinIO AIStor, see Access Control with Policy Management Resource reference ARN patterns MinIO AIStor Tables uses ARN patterns to identify resources in policies:

MinIO AIStor supports publishing audit logs to one or more configured Apache Kafka receivers. MinIO AIStor send an event for each API operation to the receiver for processing and storage. The receiver is responsible for correctly processing events, including returning 200OK or similar success messages upon receipt of the event. MinIO AIStor cannot recover events that were successfully sent but not correctly stored on the receiver. You can configure a new Kafka audit endpoint using either environment variables or runtime configuration settings. If you configure both, MinIO AIStor uses the environment variables.

This guide details the JDK Migration process.

Skip to Main Content Documentation Home MySQL 8.0 Reference Manual Related Documentation MySQL 8.0 Release Notes MySQ...

Protect MinIO AIStor data directories from accidental deletion using kernel-level storage protection with SELinux or eBPF LSM.

Skip to Main Content Documentation Home MySQL 8.0 Reference Manual Related Documentation MySQL 8.0 Release Notes MySQ...

Introduction JAR file is a file format based on the popular ZIP file format and is used for aggregating many files in...

Multi-tenancy allows multiple isolated workloads, teams, or customers to share a single MinIO AIStor deployment while maintaining data isolation and access control. IAM-based multi-tenancy The recommended approach uses a single deployment with IAM-based isolation. Each tenant is represented as an IAM user or group with policies that restrict access to specific buckets or prefixes.