El 15 de septiembre del 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 ver una lista de los servicios que necesita Cloud Composer en las configuraciones de Controles de Servicio de VPC, consulta Configurar Controles de Servicio de VPC.
Habilitar el servicio Cloud Composer
En esta sección se describe cómo habilitar el servicio Cloud Composer en tu proyecto de Google Cloud .
Antes de empezar
Para habilitar el servicio Cloud Composer, debes tener los permisos de Gestión de Identidades y Accesos correctos. Para obtener información sobre los requisitos de gestión de identidades y accesos de Uso de Servicios, consulta la página Uso de Servicios para Control de acceso.
En esta sección se describe cómo inhabilitar el servicio Cloud Composer en tu proyecto de Google Cloud .
Antes de empezar
Para inhabilitar el servicio Cloud Composer, debes tener los permisos de Gestión de Identidades y Accesos correctos. Para obtener información sobre los requisitos de gestión de identidades y accesos de Uso de Servicios, consulta la página Control de acceso.
Asegúrate de que se hayan eliminado todos los entornos de Cloud Composer de tu proyecto. Si inhabilitas la API, se eliminarán de forma irreversible las partes del proyecto de inquilino de los entornos de Cloud Composer, y estos entornos dejarán de poder usarse.
Para evitar cargos adicionales, sigue estos pasos en cada entorno antes de inhabilitar la API Cloud Composer:
Pausa los DAGs.
Si es necesario, exporta los datos del entorno, como los DAGs del segmento del entorno.
Elimina tu entorno, incluidos los recursos que no se eliminan automáticamente.
Inhabilitar la API de Cloud Composer
Para inhabilitar el servicio Cloud Composer, sigue estos pasos:
Consola
En la consola, ve a la página API Cloud Composer. Google Cloud
Usa el método services.disable para inhabilitar la API composer.googleapis.com.
Terraform
Elimina la configuración de la API composer.googleapis.com. Normalmente, se usa el recurso google_project_service para configurar servicios Google Cloud .
Servicios necesarios para Cloud Composer
En esta sección se describen los servicios que requiere Cloud Composer. En algunos casos, los administradores de organizaciones o proyectos 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
deploymentmanager.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 usen tus DAGs. Por ejemplo:
bigquery.googleapis.com
dataflow.googleapis.com
datacatalog.googleapis.com
Puede encontrar los nombres *.googleapis.com de los servicios en las páginas de las APIs
vinculadas desde la página Explorador de APIs.
Próxima retirada de los servicios que no son necesarios para Cloud Composer 3
Tenemos previsto retirar gradualmente las APIs que no necesita Cloud Composer 3:
A partir del 27 de febrero del 2026, las siguientes APIs se podrán separar por completo. La desactivación de estas APIs no provocará la desactivación de la API Cloud Composer.
artifactregistry.googleapis.com
cloudbuild.googleapis.com
container.googleapis.com
pubsub.googleapis.com
sqladmin.googleapis.com
A partir del 27 de mayo del 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 independientes debe habilitarse manualmente.
Los entornos de Cloud Composer 3 y Cloud Composer 2 que ya estén en proyectos en los que la API Cloud Composer esté habilitada no se verán afectados. Puedes hacer lo siguiente:
Después del 27 de febrero del 2026, si tu proyecto solo tiene entornos de Cloud Composer 3, puedes inhabilitar manualmente las APIs independientes.
Después del 27 de febrero del 2026, si tu proyecto tiene entornos de Cloud Composer 2, te recomendamos que mantengas estas APIs habilitadas, ya que inhabilitarlas podría provocar que los entornos no funcionen correctamente.
Después del 27 de mayo del 2026, si usas secuencias de comandos de automatización para aprovisionar entornos de Cloud Composer 2, asegúrate de que las APIs indicadas estén habilitadas, además de la API de Cloud Composer.
[[["Es fácil de entender","easyToUnderstand","thumb-up"],["Me ofreció una solución al problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Es difícil de entender","hardToUnderstand","thumb-down"],["La información o el código de muestra no son correctos","incorrectInformationOrSampleCode","thumb-down"],["Me faltan las muestras o la información 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 page outlines the process for enabling and disabling the Cloud Composer service within a Google Cloud project, highlighting the importance of proper IAM permissions and billing setup.\u003c/p\u003e\n"],["\u003cp\u003eEnabling the Cloud Composer API can be done through the Google Cloud console, the gcloud command-line tool, the API directly, or via Terraform, using the \u003ccode\u003egcloud services enable composer.googleapis.com\u003c/code\u003e command or its equivalents.\u003c/p\u003e\n"],["\u003cp\u003eDisabling the Cloud Composer API requires prior deletion of all environments and pausing of DAGs, and it is a permanent action, rendering environments unusable after completion, but still granting access to stored data.\u003c/p\u003e\n"],["\u003cp\u003eCloud Composer relies on several Google Cloud services, including \u003ccode\u003eartifactregistry.googleapis.com\u003c/code\u003e, \u003ccode\u003ecompute.googleapis.com\u003c/code\u003e, and \u003ccode\u003estorage.googleapis.com\u003c/code\u003e, among others, for its operation.\u003c/p\u003e\n"],["\u003cp\u003eThe Cloud Deployment Manager API will not be automatically enabled when you enable Cloud Composer API starting on April 14, 2025, as it will no longer be used by Cloud Composer.\u003c/p\u003e\n"]]],[],null,["\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\n[Cloud Composer 3](/composer/docs/composer-3/enable-composer-service \"View this page for Cloud Composer 3\") \\| [Cloud Composer 2](/composer/docs/composer-2/enable-composer-service \"View this page for Cloud Composer 2\") \\| **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-1/configure-vpc-sc).\n\nEnable the Cloud Composer service\n\nThis section describes how to enable the Cloud Composer service in\nyour Google Cloud project.\n\nBefore 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\nEnable Cloud Composer API \n\nConsole\n\nEnable the Cloud Composer API:\n\n\n```bash\ngcloud services enable composer.googleapis.com\n```\n\n\u003cbr /\u003e\n\ngcloud\n\nEnable the `composer.googleapis.com` API:\n\n\n```bash\ngcloud services enable composer.googleapis.com\n```\n\n\u003cbr /\u003e\n\nAPI\n\nUse the [`services.enable`](/service-usage/docs/reference/rest/v1/services/enable) method to enable\nthe `composer.googleapis.com` API.\n\nTerraform\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\nThis section describes how to disable the Cloud Composer service in\nyour Google Cloud project.\n\nBefore you begin **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-1/delete-environments), including the resources that are not deleted automatically.\n\nDisable Cloud Composer API\n\nTo disable the Cloud Composer service: \n\nConsole\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\ngcloud\n\nRun the [`gcloud services disable`](/sdk/gcloud/reference/services/disable) command: \n\n gcloud services disable composer.googleapis.com\n\nAPI\n\nUse the [`services.disable`](/service-usage/docs/reference/rest/v1/services/disable) method to disable\nthe `composer.googleapis.com` API.\n\nTerraform\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 **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- deploymentmanager.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\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- [Create environments](/composer/docs/composer-1/create-environments)\n- [Access control](/composer/docs/composer-1/access-control)"]]
