The following procedure adds a server pool to an existing AIStor deployment running on Kubernetes 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. Retrieve and review the existing object store Helm chart. The objectStore.pools key describes the current deployment topology and pool configuration. Each element in the pools array describes a single server pool in the AIStor deployment.

The mc idp ldap accesskey info outputs information about the specified access key(s). 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.

Metrics and Alerts AIStor Server publishes point-in-time metrics using the Prometheus Data Model. You can use any scraping tool which supports that data model to pull those metrics into a database for populating historical views, performing query/analysis of metrics data, or creating alerts on preferred data points.

AIStor supports publishing bucket notification events to a Redis service endpoint. Prerequisites The AIStor mc command line tool This procedure uses the mc command line tool for certain actions. See the mc Quickstart for installation instructions. Add a Redis endpoint to an AIStor Server The following procedure adds a new Redis service endpoint for supporting bucket notifications in an AIStor Server.

AIStor Server publishes cluster and node metrics using the Prometheus Data Model. You can use any scraping tool to pull metrics data from AIStor Server for further analysis and alerting. This page covers metrics version 3, which has additional metrics and endpoints. Existing deployments can continue to use version 2 metrics. Version 3 endpoints For metrics version 3, all metrics are available under the base /minio/metrics/v3 endpoint by appending an additional path for each category.

The mc anonymous set command sets anonymous (that is, unauthenticated or public) access policies for a bucket. Buckets with anonymous policies allow clients to access the bucket contents and perform actions consistent with the specified policy without authentication. To set anonymous bucket policies using an IAM JSON policy, use the mc anonymous set-json command. Syntax Example The following command sets the anonymous access policy for the mydata bucket on the myminio AIStor deployment:

Description The mc idp ldap disable command disables the currently configured AD/LDAP provider. Syntax Example The following example disables the AD/LDAP configurations on the myminio deployment.

Syntax Example The following command retrieves the JSON-formatted anonymous policy for the mydata bucket on the myminio AIStor deployment:

The mc event rm command removes an event notification trigger from a bucket. The mc event remove command has equivalent functionality to mc event rm. Syntax Example The following command removes a configured event notifications for the specified bucket notification target for the mydata bucket on the myminio AIStor deployment:

Description The mc idp ldap policy commands show the mapping relationships between policies and the associated groups or users. This command has the following subcommands: Subcommand Description attach Attaches one or more policies to an entity. detach Detaches one or more policies from an entity. entities Displays a list of mappings for a user, group, and/or policy.