NOTE: You only need to follow the steps in this section if you ran this workshop in your own AWS account. If you were at an AWS event where your AWS host provided an account using Event Engine, then those accounts will be automatically cleaned-up after the workshop and you do not need to complete this section.
While most resources created during this lab will incur very little additional expense if not removed, there are some exceptions to this. The SageMaker notebook, Glue development endpoint, and resources created by the CloudFormation template (such as the RDS server that we imported data from), all have underlying compute resources that you will be charged for as long as they continue to run.
Follow these steps to clean-up your AWS account:
Every AWS account can have one QuickSight user at no cost, so if you created a QuickSight user for the lab today and it is the only user in your account, then you can keep that user to experiment further with QuickSight.
However if you would like to delete your QuickSight account, navigate to the QuickSight service in the AWS management console, click on your username in the top right hand corner, and click Manage QuickSight.
On the left-hand side, click on Your subscriptions. This will confirm your free users and trial subscription. If you want to unsubscribe from QuickSight, on the left-hand side click on Account settings, and then click Unsubscribe. On the confirmation screen click Unsubscribe again.
NOTE: You may see a screen confirming that your unsubscribe request was successful, but that certain items could not be deleted. However, if the only items listed are IAM resources, there are no costs associated with IAM and so removal is not required to prevent charges, but you can delete these from the IAM console for the sake of account hygiene.
Navigate to the AWS Glue service in the AWS management console and click on Notebooks in the left-hand menu (under Dev Endpoints)
Click the tick box next to the notebook you created earlier (such as aws-glue-lab-notebook) then click Action / Stop
Once the notebook shows a status of stopped, click Action / Delete
On the left-hand menu, click on Dev endpoints. Click the tickbox to select the endpoint you created earlier (such as datalake-lab-endpoint) and then click Action / Delete
Navigate to the Amazon S3 service in the AWS management console
Click the checkbox to select the bucket you created for the QuickStart lab (such as datalake-lab-sales-data-
Click the checkbox to select the data lake bucket that was created by Cloud Formation (such as lf-data-lake-bucket-xxxxxxxxxxxx), and then click Empty. Type the name of the bucket to confirm. This may take a few minutes to complete.
Note that if the bucket is not empty, CloudFormation will fail when trying to delete it, which is why we are emptying it now ourselves.
LOG-OUT of the AWS management console as user lf-admin
Log back into the AWS management console as your original administrative user.
If you fail to do this step then the deletion of the Cloud Formation template will fail.
Navigate to the Cloud Formation service in the AWS management console
Click the selector next to the template you deployed for the first lab (such as Lake-Formation) and then click Delete. Click Delete Stack to acknowledge that deleting the stack will delete the resources that the stack initially created.
NOTE: This will delete the RDS database server containing the original TPC data that we imported using the Lake Formation Blueprint, as well as resources such as a NAT gateway. If this step is not completed, you will be billed for these resources on an on-going basis.