No one can know all the answers. The cloud is too big, and growing too fast, for anyone to be on top of all aspects of it. When AWS proposed the well-architected framework in a whitepaper during 2015, the goal was to provide an understanding of key differences between traditional IT environments and the cloud. Too often, folks would come onto AWS, which is a self-service platform, and deploy huge numbers of servers without thinking of the foundational practices that the cloud was built on.
The Well-Architected Review was so well received that in 2017, Amazon began bringing in consulting partners to help customers use the key best practices from the well-architected program. These partners can provide 'deep AWS knowledge and hands-on experience architecting, building, migrating, and optimizing architectures that follow the AWS Well-Architected Framework.'
Your AWS cloud infrastructure doesn't manage itself. You have to stay proactive and engaged in order to get the most out of it. If you feel like you've lost touch and are unsure about how to proceed, then consider these five reasons that companies engage partners to undertake a review.
To get an independent assessment of your infrastructure: You don't know what you don't know. Let people who have worked on multiple projects bring the lessons they have learned to your architecture. Reviews should be applied at key milestones in the product life cycle, as a matter of best practice.
To plan a migration or prepare your infrastructure to scale: Your assets are most vulnerable during a migration to the cloud. Don't do it without expert help and guidance. It can be used to refactor a workload ahead of a potential migration.
To tighten security controls ahead of an audit: In so doing, you are able to address foundational areas that are often neglected.
To reduce your AWS bill, or do more with your current budget: A well-architected review will provide a bird's eye overview of your project, show you where you are spending too much, and suggest ways to realign your assets in more cost-effective and affordable ways.
To modernize your existing AWS environment: You can build a backlog of potential improvements or develop a roadmap as you look to nurture a consistently evolving structure on your applications. No matter how well you structured your AWS environment, the passage of time makes a refresh necessary.
In no time at all, you'll be able to tell if you're optimizing workloads, so that you run more efficiently and cost-effectively. You'll mitigate any risks by having a better understanding of what the risks are as you build and optimize, and you'll come into contact with new AWS services that let you build and deploy workloads faster and respond to problems that require new solutions.