https://docs.aws.amazon.com/wellarchitected/latest/framework/wellarchitected-framework.pdf#welcome
Pillars
O - S - R - P -C - S
Operational Excellence -
- ability to support
- gain insights
Security
Reliability
- Perform its indented function when it's expected to
Performance Efficiency
- ability to use computing resources efficiently
Cost Optimization - improve sustainability
impacts by reducing energy consumption
- increasing efficiency by provisioned resources
Terms :
component
code/configuration and resources - deliver against requirement
Workload
set of component that deliver business value
Architecture
how component work together in a workload
Milestone
key changes in architecture as it evolves thru the product lifecycle
Technology portfolio
collection of workload to operate business
On Architecture : central team - not recommended by AWS
- Technical Architect (infrastructure),
- Solutions
Architect (software),
- Data Architect,
- Networking Architect,
- Security Architect
Instead :
AWS Distribute the capabilities rather than having central team
- Have practices (ways of doing things, process, standard) - put experts
- implement mechanisms that carry out automated checks to
ensure standards are being met
“Good intentions never work, you need good mechanisms to make anything happen” — Jeff
Bezos.
Leadership principles : https://www.amazon.jobs/en/principles?ref=wellarchitected-wp
Principles
- Stop guessing your capacity needs
- Test systems at production scale:
- Automate to make architectural experimentation easier
- Allow for evolutionary architectures
- Drive architectures using data
- Improve through game days:
Operational Excellence
- Perform operations as code
- implement your operations procedures as
code and automate their execution by triggering them in response to events
- Make frequent, small, reversible change
- Organization
• Prepare
• Operate
• Evolve
Security
- Implement a strong identity foundation
- Enable traceability
- 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
Security Definition
- Security
- Identity and Access Management
- Detection
- Infrastructure Protection
- Data Protection
- Incident Response
Reliability
Design Principles
- Automatically recover from failure:
- Test recovery procedures
- Scale horizontally to increase aggregate workload availability
- Replace one large resource with
multiple small resources to reduce the impact of a single failure
- Stop guessing capacity
- Manage change in automation
Foundations
• Workload Architecture
• Change Management
• Failure Management
Performance Efficiency
Democratize advanced technologies
Go global in minutes
Use serverless architectures
Selection
- Compute - application design, usage patterns, and
configuration settings
- Storage - (block, file, or
object), patterns of access (random or sequential), required throughput, frequency of access (online,
offline, archival), frequency of update (WORM, dynamic)
- Database - availability, consistency,
partition tolerance, latency, durability, scalability, and query capability
- Network -Latency, throughput requirements,
jitter, and bandwidth
Review
Cloud technologies are rapidly evolving and you must ensure that workload components are using the
latest technologies and approaches to continually improve performance.
Monitoring
System performance can degrade over time. Monitor system performance to identify degradation and
remediate internal or external factors, such as the operating system or application load.
Tradeoff -When architecting solutions, determining tradeoffs enables you to select an optimal approach Depending on
your situation, you could trade consistency, durability, and space for time or latency, to deliver higher
performance.
Cost Optimization
Implement Cloud Financial Management
Adopt a consumption model
Measure overall efficiency
Stop spending money on undifferentiated heavy lifting
Analyze and attribute expenditure
- Practice Cloud Financial Management
- Expenditure and usage awareness
- Cost-effective resources
- Manage demand and supply resources
- Optimize over time
Sustainability
Understand your impact
Establish sustainability goals
Maximize utilization
Anticipate and adopt new, more efficient hardware and software offerings
Use managed services
Reduce the downstream impact of your cloud workloads
- Region selection
- User behavior patterns
- Software and architecture patterns
- Data patterns
- Hardware patterns
- Development and deployment process
