Teardown Checklist

The following list contains the elements that need to be removed in case of a manual teardown of the infrastructure, to ensure a clean redeployment without errors.

Important note: The intended use of this list is meant only for non-production instances.

1. Confluent Cloud. The following resources should be manually removed by using the fallback account (KaaS Owner): - [ ] Environments & other resources (kafka cluster, schema registry, network) - [ ] Identity provider - [ ] Identity pools - [ ] Users - [ ] Service accounts
2. AWS: - [ ] State files in S3 buckets (Terraform state files of every affected setup - platform-pipeline, teams-provisioning-pipeline, application-pipeline. Note that application-pipeline has an S3 bucket for each environment. The other 2 pipelines use one bucket each for storing all the state files.) - [ ] Dynamodb tables(lock items related to every affected state file above) - [ ] KMS key alias & key (Delete Alias from the key by going to the key under "Aliases" tab) - [ ] Secrets. Despite setting the recovery window to 0 in the terraform resource block, deleting secrets manually in the UI with an immediate effect is not possible. To remove an old secret and free up the name for clean deployment, use AWS CLI with the following command:
   aws secretsmanager delete-secret --secret-id <Your-Secret-Name-Or-ARN> --force-delete-without-recovery
3. Others: - [ ] Clean up splunk logs - [ ] Clean up CIL - [ ] Remove tags