AWS Well-Architected Framework

AWS Well-Architected Framework

1. Pillars

   • Operational Excellence
     • Focus on: Prepare Operate Evolve
     • Design principles
       • * Perform operations with code * Annotated documentation * Make frequent, small, reversible changes * Refine operations procedures frequently * Anticipate failure * Learn from all operational failures
     • Key Services
       • AWS Cloud Formation
       • Prepare
         • AWS Config & Config Rules
         • Operational Piorities
         • Design for Operations
         • Operational Readiness
       • Operate
         • Amazon CloudWatch
         • Understanding Operational Health
         • Deriving Business and Technical Insights
         • Responding Events
       • Evolve
         • Amazon Elasticsearch
         • Learn from experience
         • Share learnings
   • Security
     • Focus on: * Identity and access management * Detective controls * Infraestructure protection * Data protection * Incident response
     • Design principles
       • * Implement a strong identity foundation. * Enable traceability. * Apply security at all layers. * Automate security best practices. * Protect data in transit and at rest. * Prepare for security events.
     • Key Services
       • AWS IAM
       • Identity and access management
         • AWS IAM AWS Organizations MFA Token Temporary Security Credentials Amazon Cognito
       • Detective Controls
         • AWS Cloud Trail AWS Config Amazon CloudWatch
       • Infrastructure Protection
         • Amazon VPC Amazon Inspector AWS Shield AWS WAF
       • Data Protection
         • Amazon Macie AWS KMS Amazon S3 Amazon EBS Elastic Load Balancing Amazon RDS
       • Incident Response
         • AWS IAM AWS CloudFormation
   • Reliability
     • Focus on: * Foundations * Change management * Failure Management
   • Performance Efficiency
     • Focus on: * Selection * Review * Monitoring * Trade-offs
   • Cost Optimization
     • * Cost-effective resources * Match supply and demand * Expenditure awareness * Optimizing over time

2. General Design Principles

   • * Stop guessing capacity needs * Test at production scale * Make experimentation easier * Allow architectures to evolve * Build data-drivesn architectures * Improve through game days

3. Questions