Skip to main content
This document applies only to Astro Hybrid. To see whether you’re an Astro Hybrid user, click Organization Settings. Your Astro product type is listed under Product Type on the General page.To get started on Astro Hosted, see Start a trial.
To install Astro Hybrid on GCP, Astronomer support creates a cluster in a dedicated GCP account that’s hosted and owned by your organization. This ensures that all data remains within your network and allows your organization to manage infrastructure billing. To complete the installation, you’ll:
  • Create an Astronomer account.
  • Create a new Google Cloud project.
  • Enable Google Cloud APIs and add an IAM service account that will be used by Astro.
Astronomer support will create infrastructure within your Google Cloud project to host the resources and Apache Airflow components necessary to deploy Dags and execute tasks. If you need more than one Astro cluster, contact Astronomer support.

​
Prerequisites

  • A Google Cloud project with billing enabled. For security reasons, Google Cloud project with existing infrastructure aren’t supported.
  • A user with Owner permissions in your project.
  • Google Cloud Shell.
  • CIDR blocks of with ranges /19, /20, /22, and /22 are required for the Astro Data Plane. If you don’t have any preferred CIDR block, Astro will provision VPCs using a default CIDR ranges. See GCP resource reference for details.
  • A minimum CPU quota of 48. To adjust your project’s quota limits, see Managing your quota using the Cloud console. To view the quota limits for a project, run gcloud services enable compute.googleapis.com in the Google Cloud CLI.
  • A minimum N2_CPU quota of 24. To adjust your project’s quota limits, see Managing your quota using the Cloud console. To view the quota limits for a project, run gcloud services enable compute.googleapis.com in the Google Cloud CLI.
  • A subscription to the Astro Status Page. This ensures that you’re alerted when an incident occurs or scheduled maintenance is required.
  • The following domains added to your organization’s allowlist for any user and CI/CD environments:
    • https://cloud.astronomer.io/
    • https://api.astronomer.io/
    • https://images.astronomer.cloud/
    • https://auth.astronomer.io/
    • https://updates.astronomer.io/
    • https://install.astronomer.io/
    • https://astro-<your-org>.datakin.com/
    • https://<your-org>.astronomer.run/

​
VPC peering prerequisites (optional)

If any of your GCP resources are on a private network, you can access them using one of the following options: Astro uses four different CIDR blocks to create your Astronomer cluster infrastructure. If you plan on peering with an existing VPC and want to use custom values for your CIDRs, then you must additionally provide your own CIDR ranges (RFC 1918 IP Space) for the following services:
  • Subnet CIDR: Used by nodes in your GKE cluster (Default: 172.20.0.0/22)
  • Pod CIDR: Used by GKE pods (Default: 172.21.0.0/19)
  • Service Address CIDR: Used by GKE services (Default: 172.22.0.0/22)
  • Service VPC Peering: Used by Private Service Connections (Default: 172.23.0.0/20)
The CIDR range sizes must be equal to or greater than the default range sizes for each service.

​
Access Astro

  1. Go to https://cloud.astronomer.io/ and create an account, or enter your email address, and then click Continue.
  2. Select one of the following options to access the Astro UI:
    • Enter your password and click Continue.
    • To authenticate with an identity provider (IdP), click Continue with SSO, enter your username and password, and then click Sign In.
    • To authenticate with your GitHub account, click Continue with GitHub, enter your username or email address, enter your password, and then click Sign in.
    • To authenticate with your Google account, click Continue with Google, choose an account, enter your username and password, and then click Sign In.
    If you’re the first person in an Organization to authenticate, you’re added as a Workspace Owner to a new Workspace named after your Organization. You can add other team members to the Workspace without the assistance of Astronomer support. See Manage Workspace users. To integrate an identity provider (IdP) with Astro, see Set up an identity provider.

​
Activate the data plane

The data plane is a collection of infrastructure components for Astro that run in your cloud and are fully managed by Astronomer. This includes a central database, storage for Airflow tasks logs, and the resources required for task execution. Click the following button to open Google Cloud Shell and run a script to activate the data plane: Open in Cloud Shell The script uses your owner role to complete following actions:
  • Enable the following required services for running the data plane:
    • storage.googleapis.com
    • storage-component.googleapis.com
    • storage-api.googleapis.com
    • compute.googleapis.com
    • container.googleapis.com
    • deploymentmanager.googleapis.com
    • cloudresourcemanager.googleapis.com
    • cloudkms.googleapis.com
    • sqladmin.googleapis.com
    • servicenetworking.googleapis.com
    • dns.googleapis.com
    • servicedirectory.googleapis.com
  • Create a service account called astronomer@astro-remote-mgmt.iam.gserviceaccount.com that Astro uses to access the data plane.

​
Provide setup information to Astronomer

Once you’ve activated your data plane, provide Astronomer with:
  • Your GCP project ID.
  • Your preferred Astro cluster name.
  • The GCP region that you want to host your cluster in.
  • Your preferred node instance type.
  • Your preferred CloudSQL instance type.
  • Your preferred maximum node count.
  • (Optional) Your custom CIDR ranges for connecting to Astronomer’s services.
If you don’t specify your organization’s preferred configurations, Astronomer creates a cluster in us-central1 with a node pool of e2-standard-4 nodes. For more information, see GCP resource reference.

​
Provide VPC peering information (Optional)

Astro supports Private Services Connect, which allows private consumption of services across VPC networks that belong to different projects or organizations. If you have created custom services that are not published using Private Services Connect, then you might want to peer with Astronomer. To set up peering, provide the following information to Astronomer:
  • VPC Name/ID and region for peering with Astronomer.
  • Google Cloud project ID of the target VPC.

​
Astronomer support creates the cluster

After you provide Astronomer support with the setup information for your organization, Astronomer support creates your first cluster on GCP. Wait for confirmation from Astronomer support that the cluster has been created before creating a Deployment. If you submitted a VPC peering request, you’ll need to accept the request from Astronomer after Astro is installed. To accept the request, see Use VPC Network Peering. When VPC peering with Astronomer is complete, configure and validate the following items to ensure successful network communications between Astro and your resources:

​
Create a Deployment and confirm the install

When Astronomer support confirms that your Astro cluster has been created, you can create a Deployment and start deploying dags. See Create a Deployment. To confirm a successful installation, in the Astro UI select a Workspace and on the Deployments page click Deployment. The Astro cluster created by Astronomer support appears as an option in the Cluster list.

​
Next steps