Cloud Architecture Flashcards
AWS Well-Architected Framework
Guide for designing infrastructures
Well-Architected Framework: Operational Excellence
Run/monitor systems to deliver business value
Principles:
- Perform operations as code
- Annotate documentation
- Make frequent, small, reversible changes
- refine operations procedures frequently
- anticipate failure
- learn from all operational events and failures
Best Practice Areas
- Prepare
- Operate
- Evolve
Well-Architected Framework: Security
Protect information, systems, and assets
Principles:
- 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
Best Practice Areas:
- Identity and Access Management
- Detective controls
- Infrastructure protection
- Data protection
- Incident response
Well-Architected Framework: Reliability
Prevent and quickly recover from failures
Design Principles:
- test recovery procedures
- automatically recover from failure
- scale horizontally to increase aggregate system availability
- stop guessing capacity
- manage change in automation
Best Practices:
- Foundations
- Change Management
- Failure Management
Well-Architected Framework: Performance Efficiency
Use IT/Computing resources efficiently to meet system requirements
Design Principles
- Democratize advanced technologies
- go global in minutes
- use serverless architectures
- experiment more often
- have mechanical sympathy
Best Practices
- Selection
- Review
- Monitoring
- Tradeoffs
Well-Architected Framework: Cost Optimization
run systems to deliver business value at lowest price point
Design Principles
- adopt a consumption model
- measure overall efficiency
- stop spending money on data center operations
- analyze and attribute expenditure
- use managed and applicaiton-level services to reduce cost of ownership
Best Practices
- Expenditure awareness
- Cost-effective resources
- Matching supply and demand
- Optimizing over time
Reliability
Measure of system’s ability to provide functionality when desired by the user.
MTBF = Mean Time Between Failures MTTR = Mean Time To Repair MTTF = Mean Time To Failure
MTBF
Mean Time Between Failures
MTTR
Mean Time To Repair
MTTF
Mean Time To Failure
Highly Available System
- can withstand some measure of degradation while still remaining available
- downtime is minimized
- minimal human intervention is required
Fault Tolerance
Built in redundancy - ability to remain operational
- does not address software failures
Key factor in Availability
Scalability
Ability of an application to accommodate increases in capacity needs without changing design.
- Does not guarantee availability
Key Factor in Availability
Recoverability
Process, Policies, and Procedures related to restoring service after a catastrophic event.
Factors Affecting Availability
- Fault Tolerance
- Scalability
- Recoverabilty