There can be different perspectives on objectives depending on who you talk to in an organization. These perspectives are not necessarily conflicting with each other, but it is important to understand them well to approach your decision-making whether from a business, architecture, or operation's perspective. For example, the business perspective could be to pay as little as possible for whatever is used. Architectural goals may direct you toward avoiding waste as much as possible while achieving a more scalable and robust architecture for your applications. Similarly, operational goals may want you to focus on reducing the number of custom-developed components to be managed while using AWS services where possible to the maximum extent possible, thereby, minimizing the time and effort spent toward managing and maintaining the infrastructure and enabling more time to be spent on the business of the organization and/or to innovate.