El 15 de septiembre de 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.
En esta página, se explica cómo borrar tu entorno de Cloud Composer.
Recursos que no se borran automáticamente
Si borras el entorno, no se borrarán los siguientes datos de tu proyecto:
Es el bucket de Cloud Storage de tu entorno.
Registros de Cloud Logging
Para evitar que se apliquen cargos a tu cuenta de Google Cloud , exporta tus datos y borra el bucket del entorno y los registros de Cloud Logging, según sea necesario.
Si usas políticas de alertas para supervisar las métricas de tu
entorno, borra estas políticas antes de borrar el entorno.
El clúster de tu entorno se borra automáticamente
Borra un entorno de Cloud Composer
Console
Borra el entorno de Cloud Composer:
En la Google Cloud consola, ve a la página Environments.
[[["Fácil de comprender","easyToUnderstand","thumb-up"],["Resolvió mi problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Información o código de muestra incorrectos","incorrectInformationOrSampleCode","thumb-down"],["Faltan la información o los ejemplos que necesito","missingTheInformationSamplesINeed","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-08-29 (UTC)"],[[["\u003cp\u003eDeleting a Cloud Composer environment requires multiple steps, including deleting the environment itself and then separately deleting its associated Cloud Storage bucket.\u003c/p\u003e\n"],["\u003cp\u003eManually deleting the GKE cluster of a Cloud Composer environment before deleting the environment itself will result in an error, so it is important to delete the environment which handles the cluster deletion automatically.\u003c/p\u003e\n"],["\u003cp\u003eThe Cloud Storage bucket and Cloud Logging logs of a Cloud Composer environment are not automatically deleted when the environment is removed, and will need to be manually deleted to avoid continued charges.\u003c/p\u003e\n"],["\u003cp\u003eIf you have set up alerting policies for monitoring the environment, you should delete these policies before you delete the environment itself.\u003c/p\u003e\n"],["\u003cp\u003eCloud Composer allows the reuse of environment buckets by setting it as a custom bucket for a new environment, which can help preserve existing policies or CI/CD integrations.\u003c/p\u003e\n"]]],[],null,["# Delete Cloud Composer environments\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\n[Cloud Composer 3](/composer/docs/composer-3/delete-environments \"View this page for Cloud Composer 3\") \\| **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-2/use-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\nYour environment's cluster is deleted automatically\n---------------------------------------------------\n\n| **Warning:** Do not delete the GKE cluster of your environment manually. This happens automatically during the environment deletion. If you delete the cluster before the environment, then attempting to delete your environment results in an error. To fix this problem, see [Troubleshooting](/composer/docs/composer-1/known-issues#deleted-cluster).\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-2/create-environments)\n- [Enable and disable Cloud Composer service](/composer/docs/composer-2/enable-composer-service)"]]
