What You'll Miss on AWS & How To Find It
summary
Nine concrete gaps are named and fixed: 99.95% SLA (~four hours downtime/year) and multi‑AZ RDS failover 1–2 seconds, auto scaling + ELB session and deployment pain, EFS slow writes and PHP opcache timestamp problems, and a working S3‑based deploy plus an agent for synchronized rollouts. Lambda automates AMI builds and rolling updates, CloudWatch centralises logs, and Terraform + CloudFront reduce load. Some approaches fail (atomic/blue‑green caused consistency issues); the S3 agent, lambda pipeline and log agent do work.
AI-written summary · about
chapters (13)
- 0:00Introduction and motivation
- 1:53Planning the AWS migration
- 5:48Understanding AWS structure
- 9:05Auto scaling and load balancing
- 11:04Managing user sessions
- 13:48Storage and filesystem issues
- 17:41Optimizing deployment processes
- 21:05Deployment strategies
- 23:46Server configuration and automation
- 27:54Managing cron jobs
- 30:43SSH access and management
- 34:40Logging and monitoring
- 39:08Conclusion and resources
related talks
14mExpect the unexpected: Building resilience with AWS
44mServerless Architecture on Production: Good, Bad and Ugly Parts
57mResilient Cloud Architecture Design Patterns
43mFlying Over AWS
38mA Software Developer Guide to Working with AWS
01h 05mOperational excellence
25mHow to Fail at Serverless (without even trying)
47mReal Use Cases for Using AWS Lambda for Infrastructure Tasks