Skip to main content

Documentation Index

Fetch the complete documentation index at: https://astronomer-preview.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

This is feature is only available if you are on theTeamtier or above. SeeAstro Plans and Pricing.
A dedicated cluster exclusively runs Deployments from your Organization within a single-tenant environment on Astronomer’s cloud. Dedicated clusters provide more configuration options for regions, connectivity, and security than standard clusters. You might want to create a dedicated cluster if:
  • You need to connect to data services using private networking.
  • You want more options for the region your cluster is hosted in.
  • You otherwise want to keep your Deployments as isolated as possible.
Dedicated clusters offer the self-service convenience of a fully managed service while respecting the need to keep data private, secure, and within a single-tenant environment. If you don’t need the aforementioned features, you can use one of the standard clusters when you Create a Deployment.

​
Setup

  1. In the Astro UI, click Organization Settings, then click Clusters.
  2. Click + Cluster.
  3. Configure the following details about your cluster:
    • Cloud Provider: Select AWS.
    • Name: The name for your cluster.
    • Region: Select the region that you want your cluster to run in.
    • VPC Subnet Range: Provide a subnet range for Astro to connect to your existing AWS resources through VPC peering. The default is 172.20.0.0/20, and the minimum size you can use is /22.
  4. (Optional) Expand Advanced Configuration to further define Kubernetes Pod Networking: Astro allocates a secondary VPC CIDR range specifically for Kubernetes Pod IPs within your cluster. Pods use source network address translation (SNAT) for connections outside the VPC, so your data sources see connections from the primary VPC subnet, not the Pod CIDR. Only traffic internal to the VPC, such as to RDS databases, appears from Pod IPs in the secondary CIDR.
    • Pod CIDR Range: Specify the range for Pod IP addresses. This range must not overlap with your VPC Subnet Range or any connected networks.
    The Pod CIDR range isolates Pod networking and mitigates Pod IP exhaustion. SNAT ensures that all external connections use the main VPC subnet, simplifying integration with external services.
  5. (Optional) In the Disaster Recovery section, configure cross-region disaster recovery:
    Cross-region disaster recovery requires the Enterprise Business Critical tier.
    • Cross-Region Disaster Recovery: Enable to create a secondary DR cluster in a different AWS region.
    • Failover Region: Select the AWS region for the secondary cluster.
    • DR VPC Subnet Range: Specify a different VPC subnet range for the secondary cluster, or leave blank to use the same range as the primary cluster.
    • DR Pod CIDR Range: Specify a different Pod CIDR range for the secondary cluster, or leave blank to use the same range as the primary cluster.
    • Task Logs Replication SLA: Enable to guarantee a 15-minute recovery point objective (RPO) for task logs. Additional charges apply.
    See Disaster recovery for details on how these options affect your DR configuration.
  6. Click Create cluster. After Astro finishes creating the cluster, users in your Organization can select the cluster when they create a Deployment.