I’ve made this mistake twice now. This note & video as an attempt to stop a third time.
And in case it does happen again, I’m aware of the key resolution steps.
sst remove wasn’t even working at some point😂 that’s when I had to resort to manually deleting resources, which is generally frowned upon.
Overview of the fix
- Changed the web resource name, so I could generate new assets.
- Also changed the sst deployment stages.
- Deleted cloudflare DNS records
- Deleted AWS cloud front distributions
- I should probably delete the S3 buckets too, LOL
- Deleted origin access control rules
- The Discord server helped with this one
SST Discord
Very useful resource. For the most part, searching for your error message in the Discord will show you at least one other person who’s had the same issue, and what they tried.
Related Reading
- Reading list #4 has context on what terminal is.