1. P1: Operational Excellence
1.1. Design Principles
1.1.1. Perform operations as code
1.1.2. Annotate documentation
1.1.3. Make frequent, smal, reversible changes
1.1.4. Refine operations procedures frequently
1.1.5. Anticipate failure
1.1.6. Learn from all operational failures
1.2. Best Practices
1.2.1. Prepare
1.2.1.1. OPS-1: What factors drive your operational priorities?
1.2.1.2. OPS-2: How do you design your workload to enable operability?
1.2.1.3. OPS-3: How do you know that you are ready to support a workload?
1.2.1.4. Services
1.2.1.4.1. Config
1.2.1.4.2. Config Rules
1.2.2. Operate
1.2.2.1. OPS-4: What factors drive your understanding of operational health?
1.2.2.2. OPS-5: How do you manage operational events?
1.2.2.3. Services
1.2.2.3.1. CloudWatch
1.2.2.3.2. CloudTrail
1.2.3. Evolve
1.2.3.1. OPS-6: How do you evolve operations?
1.2.3.2. Services
1.2.3.2.1. Elastic Search
1.3. Resources
1.3.1. Documentation
1.3.2. Whitepaper
1.3.3. Video
2. P2: Security
2.1. Design Principles
2.1.1. Implement a strong identity foundation
2.1.2. Enable traceability
2.1.3. Apply security at all layers
2.1.4. Automate security best practices
2.1.5. Protect data in transit and at rest
2.1.6. Prepare for security events
2.2. Best Practice
2.2.1. Identity and Access Management
2.2.1.1. SEC-1: How are you protecting access to and use of the AWS account root user credentials?
2.2.1.2. SEC-2: How are you defining roles and responsibilities of system users to control human access to the AWS Management Console API?
2.2.1.3. SEC-3: How are you limiting automated access to AWS resources (for example applications scripts, and/or third-party tools or services)?
2.2.1.4. Services
2.2.1.4.1. IAM
2.2.1.4.2. MFA
2.2.2. Detective Controls
2.2.2.1. SEC-4: How are you capturing and analyzing logs?
2.2.2.2. Services
2.2.2.2.1. CloudTrail
2.2.2.2.2. Config
2.2.2.2.3. CloudWatch
2.2.3. Infrastructure Protection
2.2.3.1. SEC-5: How are you enforcing network and host-level boundary protection?
2.2.3.2. SEC-6: How are you leveraging AWS service-level security features?
2.2.3.3. SEC-7: How are you protecting the integrity of the operating system?
2.2.3.4. Service
2.2.3.4.1. VPC
2.2.4. Data Protection
2.2.4.1. SEC-8: How are you classifying your data?
2.2.4.2. SEC-9: How are you encrypting and protecting your data at rest?
2.2.4.3. SEC-11: How are you encrypting and protecting your data in transit?
2.2.4.4. Services
2.2.4.4.1. Encrypt RDS, S3, EBS
2.2.4.4.2. Macie
2.2.4.4.3. KMS
2.2.5. Incident Response
2.2.5.1. SEC-12: How do you ensure that you have the appropriate incident response?
2.2.5.2. Services
2.2.5.2.1. IAM
2.2.5.2.2. CloudFormation
2.3. Resources
2.3.1. Documentation
2.3.2. Whitepapers
2.3.3. Videos
3. P3: Reliability
3.1. Design Principles
3.1.1. Test recovery procedures
3.1.2. Automatically recover from failure
3.1.3. Scale horizontally to increase aggregate system availability
3.1.4. Stop guessing capacity
3.1.5. Manage change in automation
3.2. Best Practice
3.2.1. Foundations
3.2.1.1. REL-1: How are you managing AWS service limits for your accounts?
3.2.1.2. REL-2: How are you planning your network topology on AWS?
3.2.1.3. Services
3.2.1.3.1. IAM
3.2.1.3.2. VPC
3.2.1.3.3. Trusted Advisor
3.2.1.3.4. Shield
3.2.2. Change Management
3.2.2.1. REL-3: How does your system adapt to changes in demand?
3.2.2.2. REL-4: How are you monitoring AWS resources?
3.2.2.3. REL-5: How are you executing change?
3.2.2.4. Services
3.2.2.4.1. CloudTrail
3.2.2.4.2. Config
3.2.2.4.3. Auto Scaling
3.2.2.4.4. CloudWatch
3.2.3. Failure Management
3.2.3.1. REL-6: How are you backing up your data?
3.2.3.2. REL-7: How does your system withstand component failures?
3.2.3.3. REL-8: How are you testing your resiliency?
3.2.3.4. REL-9: How are you planning for disaster recovery?
3.2.3.5. Services
3.2.3.5.1. CloudFormation
3.2.3.5.2. S3
3.2.3.5.3. Glacier
3.2.3.5.4. KMS
3.3. Resources
3.3.1. Documentation
3.3.2. Whitepapers
3.3.3. Videos
3.3.4. Report
3.3.5. AWS Support
4. P4: Performance Efficiency
4.1. Design Principle
4.1.1. Democratize advanced technologies
4.1.2. Go global in minutes
4.1.3. Use serverless architectures
4.1.4. Experiment more often
4.1.5. Mechanical sympathy
4.2. Best Practices
4.2.1. Selection
4.2.1.1. PERF-1: How do you select the best performance architecture?
4.2.1.2. Compute
4.2.1.2.1. PERF-2: How did you select your compute solution?
4.2.1.2.2. Instances
4.2.1.2.3. Containers
4.2.1.2.4. Functions
4.2.1.2.5. Services
4.2.1.3. Storage
4.2.1.3.1. PERF-3: How do you select your storage solution?
4.2.1.3.2. Services
4.2.1.4. Database
4.2.1.4.1. PERF-4: How do you select your Storage solution?
4.2.1.4.2. Services
4.2.1.5. Network
4.2.1.5.1. PERF-5: How do you select your network solution?
4.2.1.5.2. Services
4.2.2. Review
4.2.2.1. PERF-6: How do you ensure that you continue to have the most appropriate resource type as new ressource types and features are introduced?
4.2.2.2. Services
4.2.2.2.1. AWS BLog
4.2.2.2.2. AWS Website
4.2.2.2.3. re:invent & summits
4.2.2.2.4. twitter
4.2.3. Monitoring
4.2.3.1. PERF-7: How do you monitoring your resources post-launch to ensure they are performing as expected?
4.2.3.2. Services
4.2.3.2.1. Cloudwatch
4.2.3.2.2. Lambda
4.2.3.2.3. Cloudtrail
4.2.4. Tradeoffs
4.2.4.1. PERF-8: How do you use tradeoffs to improve performance?
4.2.4.2. Services
4.2.4.2.1. Elastic Cache
4.2.4.2.2. CloudFront
4.2.4.2.3. Snowball
4.2.4.2.4. RDS Read replicas
4.3. Ressources
4.3.1. Documentation
4.3.2. Whitepaper
4.3.3. Videos
5. P5: Cost Optimization
5.1. Design Principle
5.1.1. Adopt a consumption model
5.1.2. Measure overall efficiency
5.1.3. Stop spending money on data center operations
5.1.4. Analyse and attribute expenditure
5.1.5. Use management services to reduce cost of ownership
5.2. Best Practices
5.2.1. Cost-Effective resources
5.2.1.1. COST-1: Are you considering cost when you select AWS services for your solutions?
5.2.1.2. COST-2: Have you sized your resources to meet your cost targets?
5.2.1.3. COST-3: Have you selected the appropriate pricing model to meet your cost targets?
5.2.1.4. Services
5.2.1.4.1. Cost Explorer
5.2.2. Matching Supply and Demand
5.2.2.1. COST-4: How do you make sure your capacity matches but does not substantially exceed what you need?
5.2.2.2. Services
5.2.2.2.1. Auto Scaling
5.2.3. Expenditure Awarness
5.2.3.1. COST-5: Do you consider data-transfer charges when designing your architecture?
5.2.3.2. COST-6: How are you monitoring usage and spending?
5.2.3.3. COST-7: Do your decommission resources that you no longer need or stop resources that are temporarily not needed?
5.2.3.4. COST-8: What access controls and procedures do you have in place to govern AWS usage?
5.2.3.5. Services
5.2.3.5.1. CloudWatch
5.2.3.5.2. SNS
5.2.4. Optimizing Over Time
5.2.4.1. COST-9: How do you manage and/or consider the adoption of new services?
5.2.4.2. Services
5.2.4.2.1. AWS Blog
5.2.4.2.2. AWS Website
5.2.4.2.3. Trusted Advisor
5.2.4.2.4. re:invent / Summits
5.2.4.2.5. Twitter
5.3. Resources
5.3.1. Documentation
5.3.2. Whitepaper
5.3.3. Video
5.3.4. Tools
5.3.4.1. AWS TCO Calculators
5.3.4.2. AWS Simple Monthly Caclulator