Product Documentation

Appearance

Deleting Stacks and Resources ​

Starting a new installation with a clean slate in your AWS environment is recommended. Before proceeding with a new installation, you need to delete the existing stack, its sub-stacks, and its resources. In theory, if the root stack itself has been successfully deleted, everything that it created must have been deleted. You can view deleted stacks by going to CloudFormation > Stacks > Deleted.

Note: Before deleting anything via the AWS Console, log into Yellowbrick Manager and delete your data warehouse instances (which in turn, will drop the clusters for each instance). If you do this first, you can avoid having to delete external storage volumes and buckets manually as part of the following procedure.

To create a new stack from a clean slate, find and delete the following stacks and resources:

  1. Delete the root stack first, and all nested sub-stacks. Wait for the deletion of each stack to finish before proceeding. (The root stack has the exact name you provided when you created the stack, and no suffix.)
  2. Empty and delete the observability bucket manually. (The delete will fail if the bucket is not empty. If the observability bucket files are important to keep for logging history, copy the files to another location.) Delete buckets by going to Amazon S3 > Buckets.
  3. Delete the region stack. Make sure this is deleted completely before deleting the account stack.
  4. Delete the account stack. Do not attempt to delete this stack before the others!
  5. Manually delete hosted zone records, except for the NS and SOA records at the top of the list. Keep these two. List and delete records by going to Route53 Dashboard > Hosted zone > View details.

Check for the existence of the following resources and delete them as required:

  • Roles created with the name yb-* (for example: yb-cdw-CopyZips). Delete roles by going to the IAM Dashboard > Roles.
  • Other S3 buckets associated with the stack, named yb*
  • EC2 storage volumes for CDWM. Delete volumes by going to EC2 Dashboard > Volumes. (Check that you are looking at the right region, or no volumes will be visible.)
  • Lambda functions with the name yb-*

Note that a VPC installation activates a set of AWS Quick Start (AWSQS) extensions. The AWSQS resource types remain after an installation and cannot be uninstalled.

Collisions between resources and files, if they occur at all, should only occur at the AWS account level, not across VPCs. You can use the same account and region to create multiple VPC stacks.

Parent topic:AWS VPC Deployment Guide for Yellowbrick