This document applies only to Astro Hosted and does not apply to Astro Hybrid. To see whether you’re an Astro Hosted user, click Organization Settings. On the General page, your Astro product type is listed under Product Type.
To learn more about Astro solutions, see Remote Execution and Create a Deployment.
This page contains reference information for all supported Astro Hosted Deployment and cluster resource configurations. Use this information to determine whether Astro supports the type of Airflow environment you want to run.
If you’re interested in a cloud region or resource size that’s not mentioned here, reach out to Astronomer support.
Astro Deployments use the worker types in the following table.
If you use the Astro executor or Celery executor, you can configure a worker queue to run tasks on a specific worker type. The Astro executor is the default for all Airflow 3.x Deployments. If you use the Kubernetes executor, Astro uses the number of A5 workers necessary to accommodate the total amount of CPU and Memory needed for the tasks.
With the Kubernetes executor, you can configure ephemeral storage per task otherwise the Deployment default setting is applied. With the Astro executor or Celery executor, you can configure ephemeral storage and concurrency for tasks per worker queue. See Configure the Astro executor or Configure the Celery executor.
A standard cluster is a multi-tenant cluster that’s hosted and managed by Astronomer. Astronomer maintains standard clusters in a limited regions and clouds, with support for more regions and clouds coming soon.
Currently, standard clusters are available on the following clouds and regions:
A dedicated cluster is cluster that Astronomer provisions solely for use by your Organization. You can create new dedicated clusters from the Astro UI in a variety of clouds and regions. To configure dedicated clusters, see Create a dedicated cluster.
Currently, dedicated clusters are available on the following clouds and regions: