Use the mc share commands to manage presigned URLs for downloading and uploading objects to a bucket. Subcommands mc share includes the following subcommands: Subcommand Description mc share download The mc share download command creates URLs for performing GET operations mc share list The mc share list command lists active share URLs mc share upload The mc share upload command creates URLs for performing PUT operations

If you integrate AIStor with Active Directory (AD/LDAP) as your identity provider, you can also manage access with AD/LDAP. AIStor can map a user’s Distinguished Name or group Distinguished Names (DNs) to existing policies. See Active Directory/LDAP Identity Management for configuring the integration. This page explains how to create AIStor access policies that match the AD/LDAP DNs. AIStor supports configuring a single Active Directory or LDAP (AD/LDAP) service for external management of user identities.

In rare circumstances, you may need to restore site replication service account information to a peer in the cluster. Seeing AccessDenied for site replication calls either in logs or with :mc-cmd:mc admin trace indicates a need to restore service account information to a peer. This error typically results when the service accounts for site replication of one of the peer sites have been lost or corrupted. Procedure To restore the required information, export the service account information from an existing healthy peer site and import it to the site with the missing account information.

AIStor supports using an OpenID Connect (OIDC) identity provider (IDP) such as Okta, KeyCloak, Dex, Google, or Facebook for external management of user identities. This page explains how to configure an OIDC provider for AIStor on Kubernetes and bare-metal infrastructures. See OpenID Connect Access Management for how to set up appropriate access controls for OIDC-managed identities. This procedure is generic for OIDC compatible providers. Refer to the documentation for the OIDC provider of your choice for specific information.

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:

You can exclude up to 10 prefixes on a bucket with versioning enabled. This is especially useful for Spark or Hadoop workloads or any process that initially creates objects with temporary prefixes. Prefixes A prefix is a common leading string of characters under a bucket that a set of objects share.

AIStor bucket notifications allow administrators to send notifications to supported external services when events occur on objects or buckets, similar to Amazon S3 Event Notifications. This page lists supported event types that trigger notifications, including bucket-level and object-level S3 events. Supported notification targets AIStor supports publishing event notifications to the following targets:

The mc admin accesskey edit command modifies the configuration of an access key associated to the specified user. The command requires that at least one attribute of the access key change. Otherwise, the command exits with an error message. Syntax Example The following command applies a new policy and secret key to the myuserserviceaccount access key on the myaistor deployment:

This page documents the steps necessary to add a new AIStor installation to an existing Site Replication configuration. The procedures assumes a new AIStor installations and an existing set of deployments configured for Site Replication. The existing configuration must have all AIStor peer sites reachable and healthy. If any of the sites are unreachable or permanently lost, you must first remove the unreachable site(s) with mc admin replicate rm before expanding with the new site.

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.