The mc support top net command displays realtime network metrics. Syntax Example The following command displays the current realtime network metrics for the alias myaistor deployment.

The AIStor Client mc support commands provides tools for analyzing deployment health or performance and for running diagnostics. You can also upload generated health reports for further analysis by AIStor engineering. mc support proxy set and mc support proxy remove are exceptions, as you may need to set up a proxy to complete the deployment registration. Subcommands mc support includes the following subcommands:

mc idp openid accesskey disable disables the specified access key on the AIStor deployment. Example and syntax Example The following example disables the access key mykey on the myaistor deployment:

The mc ilm rule command and its subcommands configure the rules used to transition objects between storage tiers in AIStor’s Lifecycle Management. Before creating rules with this command, use mc ilm tier and its subcommands to create the tier or tiers of other object storage locations where objects move. For more information, see the overview of lifecycle management. Subcommands mc ilm rule includes the following subcommands:

The mc mv command moves an object from source to the target, such as between AIStor deployments or between buckets on the same AIStor deployment. mc mv also supports moving objects between a local filesystem and AIStor. You can also use mc mv against the local filesystem to produce similar results to the mv command-line tool. Syntax Example The following command moves objects from the mydata bucket to the archive bucket on the myaistor AIStor deployment:

The mc mb command creates a new bucket on an AIStor deployment. You can also use mc mb to create buckets on S3-compatible services. Syntax Example The following command creates a new bucket on the myaistor deployment:

The MinIO Go Client SDK provides straightforward APIs to access any Amazon S3 compatible object storage. This Quickstart Guide covers how to install the MinIO client SDK, connect to MinIO, and create a sample file uploader. For a complete list of APIs and examples, see the godoc documentation or Go Client API Reference. These examples presume a working Go development environment and the MinIO mc command line tool. Download from GitHub From your project directory:

This tutorial shows how to setup a KES server that uses Fortanix SDKMS as a persistent and secure key store: K E S C l i e n t K E S S e r v e r F o r t a n i x S D K M S Fortanix SDKMS Create Application

The following page includes the full contents of the AIStor Server Operator Helm Chart default values.yaml and all accompanying documentation. # Default values for AIStor Operators chart # The Following annotations/labels are applied to all resources created by the Helm chart annotations: {} labels: {} # Allow override the namespace for all resources #namespaceOverride: "test" # The repositories allow overriding the default repositories that # are used to determine the full images names. When left empty, # the default repository will be used. repositories: {} # aistor: # hostname: quay.io # pathPrefix: minio/aistor/ # minio: # hostname: quay.io # pathPrefix: minio/ # prometheus: # hostname: quay.io # pathPrefix: prometheus/ # The MinIO license can be set directly from the Helm chart. Note that it is not advised # to expose the license key in the Helm chart. Instead, it is recommended to create a # secret manually. It's just here for convenience. license: "" # global settings are settings that will be applied to all operators # unless explicitly overridden in the operator settings. global: # The Helm chart will try to auto-detect OpenShift. If it cannot detect OpenShift # (i.e. when running helm template), then it will default to false. You can # override this setting to force OpenShift mode. #forceOpenShift: true # Specify the default cluster domain. When it's not set, then it # will try to auto-detect the cluster. But you may want to set it # explicitly # clusterDomain: "cluster.xxx" # The following settings will be set for all operators. They can # be overridden per operator by setting the same key in the # .operator.<operator> section. operator: # Specify number of replicas replicas: 1 # Specify `annotations <https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/>`__ to associate to pods. podAnnotations: {} # Specify `labels <https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/>`__ to associate to pods. podLabels: {} # This will add extra environment variables to the operator # containers. extraEnv: [] # Image pull policy (empty uses the default registry policy). imagePullPolicy: "" ### # You may need to set the image pull secrets when using a private registry. # Need to be set as an array of LocalObjectReference. # .. code-block:: yaml # # imagePullSecrets: # - name: minio-registry-secret # type: kubernetes.io/dockerconfigjson imagePullSecrets: [] # Resources for the operator containers. resources: requests: cpu: 200m ephemeral-storage: 100Mi memory: 256Mi # Security context for the operator containers (ignored on OpenShift) securityContext: allowPrivilegeEscalation: false capabilities: drop: - ALL runAsGroup: 1000 runAsNonRoot: true runAsUser: 1000 seccompProfile: type: RuntimeDefault # Security context for the operator pods (ignored on OpenShift) podSecurityContext: {} # fsGroup: 2000 # All operators will be using the global setting, unless overridden # in the section below. All keys in `.global.operators` can also be # used here and will override (not extend) the global setting. # # All operators will be disabled by default, with the exception of # the object-store. operators: adminjob: disabled: false aihub: disabled: true inference: disabled: true object-store: disabled: false # STS can now be used on MinIO endpoints, so there is no need to # enable STS for the object-store. This is kept for backward # compatibility, but will be removed in the future. enableSTS: false prompt: disabled: true warp: disabled: true

The MinIO Python Client SDK provides high level APIs to access any MinIO Object Storage or other Amazon S3 compatible service. This Quickstart Guide covers how to install the MinIO client SDK, connect to the object storage service, and create a sample file uploader. The example below uses: Python version 3.7+ The MinIO mc command line tool The MinIO play test server The play server is a public MinIO cluster located at https://play.min.io. This cluster runs the latest stable version of MinIO and may be used for testing and development. The access credentials in the example are open to the public and all data uploaded to play should be considered public and world-readable.