Le 15 septembre 2026, tous les environnements Cloud Composer 1 et Cloud Composer 2 version 2.0.x atteindront leur fin de vie prévue et vous ne pourrez plus les utiliser. Nous vous recommandons de planifier la migration vers Cloud Composer 3.
Pour obtenir la liste des services requis par Cloud Composer dans les configurations VPC Service Controls, consultez Configurer VPC Service Controls.
Activer le service Cloud Composer
Cette section explique comment activer le service Cloud Composer dans votre projet Google Cloud .
Avant de commencer
Pour activer le service Cloud Composer, vous devez disposer des autorisations Identity and Access Management appropriées. Pour en savoir plus sur les exigences Cloud IAM pour Service Usage, consultez la page Contrôle des accès sur la page Service Usage.
Utilisez la méthode services.enable pour activer l'API composer.googleapis.com.
Terraform
Utilisez la ressource google_project_service pour configurer l'API composer.googleapis.com.
Désactiver le service Cloud Composer
Cette section explique comment désactiver le service Cloud Composer dans votre projet Google Cloud .
Avant de commencer
Pour désactiver le service Cloud Composer, vous devez disposer des autorisations Identity and Access Management appropriées. Pour en savoir plus sur les exigences IAM pour Service Usage, consultez la page Contrôle des accès sur la page Service Usage.
Assurez-vous que tous les environnements Cloud Composer de votre projet sont supprimés. La désactivation de l'API supprime de manière irréversible les parties de projet locataire des environnements Cloud Composer, et ces environnements deviennent inutilisables.
Pour éviter des frais supplémentaires, effectuez les étapes ci-après pour chaque environnement avant de désactiver l'API Cloud Composer :
Mettez les DAG en veille.
Si nécessaire, exportez les données de l'environnement, telles que les DAG du bucket de l'environnement.
Utilisez la méthode services.disable pour désactiver l'API composer.googleapis.com.
Terraform
Supprimez la configuration de l'API composer.googleapis.com. Vous utilisez généralement la ressource google_project_service pour configurer les services Google Cloud .
Services requis par Cloud Composer
Cette section décrit les services requis par Cloud Composer. Dans certains cas, les administrateurs d'organisation ou de projet peuvent limiter les services Google utilisables dans leurs projets.
Les services suivants sont requis par Cloud Composer :
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 vous utilisez des clés Cloud KMS ou CMEK
monitoring.googleapis.com
pubsub.googleapis.com
storage.googleapis.com
secretmanager.googleapis.com, si vous utilisez Secret Manager comme backend secret
cloudresourcemanager.googleapis.com
servicedirectory.googleapis.com
Les services Google tels que Cloud DNS ou IAM sont déjà autorisés par défaut dans la plupart des projets.
De plus, autorisez l'utilisation de tous les services utilisés par vos DAG, par exemple :
bigquery.googleapis.com
dataflow.googleapis.com
datacatalog.googleapis.com
Vous trouverez les noms *.googleapis.com des services sur les pages d'API accessibles depuis la page API Explorer.
Arrêt prochain des services qui ne sont pas requis par Cloud Composer 3
Nous prévoyons d'abandonner les API qui ne sont pas requises par Cloud Composer 3 :
À partir du 27 février 2026, les API suivantes deviendront entièrement détachables. La désactivation de ces API n'entraînera pas la désactivation de l'API Cloud Composer.
artifactregistry.googleapis.com
cloudbuild.googleapis.com
container.googleapis.com
pubsub.googleapis.com
sqladmin.googleapis.com
À partir du 27 mai 2026, ces API ne seront plus activées automatiquement lorsque vous activerez l'API Cloud Composer. Pour créer des environnements Cloud Composer 2 dans de nouveaux projets, vous devez activer manuellement le groupe d'API détachées.
Les environnements Cloud Composer 3 et Cloud Composer 2 existants dans les projets où l'API Cloud Composer est déjà activée ne seront pas affectés. Vous pouvez effectuer les opérations suivantes :
Après le 27 février 2026, si votre projet ne comporte que des environnements Cloud Composer 3, vous pourrez désactiver manuellement les API dissociées.
Après le 27 février 2026, si votre projet comporte des environnements Cloud Composer 2, nous vous recommandons de laisser ces API activées, car leur désactivation pourrait entraîner un dysfonctionnement de l'environnement.
Après le 27 mai 2026, si vous utilisez des scripts d'automatisation pour provisionner des environnements Cloud Composer 2, assurez-vous que les API listées sont activées en plus de l'API Cloud Composer.
Sauf indication contraire, le contenu de cette page est régi par une licence Creative Commons Attribution 4.0, et les échantillons de code sont régis par une licence Apache 2.0. Pour en savoir plus, consultez les Règles du site Google Developers. Java est une marque déposée d'Oracle et/ou de ses sociétés affiliées.
Dernière mise à jour le 2025/08/29 (UTC).
[[["Facile à comprendre","easyToUnderstand","thumb-up"],["J'ai pu résoudre mon problème","solvedMyProblem","thumb-up"],["Autre","otherUp","thumb-up"]],[["Difficile à comprendre","hardToUnderstand","thumb-down"],["Informations ou exemple de code incorrects","incorrectInformationOrSampleCode","thumb-down"],["Il n'y a pas l'information/les exemples dont j'ai besoin","missingTheInformationSamplesINeed","thumb-down"],["Problème de traduction","translationIssue","thumb-down"],["Autre","otherDown","thumb-down"]],["Dernière mise à jour le 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,["# Enable and disable the Cloud Composer service\n\n\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---------------------------------\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-1/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- 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-------------------------------------------------------------------------\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-1/create-environments)\n- [Access control](/composer/docs/composer-1/access-control)"]]
