This page covers settings that control behavior related to AIStor bucket notifications. You can establish or modify settings by defining: an environment variable on the host system prior to starting or restarting the AIStor Server. Refer to your operating system’s documentation for how to define an environment variable. a configuration setting using mc admin config set. If you define both an environment variable and the similar configuration setting, AIStor uses the environment variable value.

The mc support inspect command collects the data and metadata associated to objects at the specified path. If this information is required to diagnose a SUBNET issue, AIStor Engineering will provide the appropriate command. AIStor assembles this data from each backend drive storing an erasure shard for each specified object. For registered clusters, the file uploads to AIStor for use by the engineering team in support efforts. The command produces an encrypted zip file that includes all matching files with their respective host+drive+path. When writing the zip archive, AIStor also encrypts the zip index of file names included in the archive. The resulting report is intended for use by AIStor Engineering via SUBNET and may contain internal or private data points associated to the object. Exercise caution before sending a report to a third party or posting the report in a public forum.

This page documents settings for configuring an Webhook service as a target for Bucket Notifications. See Publish Events to Webhook for a tutorial on using these settings. You can establish or modify settings by defining: an environment variable on the host system prior to starting or restarting the AIStor Server. Refer to your operating system’s documentation for how to define an environment variable. a configuration setting using mc admin config set. If you define both an environment variable and the similar configuration setting, AIStor uses the environment variable value.

The AIStor Security Token Service (STS) AssumeRoleWithWebIdentity API endpoint generates temporary access credentials using a JSON Web Token (JWT) returned from a configured OIDC Identity Provider (IDP). This page documents the AIStor Server AssumeRoleWithWebIdentity endpoint. For instructions on implementing STS using an S3-compatible SDK, refer to the documentation for that SDK. The AIStor STS AssumeRoleWithWebIdentity API endpoint is modeled after the AWS AssumeRoleWithWebIdentity endpoint and shares certain request/response elements. This page documents the AIStor-specific syntax and links out to the AWS reference for all shared elements.

Scoped packages

Start a package

The following page includes the full contents of the AIStor Custom Resource Definition V1 (Stable) CustomResourceDefinition. API Reference Packages aistor.min.io/v1 aistor.min.io/v1 Package v1 - This page provides a quick automatically generated reference for the AIStor ObjectStore Operator aistor.min.io/v1 CRD.

The mc sql command provides an S3 Select interface for performing sql queries on objects in the specified AIStor deployment. See Selecting content from objects for more information on S3 Select behavior and limitations. Syntax Example The following command queries all objects in the mydata bucket on the myaistor AIStor deployment:

Documentation for the npm registry, website, and command-line interface

Documentation for the npm registry, website, and command-line interface