> ## Documentation Index
> Fetch the complete documentation index at: https://docs.strata.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Maverics Storage

The Maverics Storage config source connects the Orchestrator to Strata-managed cloud storage for centralized configuration delivery. The Console provisions and manages this storage automatically through its deployment management system.

<Warning>
  **Evaluation only -- storage is recycled every 90 days.** Maverics Storage is for evaluation and testing purposes only. All published configurations are deleted when storage is recycled. For production deployments, configure a persistent config source such as [Amazon S3](/reference/orchestrator/configuration/config-sources/s3), [Azure Blob](/reference/orchestrator/configuration/config-sources/azure-blob), or [Google Cloud Storage](/reference/orchestrator/configuration/config-sources/gcs). See [Config Sources](/reference/orchestrator/configuration/config-sources) for all available options.
</Warning>

<Note>
  **Maverics Storage** is the Strata-hosted config delivery mechanism used by Console
  deployments. In the Maverics Console, Orchestrator instances and configuration delivery
  are managed through **Deployments**. When working directly with YAML, configuration
  is managed as files delivered via the `-config` flag or `MAVERICS_CONFIG` environment variable.
</Note>

## Overview

When an Orchestrator is configured through the Maverics Console, the Console provisions Maverics Storage (a temporary S3 bucket) for each deployment. The Orchestrator downloads its configuration from this storage. Configuration bundles are cryptographically signed and verified before application, ensuring that only authentic, unmodified configuration is loaded.

This config source type is called **Maverics Storage** and is designed for managing multiple Orchestrator instances from a single control plane -- the Console handles all provisioning and delivery automatically.

<Note>
  When using Console-managed configuration, the Orchestrator receives its configuration from the Maverics Console. You do not need to set `MAVERICS_CONFIG` or any remote config source environment variable.
</Note>

## Use Cases

* **Multi-Orchestrator fleet management** -- manage configuration for multiple Orchestrator instances from a single Console
* **Centralized config delivery** -- deliver configuration through the Console management plane with audit trails
* **Team collaboration** -- enable multiple team members to author and review configuration changes through the Console UI

## Getting Started with Maverics Storage

When using Maverics Storage, you download an evaluation bundle from the Console that includes everything the Orchestrator needs -- the binary, preconfigured environment variables, and self-signed certificates.

You do not need to configure any environment variables manually. The evaluation bundle sets `MAVERICS_AWS_CONFIG`, `MAVERICS_BUNDLE_PUBLIC_KEY_FILE`, `MAVERICS_RELOAD_CONFIG`, and `MAVERICS_POLLING_INTERVAL_SECONDS` automatically.

<Info>
  For step-by-step setup instructions including how to select Maverics Storage, publish configuration, and download the evaluation bundle, see [Maverics Storage](/reference/console/config-publishing/maverics-storage).
</Info>

## Configuration

Console-managed deployments are configured entirely through the Maverics Console. The Console handles all provisioning -- including the temporary S3 bucket -- automatically. There are no YAML flags or environment variables to set manually for this config source.

To select Maverics Storage as your configuration storage provider:

1. Navigate to **Deployments** in the Console sidebar and select your deployment.
2. Under **Host Environment**, click **Edit** next to **Configuration Storage**.
3. Select **Maverics Storage** from the **Storage Provider** dropdown.
4. Click **Save**.
5. Publish your deployment configuration and download the evaluation bundle.

The evaluation bundle includes the Orchestrator binary, preconfigured environment variables, and self-signed certificates. When you create a Deployment in the Console and install the Orchestrator, configuration is delivered automatically. See [Maverics Storage setup](/reference/console/config-publishing/maverics-storage) for the full walkthrough.

## Configuration Reference

Console-managed deployments are configured through the Console UI. There are no CLI flags or environment variables specific to this config source -- the Console handles all provisioning and delivery automatically.

## Troubleshooting

* **Orchestrator not receiving config** -- check network connectivity between the Orchestrator and the Maverics Console. Ensure firewalls allow outbound HTTPS traffic to the Console and to AWS S3 (used for configuration delivery).
* **Conflict with other config sources** -- do not set `MAVERICS_CONFIG` or remote config source environment variables when using Console-managed configuration.

## Related Pages

<CardGroup cols={2}>
  <Card title="Config Sources" icon="folder-gear" href="/reference/orchestrator/configuration/config-sources">
    Overview of all configuration sources
  </Card>

  <Card title="File" icon="file" href="/reference/orchestrator/configuration/config-sources/file">
    Load config from a local YAML file
  </Card>

  <Card title="Maverics Storage" icon="cloud" href="/reference/console/config-publishing/maverics-storage">
    Console-side Maverics Storage setup and evaluation bundle download
  </Card>
</CardGroup>