Enabling and Disabling Cloud Composer

This page explains how to enable or disable Cloud Composer for your Google Cloud Platform project. For information about service usage on GCP, see Enabling and Disabling Services.

Before you begin

  • You must have the Owner permission to enable and disable the Cloud Composer API. For more information about roles and permissions, see Access Control.
  • To avoid additional charges, complete the following steps for each environment before you disable the Cloud Composer API.

    • Delete your environment and delete the Cloud Storage bucket for the environment. Otherwise, you are billed for Cloud Composer resources.
    • Wait until in-progress environment operations have completed; operations include creating, updating, or deleting an environment.
    • Wait until all DAGs are no longer running.
  • If you disable the Cloud Composer API, environments become unusable within an hour of service deactivation unless you re-enable the API. If you re-enable the API, you are billed for the service usage that occurs while the Cloud Composer service is deactivating.

Enabling Cloud Composer

Before using Cloud Composer, you must create a GCP project and enable billing.

You can use an existing project with Cloud Composer or create a new one. If you are using an existing project, you need to enable the Cloud Composer API. To create a project and enable the Cloud Composer API:

  1. In the GCP Console, select or create a project.
  2. Make sure that billing is enabled for your project.
  3. To activate the Cloud Composer API in a new or existing project, go to the API Overview page for Cloud Composer.
  4. Click Enable.

Disabling Cloud Composer

  1. In the GCP Console, select the project to disable the Cloud Composer API in.
  2. Go to the API Overview page for Cloud Composer.
  3. Click Manage.
  4. Click Disable API.
Was this page helpful? Let us know how we did:

Send feedback about...

Cloud Composer