Six design principles for operational excellence in the cloud
- Perform operations as code
- Annotate documentation
- Make frequent, small, reversible changes
- Refine operations procedures frequently
- Anticipate failure
- Learn from all operational failures
Three best practise areas for cloud operational excellence
Prepare
Operate
Evolve
Seven design principles of the security pillar
- Implement a strong identity foundation
- Enable traceability
- Apply security at all layers
- Automate security best practises
- Protect data in transit and at rest
- Keep people away from data
- Prepare for security events
Five design principles of the reliability pillar
- Test recovery procedures
- Automatically recover from failure
- Scale horizontally to increase aggregate system availability
- Stop guessing capacity
- Manage change in automation
Four best practice areas for performance efficiency pillar
Selection
Review
Monitoring
Tradeoffs
Five design principles of the cost optimization pillar
- Measure overall efficiency
- Stop spending money on data centre operations
- Analyze and attribute expenditure
- Use managed and application level services to reduce cost of ownership
- Adopt a consumption model
Reliability
Probability that a system will function as intended for a specified period of time. Mean time between failures.
Availability
The percentage of uptime over a period of time (length of time between failures / year). Number of 9s. 5 9s is 99.999 percent availability.
Highly available system
Can withstand some degradation while remaining available.
Three factors that determine an application’s availability
- Fault tolerance
- Scalability
- Recoverability
AWS Trusted Advisor
Tool for reviewing your architectures.
Trusted advisor recommendation areas
Cost optimization Performance Security Fault tolerance Service limits
