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

# Overview

After you create an Astro Deployment, you can modify its settings using the Astro UI and Astro CLI to tailor its performance. There are two categories of Deployment configurations: Deployment *details* and *resources*.

<Tip>
  **A new Astro UI is here**

  Astronomer has redesigned the Astro UI. Try the new experience and switch your instructions using the **New Astro UI** and **Legacy UI** tabs on this page. Your selection is remembered across the docs.
</Tip>

You can also view more details about your Deployment including:

<Tabs>
  <Tab title="New Astro UI" language="astro-next-ui">
    * **Overview**: View information about your Deployment including recent Dag usage and the [code deploy history](/docs/astro/deploy-history).
    * **Analytics**: Find [detailed metrics](/docs/astro/deployment-metrics) about the historical resource consumption when you run Dags.
    * **Logs**: See the [Airflow and task logs](/docs/astro/view-logs) for a Deployment.
    * **Environment**: Manage [environment variables](/docs/astro/environment-variables), [connections](/docs/astro/create-and-link-connections), [metrics exports](/docs/astro/export-metrics), and [Airflow variables](/docs/astro/create-and-link-variables).
    * **Access**: Manage user, team, and API token access to the Deployment.
    * **Alerts**: Create, manage, and delete [notification channels and alerts](/docs/astro/alerts).
    * **Incident History**: Review [Deployment health incidents](/docs/astro/deployment-health-incidents).
    * **AI Agents**: Configure [Otto investigation guidance](/docs/astro/otto-investigate) for the Deployment.
    * **Details**: Make changes or reference your Deployment configurations.
  </Tab>

  <Tab title="Legacy UI" language="legacy-ui">
    * **Overview**: View information about your Deployment including recent dag usage and the [code deploy history](/docs/astro/deploy-history).
    * **Analytics**: Find [detailed metrics](/docs/astro/deployment-metrics) about the historical resource consumption when you run dags.
    * **Logs**: See the [Airflow and task logs](/docs/astro/view-logs) for a Deployment.
    * **Environment**: Manage [environment variables](/docs/astro/environment-variables), [connections](/docs/astro/create-and-link-connections), [metrics exports](/docs/astro/export-metrics), and [Airflow variables](/docs/astro/create-and-link-variables).
    * **Access**: Manage user, team, and API token access to the Deployment.
    * **Alerts**: Create, manage, and delete [notification channels and alerts](/docs/astro/alerts).
    * **Details**: Make changes or reference your Deployment configurations.
  </Tab>
</Tabs>

## Deployment details

[Deployment details](/docs/astro/deployment-details) are high level settings that define how users can interact with the Deployment. These settings include:

* Deployment names and descriptions.
* Deployment contact emails.
* Rules for what types of deploys are allowed.
* Your Deployment's current Workspace.

## Deployment resources

[Deployment resources](/docs/astro/deployment-resources) let you customize the resource use, infrastructure, and performance of your Deployment. Use these settings to optimize Deployment processing, optimize compute resources and cost, and enable advanced use cases with intensive workloads. The following configuration options are available for customizing your resource use:

* Change the Deployment executor.
* Configure Kubernetes Pod resources.
* Change Scheduler and Dag processor resources.
* Enforce CI/CD Deploys.
* Enable High Availability.
* Customize your Airflow environment using environment variables.

For advanced Deployment resource configurations, see [Manage Airflow executors on Astro](/docs/astro/executors-overview) and [Configure worker queues](/docs/astro/configure-worker-queues).

## Configure Otto investigation guidance

Otto investigation guidance is custom text you provide to tailor [Otto investigations](/docs/astro/otto-investigate) for a Deployment. By default, a Deployment inherits the Otto investigation guidance set at the [Workspace level](/docs/astro/manage-workspaces#configure-otto-investigation-guidance). You can override the inherited guidance with Deployment-specific instructions.

<Tabs>
  <Tab title="New Astro UI" language="astro-next-ui">
    1. In the Astro UI, select a Deployment.
    2. Click the **AI Agents** tab, then click **Edit**.
    3. Enter up to 10,000 characters of markdown guidance, then click **Save**.
  </Tab>

  <Tab title="Legacy UI" language="legacy-ui">
    1. In the Astro UI, select a Deployment.
    2. Click the **AI Agents** tab.
    3. Enter up to 10,000 characters of markdown guidance, then save your changes.
  </Tab>
</Tabs>

Deployment-level guidance takes precedence over Workspace-level guidance for investigations on this Deployment.

<Info>
  **CLI**

  These documents focuses on configuring Deployments through the Astro UI. To configure Deployments as code using the Astro CLI, see [Manage Deployments as code](/docs/astro/manage-deployments-as-code).
</Info>

## See also

* [Set environment variables on Astro](/docs/astro/environment-variables)
* [Authenticate an automation tool to Astro](/docs/astro/automation-authentication)
* [Manage Deployments as Code](/docs/astro/manage-deployments-as-code)