This document explains Cloud Composer pricing details. To see the pricing for other products, read the Pricing documentation. Disk size, machine type memory, and network usage are calculated in gigabytes (GB), where 1 GB is 230 bytes. This unit of measurement is also known as a gibibyte (GiB).
You can also use the Google Cloud Pricing Calculator to estimate the cost of using Cloud Composer.
Pricing is based on the size of a Cloud Composer environment and the duration the environment runs. Cloud Composer environments are billed at 10-minute intervals. The costs are calculated based on the number and size of web server nodes, database nodes and storage, and the amount of network egress.
Cloud Composer pricing is billed in addition to billing for the following services used to run and monitor environments and hold data.
- Google Kubernetes Engine nodes used for workers and schedulers in an environment. These nodes are subject to separate Compute Engine pricing based on the number and type of instances used. Persistent Disk used for Redis queue (this disk persists until manually deleted).
- The Cloud Storage bucket created by an environment for managing DAGs and holding task logs. This bucket persists unless manually deleted.
- The data that Cloud Monitoring collects to help you understand your environment's performance and health. By default, Monitoring is enabled, and the data is subject to separate Monitoring pricing.
- The storage and egress traffic generated when using Google Container Registry and Google Artifact Registry. These services are used to store and serve container images created when you install additional PyPi modules. The details can be found on the Container Registry pricing and Artifact Registry pricing pages.
- If you use Customer Managed Encryption Keys, there may be additional charges for the usage of the Cloud Key Management Service (KMS). See Google Key Management Service pricing for details.
Although some pricing is stated in hours or by the month, Cloud Composer is billed by the minute.
NOTE: The table below describes the price for Web Server when Cloud Composer is configured to run in Public IP mode. When you create Cloud Composer environment in Private IP mode the cost related to the Web Server doubles as Composer has two Web Server instances running behind the load balancer.
Supported machine types
Cloud Composer environments support the following Compute Engine instance types:
- N1 standard machine types (
- N1 high-memory machine types (
- N1 high-CPU machine types (
- N2 standard machine types (
- N2 high-memory machine types (
- N2 high-CPU machine types (
- E2 standard machine types (
- E2 high-memory machine types (
- E2 high-CPU machine types (
- C2 compute-optimized machine types (
- M1 memory-optimized machine types (
- M2 memory-optimized machine types (
- N2D standard machine types running on AMD processors (
- N2D high-memory machine types running on AMD processors (
- N2D high-CPU machine types running on AMD processors (
Shared-core machine types are not supported.
Supported machine types for the Cloud SQL instance running the Airflow database
At this time the following machines types are supported:
NOTE: the disk size of CloudSQL instances increases automatically, following the demand coming from the database storage usage.
Supported machine types for the VM instance running the Airflow web server
At this time the following machine types are supported:
|composer-n1-webserver-2||2||1.6 GB||20 GB|
|composer-n1-webserver-4||4||3.6 GB||20 GB|
|composer-n1-webserver-8||8||7.6 GB||20 GB|
The size of a Cloud Composer environment affects pricing for an environment. Some settings can be adjusted to change the size of Cloud Composer environments. Other settings are pre-set and cannot be adjusted.
|Worker machine type||n1-standard-1||Yes|
|Worker storage (GB per worker)||100||Yes|
Assume you create a Cloud Composer environment in Public IP mode
us-central1 (Iowa) and you do not adjust settings during the creation process.
Your environment uses the following resources.
In this example, your environment has 3 worker vCPUs: the default
machine type is an n1-standard-1 with 1 vCPU, and the default number of workers
is 3 (
3 workers * 1 vCPU = 3 vCPUs), The Airflow database runs in a Cloud SQL instance using the db-n1-standard-2 machine type, while composer-n1-webserver-2 is used to run the Airflow web server.
If this is a development environment that you run for 25% of one month (182 hours per month) with 6.5 GB of egress traffic, the total Cloud Composer monthly costs for this environment are:
|Database core hours||$45.66|
|Web core hours||$26.91|
|Web and database storage||$2.05|
|Total Cloud Composer cost||$76.06|
These charges are in addition to the Cloud Storage and Compute Engine charges for the GKE nodes used for DAG storage, the workers, and the scheduler.
NOTE: This section describes the cost of Composer working in Public IP mode. When you create Composer environment in Private IP mode the cost related to the Web Server doubles as Composer has two Web Server instances running behind the load balancer.
You can use the Google Cloud Pricing Calculator to estimate the cost of these workers.