Safely deletes an Amazon Redshift cluster and all its dependent resources.
Archive-only workloads, migrating to Amazon RDS PostgreSQL, or cutting cloud costs often require deleting the entire Redshift cluster instead of simply dropping tables like Customers
or Orders
.Removing the cluster frees compute nodes, storage, and IAM roles.
Ensure you have awscli
v2 installed, an IAM user with redshift:DeleteCluster
and s3:PutObject
(for snapshots) permissions, and that no critical ETL jobs still point to the cluster.
Create a final, restorable copy with aws redshift create-cluster-snapshot --cluster-identifier ecommerce-prod --snapshot-identifier ecommerce-prod-final
.Snapshots allow tables such as OrderItems
or Products
to be restored later.
Run aws redshift delete-cluster
with either --skip-final-cluster-snapshot
or --final-cluster-snapshot-identifier
. The operation is asynchronous; use aws redshift describe-clusters
to confirm its status turns to deleting
and then disappears.
Check that the cluster no longer appears in describe-clusters
, the subnet group is unused, and CloudWatch alarms tied to the cluster have been removed.Finally, revoke or delete dedicated IAM roles.
Delete unused snapshots older than your retention policy, update connection strings in application code, and migrate any leftover S3 UNLOAD data to cost-effective storage classes.
.
Yes, restore from the final snapshot with aws redshift restore-from-cluster-snapshot
.
Small test clusters delete in minutes; multi-node production clusters can take 20-40 minutes.
No. Manual and final snapshots stay in your account until you delete them or they expire per your retention policy.