Cloud Composer 3 | Cloud Composer 2 | Cloud Composer 1
This page explains how to delete your Cloud Composer environment.
Resources that are not deleted automatically
Deleting your environment does not delete the following data in your project:
- Your environment's Cloud Storage bucket.
- Cloud Logging logs.
To avoid incurring charges to your Google Cloud account, export your data and delete the environment's bucket and Cloud Logging logs, as needed.
If you use alerting policies to monitor your environment's metrics, delete these policies before deleting your environment.
Delete a Cloud Composer environment
Delete the Cloud Composer environment:
In the Google Cloud console, go to the Environments page.
Select your environment and click Delete.
Wait until the environment is deleted.
Delete your environment's bucket. Cloud Composer does not delete the environment's bucket automatically.
In the Google Cloud console, go to the Storage > Browser page.
Select the environment's bucket and click Delete. For example, this bucket can be named
us-central1-example-environ-c1616fe8-bucket
.
Delete the Cloud Composer environment:
gcloud composer environments delete
ENVIRONMENT_NAME \ --locationLOCATION Replace:
ENVIRONMENT_NAME
with the name of the environment.LOCATION
with the region where the environment is located.
Delete your environment's bucket. Cloud Composer does not delete the environment's bucket automatically.
gcloud storage rm gs://
BUCKET_NAME --recursiveReplace:
BUCKET_NAME
with the name of your environment's bucket. For example, this bucket can be namedus-central1-example-environ-c1616fe8-bucket
.
To delete an environment, construct an environments.delete
API request with the environment ID.
To delete an environment using Terraform, remove the
Cloud Composer configuration from your overall resource
configuration and run terraform apply
.