Uninstalling Yuki and Cleaning Up Resources

This guide provides detailed steps for safely removing all configurations and installations related to the Yuki Proxy, including associated AWS and Snowflake components.

---

Step 1: Disconnect Yuki in the Application

• Log in to Yuki:

  • Visit the Yuki web interface and log into your account.

• Remove Connections:

  • Navigate to the Connections page within the Yuki dashboard.

  • Locate and select the connections you wish to remove.

  • Delete the connections. This action will automatically remove all warehouses provisioned by Yuki for these connections.

---

Step 2: Remove DNS Configuration

• Access the AWS Route 53 console.

• Delete any DNS records you created for the Yuki Proxy, especially those linked to the Load Balancer and EKS service.

---

Step 3: Delete AWS Resources

DNS Terraform Deletion

• In your terminal change directory to the Terraform/proxy-dns-record folder.

• Run the following command to destroy the DNS settings:

  terraform destroy

• Confirm the action when prompted. This step will remove the DNS configurations from AWS Route 53.

Main Terraform Deletion

• In your terminal change directory to the Terraform folder.

• Run the following command to destroy all resources managed by the main Terraform:

  terraform destroy -target=module.eks
  terraform destroy -target=module.vpc

• Confirm the action when prompted to delete all resources. This step will remove the AWS infrastructure such as EKS clusters, EC2 instances, Load Balancers, and any associated networking resources like VPCs and security groups.

Manual Cleanup

• If there are any resources that were manually created or not managed by Terraform, you need to delete them individually:

  • Go to the AWS Management Console.

  • Manually remove any leftover resources like additional Elastic IPs, orphaned snapshots, or security groups.

---

Step 4: Clean Up Snowflake Configurations

Removing Yuki Users and Roles

• Log into your Snowflake account.

• Run the following commands to remove the custom roles and users created for Yuki:

  REVOKE ROLE yuki_application_role FROM USER yuki_application;
  DROP USER IF EXISTS yuki_application;
  DROP ROLE IF EXISTS yuki_application_role;

Removing Grants and Privileges

• Ensure that any grants provided to the Yuki roles or users are revoked:

  REVOKE ALL PRIVILEGES ON ALL WAREHOUSES FROM ROLE yuki_application_role;
  REVOKE ALL PRIVILEGES ON ALL DATABASES FROM ROLE yuki_application_role;

---

Step 5: Verify and Close Accounts

• Check both AWS and Snowflake for any residual data or configurations that may need to be addressed.

• Consider closing any accounts or sub-accounts that were specifically created for operating Yuki if they are no longer needed.

---

Step 6: Switch Connection Strings Back to Snowflake

After the Yuki Proxy has been removed, all tools that were previously routed through Yuki must be pointed back to Snowflake directly.

For each tool that was configured to use the Yuki Proxy hostname, replace it with your original Snowflake hostname.

---

Final Thoughts

• Ensure that all data backups or necessary data migrations are completed before fully deleting and cleaning up resources.

• It's recommended to retain backup copies of configurations and data in case they are needed in the future.

By following these steps, you can effectively remove the Yuki Proxy setup and clean up all related resources in AWS and Snowflake, ensuring a clean slate and preventing unwanted costs or security loopholes.