The mc idp ldap accesskey enable enables the specified access key on the local server. Syntax Example The following example enables the access key mykey from the myaistor deployment:

This page describes how to upgrade AIStor Helm deployments in completely airgapped environments with no direct internet access. If your deployment has internet access, see: Upgrade with Public Registries Upgrade with Private Registry Overview AIStor Helm upgrades involve updating two components:

The mc alias import command imports an alias configuration from a JSON file or STDIN. The command reads the configuration and adds it as a new alias or updates an existing one. Syntax Example The following command imports an alias configuration from a file:

The mc alias remove command removes an alias from the AIStor Client configuration. Syntax Example The following command removes the alias named myaistor:

Description The mc admin scanner commands provide information about the scanner process. Subcommands mc admin scanner includes the following subcommands:

Creates a new policy on the target AIStor deployment. AIStor deployments include the following built-in policies by default: consoleAdmin readonly readwrite diagnostics writeonly Syntax Example Consider the following JSON policy document saved at a file called /tmp/listmybuckets.json:

This section provides reference documentation for AIStor Object Store components. The AIStor Server reference provides extensive details of how AIStor Server works. As you build or expand your infrastructure, look here for requirements for compute, network, memory, and storage, as well as thresholds and limits. Find recommended hardware tests, detailed explanations of how the scanner works and how to implement S3 express. AIStor provides extensive set of options to customize how AIStor runs. Configure the many options through either environment variables or configuration settings.

Use the following examples to help design your own QoS rules. Basic rate limiting The following QoS rule sets a rate limit of 50 s3.PutObject requests per second with a burst of 10. The rule applies to all objects in the bucket and has the highest priority.

The mc cors commands manage Cross-Origin Resource Sharing (CORS) configuration for buckets. Cross-Origin Resource Sharing (CORS) is a browser security mechanism that controls which web domains can access your object storage from client-side JavaScript. When a web application running on one domain attempts to access objects in AIStor from a different domain, the browser checks CORS policies to determine if the request should be allowed. See the Mozilla CORS documentation for more information.

Description The mc admin cluster iam command and its subcommands provide tools for manually importing and exporting AIStor identity and access management (IAM) metadata. For automatic synchronization of all IAM configurations in a deployment to a remote site, use site replication.