We have looked at a number of good processes, practices, and patterns for the AWS cloud. Now, we will explore some that you want to avoid. Some of the examples that follow are going to be countered by using the items in the first two sections. Others are not inherently technology problems. You should be aware of the smells that they bring and change course when you run into them. As your cloud craftsmanship improves, they will be easier to spot before implementation. At the beginning of your cloud journey, we expect failure to occur all the time. Be aware that refactoring is always going to be an option moving past your minimum viable product. Often, speed is the most important dimension to your product success. Taking on technical debt may be required to increase market shares or...





















































