On September 15, 2026, all Cloud Composer 1 versions and versions 2.0.x of Cloud Composer 2 will reach their planned end of life. You will not be able to use environments with these versions. We recommend planning migration to Cloud Composer 3. Cloud Composer 2 versions 2.1.x and later are still supported and are not impacted by this change.
For a list of services required by Cloud Composer in
VPC Service Controls configurations, see Configure VPC Service Controls.
Enable the Cloud Composer service
This section describes how to enable the Cloud Composer service in
your Google Cloud project.
Before you begin
To enable the Cloud Composer service, you must have the correct
Identity and Access Management permissions. To learn about the IAM
requirements for Service Usage, see Service Usage page
for Access Control.
This section describes how to disable the Cloud Composer service in
your Google Cloud project.
Before you begin
To disable the Cloud Composer service, you must have the correct
Identity and Access Management permissions. To learn about the IAM
requirements for Service Usage, see the Service Usage
page for Access Control.
Make sure that all Cloud Composer environments in
your project are deleted. Disabling the API irreversibly deletes tenant
project parts of Cloud Composer environments, and these
environments become unusable.
To avoid additional charges, complete the following steps for each
environment before you disable the Cloud Composer API:
Pause the DAGs.
If required, export the environment's data, such as DAGs from the
environment's bucket.
Use the services.disable method to disable
the composer.googleapis.com API.
Terraform
Remove the configuration for the composer.googleapis.com API. You usually
use the google_project_service
resource to configure Google Cloud services.
Services required by Cloud Composer
This section describes services that are required by
Cloud Composer. In some cases, organization or project
administrators can restrict what Google services can be used in their projects.
The following services are required by Cloud Composer:
artifactregistry.googleapis.com
cloudbuild.googleapis.com
composer.googleapis.com
compute.googleapis.com
container.googleapis.com
logging.googleapis.com
cloudkms.googleapis.com, if you are using Cloud KMS or CMEK keys
monitoring.googleapis.com
pubsub.googleapis.com
storage.googleapis.com
secretmanager.googleapis.com, if you are using Secret Manager
as a secret backend
cloudresourcemanager.googleapis.com
servicedirectory.googleapis.com
Google services like Cloud DNS or IAM are already
allowed by default in most projects.
In addtion, allow using all services that your DAGs are using, for example:
bigquery.googleapis.com
dataflow.googleapis.com
datacatalog.googleapis.com
You can find the *.googleapis.com names of the services in API pages
linked from the API Explorer page.
Upcoming deprecation of services that aren't required by Cloud Composer 3
We're planning to phase out the APIs that aren't required by Cloud Composer 3:
Starting February 27, 2026, the following APIs will
become fully detachable. Deactivating these APIs won't cause the
deactivation of the Cloud Composer API.
artifactregistry.googleapis.com
cloudbuild.googleapis.com
container.googleapis.com
pubsub.googleapis.com
sqladmin.googleapis.com
Starting May 27, 2026, these APIs
will no longer be enabled automatically when you enable the
Cloud Composer API. To create Cloud Composer 2 environments in new
projects, the group of detached APIs must be enabled manually.
Existing Cloud Composer 3 and Cloud Composer 2 environments in projects where
the Cloud Composer API is already enabled won't be impacted. You can do the
following:
After February 27, 2026, if your project has only Cloud Composer 3
environments, then you can manually disable the detached APIs.
After February 27, 2026, if your project has
Cloud Composer 2 environments, then we recommend keeping these APIs
enabled because disabling them might lead to environment's malfunction.
After May 27, 2026, if you use automation scripts to provision
Cloud Composer 2 environments, then make sure that the listed APIs are
enabled in addition to the Cloud Composer API.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-25 UTC."],[[["\u003cp\u003eThis document provides instructions on how to enable and disable the Cloud Composer service within a Google Cloud project.\u003c/p\u003e\n"],["\u003cp\u003eEnabling the Cloud Composer API can be achieved through the Google Cloud console, \u003ccode\u003egcloud\u003c/code\u003e command-line tool, API methods, or Terraform, requiring proper Identity and Access Management permissions and billing to be enabled.\u003c/p\u003e\n"],["\u003cp\u003eDisabling the Cloud Composer API is irreversible and will result in environments becoming unusable, even though data in environment buckets will remain accessible; therefore it is important to pause DAGs, export data if needed, and delete environments beforehand.\u003c/p\u003e\n"],["\u003cp\u003eCloud Composer requires several Google services to function, including \u003ccode\u003eartifactregistry.googleapis.com\u003c/code\u003e, \u003ccode\u003ecompute.googleapis.com\u003c/code\u003e, and \u003ccode\u003estorage.googleapis.com\u003c/code\u003e, and additional services may be necessary depending on the DAGs in use, such as \u003ccode\u003ebigquery.googleapis.com\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThe Cloud Deployment Manager API will not be automatically enabled when you enable Cloud Composer API starting April 14, 2025, as it is not used by the Cloud Composer service.\u003c/p\u003e\n"]]],[],null,["# Enable and disable the Cloud Composer service\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\n**Cloud Composer 3** \\| [Cloud Composer 2](/composer/docs/composer-2/enable-composer-service \"View this page for Cloud Composer 2\") \\| [Cloud Composer 1](/composer/docs/composer-1/enable-composer-service \"View this page for Cloud Composer 1\")\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nThis page explains how to enable and disable the Cloud Composer service\nin your Google Cloud project.\n\nFor information about services management on Google Cloud, see\n[Enabling and Disabling Services](/service-usage/docs/enable-disable).\n\nFor a list of services required by Cloud Composer in\nVPC Service Controls configurations, see [Configure VPC Service Controls](/composer/docs/composer-3/configure-vpc-sc).\n\nEnable the Cloud Composer service\n---------------------------------\n\nThis section describes how to enable the Cloud Composer service in\nyour Google Cloud project.\n\n### Before you begin\n\n- To enable the Cloud Composer service, you must have the correct\n [Identity and Access Management](/iam) permissions. To learn about the IAM\n requirements for Service Usage, see Service Usage page\n for [Access Control](/service-usage/docs/access-control).\n\n- Make sure that [billing is enabled](/billing/docs/how-to/modify-project) in your project.\n\n### Enable Cloud Composer API\n\n### Console\n\nEnable the Cloud Composer API:\n\n\n```bash\ngcloud services enable composer.googleapis.com\n```\n\n\u003cbr /\u003e\n\n### gcloud\n\nEnable the `composer.googleapis.com` API:\n\n\n```bash\ngcloud services enable composer.googleapis.com\n```\n\n\u003cbr /\u003e\n\n### API\n\nUse the [`services.enable`](/service-usage/docs/reference/rest/v1/services/enable) method to enable\nthe `composer.googleapis.com` API.\n\n### Terraform\n\nUse the [`google_project_service`](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/google_project_service)\nresource to configure the `composer.googleapis.com` API.\n| **Important:** If you disable the BigQuery API, your Cloud Composer environment stops working. This happens because Google Kubernetes Engine depends on BigQuery and Cloud Composer inherits this dependency from the Google Kubernetes Engine API.\n\nDisable the Cloud Composer service\n----------------------------------\n\nThis section describes how to disable the Cloud Composer service in\nyour Google Cloud project.\n\n### Before you begin\n\n| **Warning:** You cannot recover environments in your project after you disable the Cloud Composer API. After the API is disabled, you still have access to data stored in your environment's buckets, but the environments themselves are no longer usable.\n\n- To disable the Cloud Composer service, you must have the correct\n [Identity and Access Management](/iam) permissions. To learn about the IAM\n requirements for Service Usage, see the Service Usage\n page for [Access Control](/service-usage/docs/access-control).\n\n- Make sure that all Cloud Composer environments in\n your project are deleted. Disabling the API irreversibly deletes tenant\n project parts of Cloud Composer environments, and these\n environments become unusable.\n\n- To avoid additional charges, complete the following steps for each\n environment before you disable the Cloud Composer API:\n\n 1. Pause the DAGs.\n 2. If required, export the environment's data, such as DAGs from the environment's bucket.\n 3. [Delete your environment](/composer/docs/composer-3/delete-environments), including the resources that are not deleted automatically.\n\n### Disable Cloud Composer API\n\nTo disable the Cloud Composer service: \n\n### Console\n\n1. In the Google Cloud console, go to the **Cloud Composer API**\n page.\n\n [Go to Cloud Composer API](https://console.cloud.google.com/apis/library/composer.googleapis.com)\n2. Click **Manage**.\n\n3. Click **Disable API**.\n\n### gcloud\n\nRun the [`gcloud services disable`](/sdk/gcloud/reference/services/disable) command: \n\n gcloud services disable composer.googleapis.com\n\n### API\n\nUse the [`services.disable`](/service-usage/docs/reference/rest/v1/services/disable) method to disable\nthe `composer.googleapis.com` API.\n\n### Terraform\n\nRemove the configuration for the `composer.googleapis.com` API. You usually\nuse the [`google_project_service`](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/google_project_service)\nresource to configure Google Cloud services.\n\nServices required by Cloud Composer\n-----------------------------------\n\n| **Upcoming deprecation:** We're planning to [phase out the APIs](#api-deprecation) that aren't required by Cloud Composer 3\n\nThis section describes services that are required by\nCloud Composer. In some cases, organization or project\nadministrators can restrict what Google services can be used in their projects.\n\nThe following services are required by Cloud Composer:\n\n- artifactregistry.googleapis.com\n- cloudbuild.googleapis.com\n- composer.googleapis.com\n- compute.googleapis.com\n- container.googleapis.com\n\n- logging.googleapis.com\n\n- cloudkms.googleapis.com, if you are using Cloud KMS or CMEK keys\n\n- monitoring.googleapis.com\n\n- pubsub.googleapis.com\n\n- storage.googleapis.com\n\n- secretmanager.googleapis.com, if you are using Secret Manager\n as a secret backend\n\n- cloudresourcemanager.googleapis.com\n\n- servicedirectory.googleapis.com\n\nGoogle services like Cloud DNS or IAM are already\nallowed by default in most projects.\n\nIn addtion, allow using all services that your DAGs are using, for example:\n\n- bigquery.googleapis.com\n- dataflow.googleapis.com\n- datacatalog.googleapis.com\n\nYou can find the \\*.googleapis.com names of the services in API pages\nlinked from the [API Explorer page](https://developers.google.com/apis-explorer).\n\nUpcoming deprecation of services that aren't required by Cloud Composer 3\n-------------------------------------------------------------------------\n\nWe're planning to phase out the APIs that aren't required by Cloud Composer 3:\n\n- Starting **February 27, 2026** , the following APIs will\n **become fully detachable**. Deactivating these APIs won't cause the\n deactivation of the Cloud Composer API.\n\n - artifactregistry.googleapis.com\n - cloudbuild.googleapis.com\n - container.googleapis.com\n - pubsub.googleapis.com\n - sqladmin.googleapis.com\n- Starting **May 27, 2026** , these APIs\n **will no longer be enabled automatically** when you enable the\n Cloud Composer API. To create Cloud Composer 2 environments in new\n projects, the group of detached APIs must be enabled manually.\n\nExisting Cloud Composer 3 and Cloud Composer 2 environments in projects where\nthe Cloud Composer API is already enabled won't be impacted. You can do the\nfollowing:\n\n- After **February 27, 2026**, if your project has only Cloud Composer 3\n environments, then you can manually disable the detached APIs.\n\n- After **February 27, 2026**, if your project has\n Cloud Composer 2 environments, then we recommend keeping these APIs\n enabled because disabling them might lead to environment's malfunction.\n\n- After **May 27, 2026**, if you use automation scripts to provision\n Cloud Composer 2 environments, then make sure that the listed APIs are\n enabled in addition to the Cloud Composer API.\n\nWhat's next\n-----------\n\n- [Create environments](/composer/docs/composer-3/create-environments)\n- [Access control](/composer/docs/composer-3/access-control)"]]
