The first category we will explore is counterproductive processes. The cloud provides a whole new set of features that you can take advantage of. Migrating existing processes to your AWS-based product will work in most cases, but you will miss out on a great opportunity to make things better. Doing things the same way in the cloud will lead you back to where you are today. Consider how you add the greatest value for your customer before you spend time repeating what you did before the cloud existed.
The sections that follow cover processes that can be used, but probably shouldn't.
Wholesale migration of your existing systems, products, practices, and patterns to AWS is our first anti-pattern. You can do it, but seriously think about it. If your only objective is cost savings and you have no plans to ever change your product offerings, go for it. However, you will end up loading even more technical debt onto your teams. This will make it...