Am 15. September 2026erreichen alle Cloud Composer 1- und Cloud Composer 2-Umgebungen der Version 2.0.x das geplante Ende des Lebenszyklus und können nicht mehr verwendet werden. Wir empfehlen, die Migration zu Cloud Composer 3 zu planen.
Auf dieser Seite wird erläutert, wie Sie Ihre Cloud Composer-Umgebung löschen.
Ressourcen, die nicht automatisch gelöscht werden
Durch das Löschen Ihrer Umgebung werden die folgenden Daten in Ihrem Projekt nicht gelöscht:
Cloud Storage-Bucket Ihrer Umgebung.
Cloud Logging-Logs.
Um Kosten für Ihr Google Cloud -Konto zu vermeiden, exportieren Sie Ihre Daten und löschen Sie den Bucket der Umgebung und die Cloud Logging-Logs nach Bedarf.
Wenn Sie Benachrichtigungsrichtlinien verwenden, um die Messwerte Ihrer Umgebung zu überwachen, löschen Sie diese Richtlinien, bevor Sie Ihre Umgebung löschen.
Der Cluster Ihrer Umgebung wird automatisch gelöscht.
Cloud Composer-Umgebung löschen
Console
Löschen Sie die Cloud Composer-Umgebung.
Rufen Sie in der Google Cloud Console die Seite Umgebungen auf.
Wählen Sie den Bucket der Umgebung aus und klicken Sie auf Löschen. Dieser Bucket kann beispielsweise us-central1-example-environ-c1616fe8-bucket heißen.
LOCATION durch die Region, in der sich die Umgebung befindet.
Löschen Sie den Bucket Ihrer Umgebung. Cloud Composer löscht den Bucket der Umgebung nicht automatisch.
gcloudstoragermgs://BUCKET_NAME--recursive
Ersetzen Sie:
BUCKET_NAME durch den Namen des Buckets Ihrer Umgebung. Dieser Bucket kann beispielsweise us-central1-example-environ-c1616fe8-bucket heißen.
API
Erstellen Sie eine API-Anfrage environments.delete mit der Umgebungs-ID, um eine Umgebung zu löschen.
Terraform
Wenn Sie eine Umgebung mit Terraform löschen möchten, entfernen Sie die Cloud Composer-Konfiguration aus Ihrer allgemeinen Ressourcenkonfiguration und führen terraform apply aus.
[[["Leicht verständlich","easyToUnderstand","thumb-up"],["Mein Problem wurde gelöst","solvedMyProblem","thumb-up"],["Sonstiges","otherUp","thumb-up"]],[["Schwer verständlich","hardToUnderstand","thumb-down"],["Informationen oder Beispielcode falsch","incorrectInformationOrSampleCode","thumb-down"],["Benötigte Informationen/Beispiele nicht gefunden","missingTheInformationSamplesINeed","thumb-down"],["Problem mit der Übersetzung","translationIssue","thumb-down"],["Sonstiges","otherDown","thumb-down"]],["Zuletzt aktualisiert: 2025-09-03 (UTC)."],[[["\u003cp\u003eDeleting a Cloud Composer environment does not automatically delete the associated Cloud Storage bucket or Cloud Logging logs, which may need to be manually deleted to avoid charges.\u003c/p\u003e\n"],["\u003cp\u003eIt is crucial to delete any alerting policies tied to your environment before deleting the environment itself.\u003c/p\u003e\n"],["\u003cp\u003eThe environment's GKE cluster is automatically deleted during the environment deletion process, and attempting to manually delete it beforehand will result in errors.\u003c/p\u003e\n"],["\u003cp\u003eAfter deleting the environment, users must also delete the associated Cloud Storage bucket manually via the console, gcloud or API, if it is no longer needed.\u003c/p\u003e\n"],["\u003cp\u003eDeleting the environment's bucket will permanently remove all data stored within it, including DAGs and plugins.\u003c/p\u003e\n"]]],[],null,["\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](/composer/docs/composer-2/delete-environments \"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\nThis page explains how to delete your Cloud Composer environment.\n\nResources that are not deleted automatically\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\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 **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\nConsole\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\ngcloud\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\nAPI\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\nTerraform\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- [Create environments](/composer/docs/composer-1/create-environments)\n- [Enable and disable Cloud Composer service](/composer/docs/composer-1/enable-composer-service)"]]
