The mc idp ldap accesskey ls displays a list of LDAP access key pairs. mc idp ldap accesskey ls is also known as mc idp ldap accesskey list. 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.

The mc get command retrieves objects from an AIStor deployment or S3-compatible service to a local filesystem. mc get provides a simplified interface for downloading files compared to mc cp or mc mirror. mc get uses a one-way download function that trades efficiency for the power and complexity of the other commands. Syntax Example The following command downloads an object from the myaistor deployment to the local filesystem:

The mc cors get command retrieves and displays the Cross-Origin Resource Sharing (CORS) configuration for a bucket in XML format. 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.

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

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

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

The Temporal.Duration() constructor creates Temporal.Duration objects.

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

The Temporal.Now.plainTimeISO() static method returns the current time as a Temporal.PlainTime object, in the specified time zone.

AIStor supports hot-swapping failed drives with new healthy drives. Healing AIStor detects and heals those drives without requiring any node or deployment-level restart. AIStor healing occurs only on the replaced drive(s) and in most cases has minimal or negligible impact on deployment performance.