Em 15 de setembro de 2026, todos os ambientes do Cloud Composer 1 e da versão 2.0.x do Cloud Composer 2 vão atingir o fim da vida útil planejado e não poderão mais ser usados. Recomendamos planejar a migração para o Cloud Composer 3.
Para conferir uma lista dos serviços exigidos pelo Cloud Composer nas configurações do VPC Service Controls, consulte Configurar o VPC Service Controls.
Ativar o serviço do Cloud Composer
Nesta seção, descrevemos como ativar o serviço do Cloud Composer no projeto Google Cloud .
Antes de começar
Para ativar o serviço do Cloud Composer, você precisa ter as permissões
de Identity and Access Management corretas. Para saber mais sobre os requisitos do IAM
para o Service Usage, consulte a página "Service Usage"
para Controle de acesso.
Nesta seção, descrevemos como desativar o serviço do Cloud Composer no projeto Google Cloud .
Antes de começar
Para desativar o serviço do Cloud Composer, você precisa ter as permissões de
Identity and Access Management corretas. Para saber mais sobre os requisitos do IAM
para o Service Usage, consulte a página
do Service Usage para Controle de acesso.
Verifique se todos os ambientes do Cloud Composer no
projeto foram excluídos. Desativar a API exclui de forma irreversível as partes do projeto de locatário
de ambientes do Cloud Composer, e esses
ambientes se tornam inutilizáveis.
Para evitar cobranças extras, conclua os passos a seguir para cada
ambiente antes de desativar a API Cloud Composer:
Pause os DAGs.
Se necessário, exporte os dados do ambiente, como DAGs do bucket dele.
Exclua seu ambiente, incluindo os recursos que não são
excluídos automaticamente.
Desativar a API Cloud Composer
Para desativar o serviço do Cloud Composer:
Console
No console do Google Cloud , acesse a página da API Cloud Composer.
Use o método services.disable para desativar
a API composer.googleapis.com.
Terraform
Remova a configuração da API composer.googleapis.com. Normalmente,
o recurso google_project_service
é usado para configurar serviços do Google Cloud .
Serviços exigidos pelo Cloud Composer
Nesta seção, descrevemos os serviços necessários para o Cloud Composer. Em alguns casos, os administradores da organização ou do projeto podem restringir quais Serviços do Google podem ser usados nos projetos.
Os seguintes serviços são necessários para o Cloud Composer:
artifactregistry.googleapis.com
cloudbuild.googleapis.com
composer.googleapis.com
compute.googleapis.com
container.googleapis.com
logging.googleapis.com
cloudkms.googleapis.com, se você estiver usando chaves do Cloud KMS ou da CMEK
monitoring.googleapis.com
pubsub.googleapis.com
storage.googleapis.com
secretmanager.googleapis.com, se você estiver usando o Secret Manager
como um back-end de secrets
cloudresourcemanager.googleapis.com
servicedirectory.googleapis.com
Os serviços do Google, como o Cloud DNS ou o IAM, já são permitidos por padrão na maioria dos projetos.
Além disso, permita o uso de todos os serviços usados pelos seus DAGs, por exemplo:
bigquery.googleapis.com
dataflow.googleapis.com
datacatalog.googleapis.com
Você pode encontrar os nomes *.googleapis.com dos serviços nas páginas de API
vinculadas à página do API Explorer.
Suspensão de uso dos serviços que não são necessários para o Cloud Composer 3
Estamos planejando desativar gradualmente as APIs que não são necessárias para o Cloud Composer 3:
A partir de 27 de fevereiro de 2026, as APIs a seguir vão
se tornar totalmente separáveis. A desativação dessas APIs não causa a desativação da API Cloud Composer.
artifactregistry.googleapis.com
cloudbuild.googleapis.com
container.googleapis.com
pubsub.googleapis.com
sqladmin.googleapis.com
A partir de 27 de maio de 2026, essas APIs
não serão mais ativadas automaticamente quando você ativar a
API Cloud Composer. Para criar ambientes do Cloud Composer 2 em novos
projetos, o grupo de APIs separadas precisa ser ativado manualmente.
Os ambientes atuais do Cloud Composer 3 e do Cloud Composer 2 em projetos em que a API Cloud Composer já está ativada não serão afetados. Você pode fazer o
seguinte:
Depois de 27 de fevereiro de 2026, se o projeto tiver apenas ambientes do Cloud Composer 3, será possível desativar manualmente as APIs separadas.
Após 27 de fevereiro de 2026, se o projeto tiver ambientes do Cloud Composer 2, recomendamos manter essas APIs ativadas, porque a desativação delas pode causar mau funcionamento do ambiente.
Depois de 27 de maio de 2026, se você usar scripts de automação para provisionar ambientes do Cloud Composer 2, verifique se as APIs listadas estão ativadas, além da API Cloud Composer.
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 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)"]]
