On September 15, 2026, all Cloud Composer 1 versions and versions 2.0.x of Cloud Composer 2 will reach their planned end of life. You will not be able to use environments with these versions. We recommend planning migration to Cloud Composer 3. Cloud Composer 2 versions 2.1.x and later are still supported and are not impacted by this change.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-25 UTC."],[[["\u003cp\u003eThis guide outlines the process for deleting a Cloud Composer environment, detailing steps for both console and command-line interface (gcloud) methods.\u003c/p\u003e\n"],["\u003cp\u003eDeleting a Cloud Composer environment does not automatically remove its associated Cloud Storage bucket or Cloud Logging logs, which must be deleted separately to avoid ongoing charges.\u003c/p\u003e\n"],["\u003cp\u003eBefore deleting the environment's bucket, it is important to note that it will also remove all contained objects, such as DAGs and plugins, with limited or no possibility of recovery.\u003c/p\u003e\n"],["\u003cp\u003eUsers employing alerting policies for environment monitoring should delete those policies prior to deleting the Cloud Composer environment.\u003c/p\u003e\n"],["\u003cp\u003eThere are alternative methods for deleting an environment, using the API or Terraform, which have the same considerations regarding the deletion of the associated Cloud Storage bucket.\u003c/p\u003e\n"]]],[],null,["# Delete Cloud Composer environments\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\n**Cloud Composer 3** \\| [Cloud Composer 2](/composer/docs/composer-2/delete-environments \"View this page for Cloud Composer 2\") \\| [Cloud Composer 1](/composer/docs/composer-1/delete-environments \"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\nThis page explains how to delete your Cloud Composer environment.\n\nResources that are not deleted automatically\n--------------------------------------------\n\nDeleting your environment does not delete the following data in your project:\n\n- Your environment's Cloud Storage bucket.\n- Cloud Logging logs.\n\nTo avoid incurring charges to your Google Cloud account, export your\ndata and [delete the environment's bucket](/storage/docs/deleting-buckets)\nand Cloud Logging logs, as needed.\n| **Note:** As an alternative, you can reuse your environment's bucket by specifying it [as a custom bucket](/composer/docs/composer-3/custom-bucket) for a new environment. For example, you can do so to preserve existing policies or CI/CD integrations.\n\nIf you use [alerting policies](/monitoring/alerts/manage-alerts) to monitor your\nenvironment's metrics, delete these policies before deleting your environment.\n\nDelete a Cloud Composer environment\n-----------------------------------\n\n### Console\n\n1. Delete the Cloud Composer environment:\n\n 1. In the Google Cloud console, go to the **Environments** page.\n\n [Go to Environments](https://console.cloud.google.com/composer/environments)\n 2. Select your environment and click **Delete**.\n\n 3. Wait until the environment is deleted.\n\n2. Delete your environment's bucket. Cloud Composer\n does not delete the environment's bucket automatically.\n\n | **Warning:** Deleting your environment's bucket deletes all objects stored within the bucket, such as DAGs and plugins. You might not be able to recover these objects, depending on the [bucket's settings](/storage/docs/soft-delete) and the length of time since the bucket was deleted.\n 1. In the Google Cloud console, go to the **Storage** \\\u003e\n **Browser** page.\n\n [Go to Storage \\\u003e Browser](https://console.cloud.google.com/storage/browser)\n 2. Select the environment's bucket and click **Delete** . For example, this\n bucket can be named `us-central1-example-environ-c1616fe8-bucket`.\n\n### gcloud\n\n1. Delete the Cloud Composer environment:\n\n gcloud composer environments delete \u003cvar translate=\"no\"\u003eENVIRONMENT_NAME\u003c/var\u003e \\\n --location \u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e\n\n Replace:\n - `ENVIRONMENT_NAME` with the name of the environment.\n - `LOCATION` with the region where the environment is located.\n2. Delete your environment's bucket. Cloud Composer\n does not delete the environment's bucket automatically.\n\n **Warning:** Deleting your environment's bucket deletes all objects stored within the bucket, such as DAGs and plugins. You might not be able to recover these objects, depending on the [bucket's settings](/storage/docs/soft-delete) and the length of time since the bucket was deleted. \n\n gcloud storage rm gs://\u003cvar translate=\"no\"\u003eBUCKET_NAME\u003c/var\u003e --recursive\n\n Replace:\n - `BUCKET_NAME` with the name of your environment's bucket. For example, this bucket can be named `us-central1-example-environ-c1616fe8-bucket`.\n\n### API\n\nTo delete an environment, construct an [`environments.delete`](/composer/docs/reference/rest/v1/projects.locations.environments/delete)\nAPI request with the environment ID.\n| **Caution:** Cloud Composer doesn't automatically delete the environment's bucket. If it's no longer needed, delete it manually.\n\n### Terraform\n\nTo delete an environment using Terraform, remove the\nCloud Composer configuration from your overall resource\nconfiguration and run `terraform apply`.\n| **Caution:** Cloud Composer does not automatically delete the environment's bucket. If it's no longer needed, delete it manually.\n\nWhat's next\n-----------\n\n- [Create environments](/composer/docs/composer-3/create-environments)\n- [Enable and disable Cloud Composer service](/composer/docs/composer-3/enable-composer-service)"]]