Transcript For Introduction To AWS Well-Architected Framework

Uploaded by

Mamadou Sylla

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

34 views

Transcript For Introduction To AWS Well-Architected Framework

Uploaded by

Mamadou Sylla

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 2

PARTNER NETWORK

AWS Partner: Accreditation (Technical)

Transcript for AWS Well-Architected Framework video

Now that you can identify the appropriate application migration strategy based on a specific
customer use case or application, once the customer has migrated that workload, how can
you ensure that your customers are following AWS, architectural best practices?

Well, we have something for that, and it’s called the AWS Well-Architected Framework. This
body of knowledge brings together years of AWS Solutions Architects’ experience, across a
wide variety of business verticals and use cases.

Using the framework, customers can learn architectural best practices for designing and
operating reliable, secure, performant, and cost-effective systems in the cloud, all while
aiming to achieve customer’s sustainability goals.

The AWS Well Architected Framework provides a way to measure architectures against AWS
best practices and identify areas for improvement. Consider walking your customer through
the framework if their business goals encompass any of the following:

• They want to reduce their infrastructure spend.

• They want to pivot employees to more strategic work.
• They want to decrease unplanned downtime of application workloads.
• They want to decrease the time to market for new products.
• What is the AWS Well-Architected Framework based on?

The framework is divided into six areas of focus, referred to as the pillars of the AWS Well-
Architected Framework:

1. Operational excellence: This pillar focuses on improving the people and process
efficiency. Examples of this pillar include managing and automating changes,
responding to events, and defining standards to successfully manage daily operations.
2. Security: This pillar focuses on protecting data, information, and systems. Examples of
this pillar include providing least privilege access, credential management, protecting
systems, and establishing controls to detect security events and respond in an efficient
manner.
3. Reliability: This pillar focuses on designing highly available and resilient systems that
can handle component, service, or infrastructure events. This empowers your customer
to continue business operations in the face of unexpected events. Examples of this
pillar include foundational elements around setup, cross-project requirements,
recovery planning, and how we handle change.
4. Performance efficiency: The performance efficiency pillar focuses on using AWS
resources efficiently to meet business objectives, outcomes, and goals. Examples of this

AWS Partner: Accreditation (Technical)

pillar include selecting the right resource types and sizes based on workload
requirements, monitoring performance, and ensuring elasticity.
5. Cost optimization: This pillar focuses on maximizing the value of your current spend.
Examples include knowing where your money is spent, selecting the most appropriate
AWS resources for applications, and analyzing spend over time for long-term success.
6. Sustainability: This pillar focuses on minimizing the environmental impact of running
the cloud workloads. Examples of this pillar include understanding impact, and
maximizing utilization to minimize required resources and reduce downstream impacts.

You might be used to reviewing your customer’s architecture and documenting answers in a
PDF or spreadsheet. But that can limit your insight to measure the maturity of their
workloads and portfolios. By using the AWS Well-Architected Tool, customers can document
the maturity of their workloads and portfolios. They can then use that data to drive
investment and communicate application health.

Let’s say you worked with a customer to review an application workload using the AWS Well-
Architected Framework and the AWS Well-Architected Tool. This tool identifies issues and
assigns risk scores for their workloads. Based on these scores, you’re now better positioned to
advise where your customer should prioritize remediation efforts.

From these results, you can advise your customer to first address risks with straightforward
measures, like rewriting operating procedures and moving more of their infrastructure to
cloud-native services on AWS. For example, shifting a self-managed application stack more
toward AWS managed services will provide better scalability, performance, and availability,
while keeping cost under control. Another added benefit would be having more time
available to work on business logic, instead of managing infrastructure. With these
adjustments, customers can improve the risk score of their application’s design.

Using the AWS Well-Architected Framework, partners can gain expertise to build high-quality
solutions, implement best practices, and make improvements to meet customer’s business
outcomes. AWS Well-Architected review is an ongoing engagement with your customers,
providing you an opportunity to uncover additional business outcomes and potential revenue
for you as a partner.

For more information about AWS Well-Architected Framework, learn more by checking out
the resources provided at the end of this course. Thanks for learning with me, and I will see
you in the next video.