Amazon Web Services

WELL-ARCHITECTED
by TechX Corp.
WELL-ARCHITECTED REVIEW
1. Team TechX
2. Introduction to the Well-Architected Framework
3. Well-Architected Framework – Pillars
4. Implementation process
1. Team TechX

• Mr. KHOA THAN - Well-Architected Tech Lead

• Mr. HAI THAN - Well-Architected Senior Solutions Architect

• Mr. KHANG NGO - Well-Architected Project Manager

• Mr. HUY DINH - Well-Architected Account Manager

WELL-ARCHITECTED REVIEW
1. Team TechX
2. Introduction to the Well-Architected Framework
3. Well-Architected Framework – Pillars
4. Implementation process
 2. W-A Framework
A brief history of Well-Architected:
Framework
Questions Update, Serverless
Well-Architected across four Operational Self-service, Lens, Review
started pillars Excellence imp. plans Owner
2012 2014 2016 2018 2020

2013 2015 2017 2019

AWS SA Published APN partners, Regional
reviews framework lenses launches
2. W-A Framework
The main Benefits:

Build and Lower or Make Learn AWS

deploy faster mitigate risks informed best
decisions practices
WELL-ARCHITECTED REVIEW
1. Team TechX
2. Introduction to the Well-Architected Framework
3. Well-Architected Framework – Pillars
4. Implementation process
3. WAR Pillars
What is the AWS Well-Architected Framework?
The AWS Well-Architected Framework provides architectural best practices across the five pillars for designing
and operating reliable, secure, efficient, and cost-effective systems in the cloud. The framework provides a set
of questions that allows you to review an existing or proposed architecture. It also provides a set of AWS best
practices for each pillar.

Pillars Design Questions

principles
3. WAR Pillars
Pillars of AWS Well-Architected:

Operational Security Reliability Performance Cost

Excellence Efficiency Optimization
 3. WAR Pillars
Operational
Excellence

The Operational Excellence pillar includes: Design Principles:

the ability to support development and run • Perform operations as code
workloads effectively, gain insight into their • Make frequent, small, reversible changes
operation, and continuously improve • Refine operations procedures frequently
supporting processes and procedures to • Anticipate failure
delivery business value. • Learn from all operational failures
 3. WAR Pillars

Security

The Security pillar includes: Design Principles:

the ability to protect data, systems, and assets • Implement a strong identity foundation
to take advantage of cloud technologies to • Enable traceability
improve the security. • Apply security at all layers
• Automate security best practices
• Protect data in transit and at rest
• Keep people away from data
• Prepare for security events
 3. WAR Pillars

Reliability

The Reliability pillar includes: Design Principles:

the ability of a workload to perform its • Automatically recover from failure
intended function correctly and consistently • Test recovery procedures
when it’s expected to. • Scale horizontally to increase aggregate
workload availability
• Stop guessing capacity
• Manage change in automation
 3. WAR Pillars
Performance
Efficiency

The Performance Efficiency pillar includes: Design Principles:

the ability to use computing resources • Democratize advanced technologies
efficiently to meet system requirements, and • Go global in minutes
to maintain that efficiency as demand changes • Use serverless architectures
and technologies evolve. • Experiment more often
• Consider mechanical sympathy
 3. WAR Pillars
Cost
Optimization

The Operational Excellence pillar includes: Design Principles:

the ability to run systems to deliver business • Implement cloud financial management
value at the lowest price point. • Adopt a consumption model
• Measure overall efficiency
• Stop spending money on undifferentiated
heavy lifting
• Analyze and attribute expenditure
WELL-ARCHITECTED REVIEW
1. Team TechX
2. Introduction to the Well-Architected Framework
3. Well-Architected Framework – Pillars
4. Implementation process
4. WAR Process
Intent of WAR:

Not architecture Not a one-time

Not an audit astronauts check

WORKING PRAGMATIC, THROUGHOUT

TOGETHER TO PROVEN ADVICE LIFECYCLE
IMPROVE
4. WAR Process
1. Preparing:
• Determine the current architecture, framework, workload, applications, etc.
• Identify which Pillars that customer wants to focus on.
• Provide the IAM User with Policies/Permissions: ReadOnlyAccess và
WellArchitectedConsoleFullAccess for TechX.
2. Review Workshop:
• 2 to 4 hours in duration.
• The Solution Architect walks through the framework and asks questions concerning
architectural issues that require any additional clarification.
3. Read-out:
• TechX proposes the recommendations or the solution of remediation fixes.
4. Quick Wins:
• AWS & TechX encourage implementation of some of the proposed changes as soon as
possible, within a week or two after the review.
5. Follow Up Review:
• WAR are not a one-time event. WAR should be done about every 6 months.
TechX’s Contact
Technical Team: Point of Contact:
Mr. Khoa Than Mr. Khang Ngo
E: [email protected] E: [email protected]
P: 0933445516 P: 0908740711

Mr. Hai Than Mr. Huy

E: [email protected] E: [email protected]
P: 0933445526 P: 0913392098
Thank you!
by TechX Corp.