El 15 de septiembre de 2026, todos los entornos de Cloud Composer 1 y Cloud Composer 2 versión 2.0.x alcanzarán el final de su ciclo de vida previsto, y no podrás usarlos. Te recomendamos que planifiques la migración a Cloud Composer 3.
Para obtener una lista de los servicios que requiere Cloud Composer en las configuraciones de los Controles del servicio de VPC, consulta Configura los Controles del servicio de VPC.
Habilita el servicio de Cloud Composer
En esta sección, se describe cómo habilitar el servicio de Cloud Composer en tu Google Cloud proyecto.
Antes de comenzar
Para habilitar el servicio de Cloud Composer, debes tener los permisos adecuados de administración de identidades y accesos. A fin de obtener información sobre los requisitos de IAM para Service Usage, consulta la página de Service Usage sobre el Control de acceso.
Usa el método services.enable para habilitar la API de composer.googleapis.com.
Terraform
Usa el recurso google_project_service para configurar la API de composer.googleapis.com.
Inhabilita el servicio de Cloud Composer
En esta sección, se describe cómo inhabilitar el servicio de Cloud Composer en tu Google Cloud proyecto.
Antes de comenzar
Para inhabilitar el servicio de Cloud Composer, debes tener los permisos adecuados de administración de identidades y accesos. Si quieres obtener información sobre los requisitos de IAM para Service Usage, consulta la página de Service Usage sobre el Control de acceso.
Asegúrate de que se hayan borrado todos los entornos de Cloud Composer en tu proyecto. Si inhabilitas la API, se borrarán de forma irreversible las partes del proyecto de usuario de los entornos de Cloud Composer y estos entornos se volverán inutilizables.
A fin de evitar cargos adicionales, completa los siguientes pasos para cada entorno antes de inhabilitar la API de Cloud Composer:
Pausa los DAGs.
Si es necesario, exporta los datos del entorno, como los DAGs del bucket del entorno.
Borra tu entorno, incluidos los recursos que no se borran automáticamente.
Inhabilita la API de Cloud Composer
Para inhabilitar el servicio de Cloud Composer, sigue estos pasos:
Console
En la Google Cloud consola, ve a la página API de Cloud Composer.
Usa el método services.disable para inhabilitar la API de composer.googleapis.com.
Terraform
Quita la configuración de la API de composer.googleapis.com. Por lo general, debes usar el recurso google_project_service para configurar los servicios de Google Cloud .
Servicios requeridos por Cloud Composer
En esta sección, se describen los servicios que requiere Cloud Composer. En algunos casos, los administradores de la organización o del proyecto pueden restringir los servicios de Google que se pueden usar en sus proyectos.
Cloud Composer requiere los siguientes servicios:
artifactregistry.googleapis.com
cloudbuild.googleapis.com
composer.googleapis.com
compute.googleapis.com
container.googleapis.com
logging.googleapis.com
cloudkms.googleapis.com, si usas claves de Cloud KMS o CMEK
monitoring.googleapis.com
pubsub.googleapis.com
storage.googleapis.com
secretmanager.googleapis.com, si usas Secret Manager como backend de secretos
cloudresourcemanager.googleapis.com
servicedirectory.googleapis.com
Los servicios de Google, como Cloud DNS o IAM, ya están permitidos de forma predeterminada en la mayoría de los proyectos.
Además, permite usar todos los servicios que usan tus DAG, por ejemplo:
bigquery.googleapis.com
dataflow.googleapis.com
datacatalog.googleapis.com
Puedes encontrar los nombres *.googleapis.com de los servicios en las páginas de la API vinculadas desde la página del Explorador de APIs.
Próxima baja de los servicios que no requiere Cloud Composer 3
Tenemos previsto retirar gradualmente las APIs que no son necesarias para Cloud Composer 3:
A partir del 27 de febrero de 2026, las siguientes APIs se podrán separar por completo. La desactivación de estas APIs no provocará la desactivación de la API de Cloud Composer.
artifactregistry.googleapis.com
cloudbuild.googleapis.com
container.googleapis.com
pubsub.googleapis.com
sqladmin.googleapis.com
A partir del 27 de mayo de 2026, estas APIs ya no se habilitarán automáticamente cuando habilites la API de Cloud Composer. Para crear entornos de Cloud Composer 2 en proyectos nuevos, el grupo de APIs separadas se debe habilitar de forma manual.
Los entornos existentes de Cloud Composer 3 y Cloud Composer 2 en proyectos en los que ya está habilitada la API de Cloud Composer no se verán afectados. Puedes hacer lo siguiente:
Después del 27 de febrero de 2026, si tu proyecto solo tiene entornos de Cloud Composer 3, puedes inhabilitar manualmente las APIs separadas.
Después del 27 de febrero de 2026, si tu proyecto tiene entornos de Cloud Composer 2, te recomendamos que mantengas habilitadas estas APIs, ya que inhabilitarlas podría provocar un mal funcionamiento del entorno.
Después del 27 de mayo de 2026, si usas secuencias de comandos de automatización para aprovisionar entornos de Cloud Composer 2, asegúrate de que las APIs enumeradas estén habilitadas además de la API de Cloud Composer.
[[["Fácil de comprender","easyToUnderstand","thumb-up"],["Resolvió mi problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Información o código de muestra incorrectos","incorrectInformationOrSampleCode","thumb-down"],["Faltan la información o los ejemplos que necesito","missingTheInformationSamplesINeed","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-08-29 (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)"]]
