Security Best Practices: The Well-Architected Framework
summary
Framework shows concrete practices: use the Well-Architected tool in the console to run the same questionnaire used in tens of thousands of workload reviews, follow hands‑on Well-Architected labs (CloudFormation, CloudTrail, AWS Config) and automate fixes (cleanup IAM users, encode controls in infra-as-code). Key services and patterns named: AWS KMS (per‑dataset CMKs), Security Hub aggregating GuardDuty/Inspector findings, Systems Manager to avoid SSH, and runbooks/Game Days. Claim: partners ran reviews for over 3,500 customers; labs and automation are provided as runnable code.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 0:40The WellArchitected Framework
- 1:17Terminology
- 2:46The 5 Pillars
- 4:29Design Principles
- 6:33AWS Security Hub
- 7:46Security at All Layers
- 9:02Automate Security
- 10:23Key Management Service
- 12:21Customer Master Key
- 15:37Keeping People Away From Data
- 18:44Partner Program
- 19:38AWS WellArchitected Tool
- 20:38Resources
related talks
20mBuilding secure AWS app workloads using automated best practices
38mThe well-architected automation framework
25mIntegrate architectural best practices into enterprise IT governance
51mAWS Security Essentials
34mWhat “Security Needs to Be Our Top Priority” Means for Aws Builders/Customers
45mSecure Your APIs the AWS Well-Architected Way
38mBuilding Security at Speed
49mInstill Well-Architected Best Practices at Scale