The third pillar of the AWS Well-Architected Framework is reliability. It deals with ensuring that your workloads and applications produce the same results every time. Show
Using the five design principles of the reliability pillar, you can create workloads and applications that are reliable for their entire lifecycle. Automatically Recover From Failure You can also set up automatic recovery systems that your monitoring systems trigger when there’s a problem. To prepare as much as possible for failure, you can set up systems that track trends, meaning they can predict future problems. Test Recovery Procedures It’s also possible to use automation to recreate past failures. If you’re unsure of exactly where a failure occurred, a recreation can help you determine causes and ensure it doesn’t happen again. Scale Horizontally Ensure you spread out your requests across the smaller resources so they don’t share a common failure. Don’t Guess Capacity Use AWS tools to monitor the demands placed on your workload and its saturation level. Create systems that automatically reduce demands when your workload approaches saturation. Manage Change Changes made to automatic systems should be tracked and reviewed, preferably by another automated system. Work with an AWS Well-Architected Partner After performing a Well-Architected Review, we can identify any non-compliance issues and mitigate them for you. This blog post is part of a series about the AWS Well-Architected Framework, what it is, why it makes sense, and how we at kreuzwerker do it. In this entry, we will focus on the Reliability Pillar. What it is - A quick recapUsing their architects’ and clients’ collective knowledge and experience, AWS is continuously working on a Well-Architected Framework, which consists of key concepts, design principles, and best practices for architecting and running workloads in the AWS Cloud. AWS developed a Well-Architected Framework to understand what makes some customers succeed in the cloud while others fail. They also wanted to identify common problems, decisional and architectural patterns, and anti-patterns. In other words, what is Well-Architected and what is not, and to make this knowledge available to all, regardless of whether someone is just considering migrating to the cloud or is already running thousands of workloads there? The Well-Architected Framework is built on six pillars
The AWS Well-Architected Review process provides a consistent approach for customers and partners to evaluate architectures and implement scalable designs. It is based on the previously mentioned six pillars. It’s important to note that the Well-Architected Review is not an audit. It’s nothing to be afraid of; there are no penalty points for not getting things right the first time. A Well-Architected Review is a way of working together to improve your architecture. The process leads through several foundational questions and checks. It has been derived from years of experience working with the AWS cloud regarding security, cost efficiency, and performance. Hence, it provides sound advice on improvements. It helps you to build secure, high-performing, resilient, and efficient infrastructure for your applications and workloads. The hard facts about AWS Well-Architected reviews in 2022 are:
We describe the process from our perspective in more detail here. How we do it at kreuzwerker
As a Well-Architected partner, we do at least 20 well-architected reviews per year and have built overall deep architectural expertise for every pillar and hands-on experience.
For us, it’s an interactive process: we inspect and adapt every time we do it by requesting feedback from our clients and doing a short internal retrospective. As of now, we perform it as follows:
We do not just handle the questioning but give guidance to answering them.We can tell you how and why there could be improvements to be made. Reliability PillarIt is about the ability of a workload to perform correctly and consistently in its intended way. This includes operating and testing the workload through its total lifecycle. In a nutshellWe all want our workloads to be reliable, available 99,9…9% of the time, and to prevent failure. And if failures do occur, then handle them gracefully. Like Netflix says
Achieving this is all about the foundations, how you architect your workload, how you apply and monitor changes, and how your workload detects and handles failures. It depends on
After summarizing this pillar from our point of view, let’s talk briefly about the design principles that navigate us through each pillar. Design principlesAll pillars have their design principles, and they guide us through them. For the reliability pillar, they are as follows:
Improvement processThe architectural improvement process includes understanding what you already have and what you can do to improve the current state of your workload architecture. It selects targets for improvement, tests and adapts them, and quantifies your success. Afterward, you share what you have learned so that it can be replicated elsewhere, and then you repeat the cycle ♻️
ConclusionBased on the pillar principles and improvement process, our conclusion is:
Take care, and the final words are: we’re happy to perform an AWS Well-Architected Review with you and tackle those issues together. You want to know more about the AWS Well-Architected Framework, here are the other parts of our series: Which of the following are design principles for reliability in AWS cloud?Design Principles
Implement a strong identity foundation. Enable traceability. Apply security at all layers. Automate security best practices.
What are the design principles that increase reliability?Reliability principles. Define your reliability goals.. Build observability into your infrastructure and applications.. Design for scale and high availability.. Create reliable operational processes and tools.. Build efficient alerts.. Build a collaborative incident management process.. Which of the following AWS services are part of the AWS Foundation Services for the reliability pillar of the well architected framework in AWS cloud?Reliability
There are four best practice areas and tools for reliability in the cloud: Foundations – IAM, Amazon VPC, AWS Trusted Advisor, AWS Shield. Change Management – AWS CloudTrail, AWS Config, Auto Scaling, Amazon CloudWatch. Failure Management – AWS CloudFormation, Amazon S3, AWS KMS, Amazon Glacier.
Which of the following are principles of correct cloud design?There are 6 principles of cloud computing architecture design, including reasonable deployment, business continuity, elastic expansion, performance efficiency, security compliance, and continuous operation.
|