Deleting a Deployment
Should you wish to delete a deployment, you can delete the AWS CloudFormation stacks that created the deployment as outlined in Deploy Privitar AWS. This will clear up most resources associated with the deployment.
This process does not automatically remove some resources, such as those that the application created or are sensitive, and these may have ongoing costs attached to them within AWS.
This following list details resources that an administrator may wish to remove manually within the AWS console. You can also remove some items through the Policy Manager prior to deleting a deployment, but this is not essential.
Caution
Please contact support@privitar.com if you are unsure about the impact of deleting any of the following resources.
Secrets stored in AWS Secrets Manager, such as the secret enabling the use of the Hash Text rule or a secret enabling SAML authentication (if enabled).
Warning
Deleting a secret will irreversibly prevent ongoing use of that secret in operations that require it.
Amazon DynamoDB tables storing tokenized values. These can be deleted through the AWS console or deleted within the Policy Manager prior to deleting a deployment.
Warning
Deletion of these tables deletes tokenized values and will irreversibly prevent any subsequent unmasking operations. This action deletes data.
AWS Glue jobs, including historical metadata. These can be deleted through the AWS console or within the Policy Manager prior to deleting a deployment.
Amazon S3 buckets used for instrumentation data (if enabled) and logs, for example. These can be deleted through the AWS console.
Amazon RDS snapshots containing database backups of the Config DB component. These can be deleted through the AWS console.