How to destroy the Pinecone AWS Reference Architecture

The Pinecone AWS Reference Architecture: github.com/pinecone-io/aws-re... is the fastest way to go to production with high-scale use cases leveraging Pinecone's vector database.
This video is part of a series where we deploy, configure, and destroy the Reference Architecture end to end.
You can find the playlist dedicated to the Pinecone AWS Reference Architecture here: • Pinecone AWS Reference...
In this video, we destroy the Pinecone AWS Reference Architecture with Pulumi, which we had recently deployed via the 3-part video series in the same playlist.
Timestamps are linked below for easier navigation:
00:00 - 1:15 Why you need a jump host to access the persistence tier (database and microservices)
1:36 Following the bundled instructions on using a jump host with the Reference Architecture
2:00 Quick demo of what you can do via the jump host
2:10 Explaining what we're going to do in this video before we can run pulumi destroy
2:40 Unwinding the Security group changes we made to allow the jump host to access RDS
3:40 The settings we chose to give our jump host network connectivity to our RDS Postgres instance
4:25 Deleting the jump host inbound rule in the RDS security group
5:50 Terminating the EC2 jump host
7:03 Running pulumi destroy
7:58 The most common resource likely to get stuck during teardown
9:25 How the pulumi destroy command works with ECS clusters and services
10:20 Deleting custom VPC dependencies
10:39 Deleting NAT gateways
11:20 Deleting the custom VPC itself
12:00 A trick for cleaning up the custom VPC more quickly than waiting