On cache invalidation and naming things - AWS has certainly had a hard time with the latter. Between the variety of instance types they offer and how long they're been around, there’s no consistency.
Whether starting a new service to run internally or reviewing something we have going, it’s always a struggle to find the right instance type for the needs. For example, there are three families (r, x, z) that optimize RAM in various ways in various combinations yet I always forget about the x and z variants.
We’ve been using this 'cheat sheet' internally and thought to share here for anyone else to use; pull requests welcome for updates. Check it out: https://github.com/wrble/public/blob/main/aws-instance-types.md