Hosting Drupal on AWS
summary
Breakthrough builds a reproducible AWS stack for Drupal using Terraform + Chef to provision EC2 (Amazon Linux), RDS (multi‑AZ with PITR), EFS for shared files, and Soloist AMI Blue‑Green deployments. It scales from two servers to autoscaling pools (up to ~40 instances) to handle spikes — one project sees ~800 concurrent users and 70,000 tests month‑to‑date. CloudWatch log queries, SNS alarms, WAF DDoS protection, and onepassword vaulting are in place; deployments are near‑zero‑downtime and backups recoverible.
AI-written summary · about
chapters (23)
- 0:00Introduction and speakers
- 2:55Why choose AWS for Drupal
- 7:20Scalability and performance needs
- 10:14Client handoff and account management
- 12:01Backup and recovery strategies
- 12:45Log aggregation and monitoring
- 14:09Network security and firewalls
- 16:18Integration with Google and Tao
- 17:01Configuration management with Terraform and Chef
- 21:22Setting up Drupal on AWS
- 23:53SSL certificates and DNS management
- 28:11Load balancing and high availability
- 31:44Database setup with RDS
- 35:19DNS management with Route 53
- 39:58Additional AWS services used
- 42:12Infrastructure as code with Terraform
- 45:49Setting up EC2 servers with Chef
- 49:05Server updates and maintenance
- 52:27Development workflow and deployment
- 56:29Blue-green deployment process
- 57:54Auto-scaling for smaller projects
- 59:38Log analysis with CloudWatch Insights
- 1:03:27Q&A session
related talks
50mAutoscaling, Rolling Deploys with Drupal on AKS
49mAutomation in Deployment on Hybrid Hosting and Private Cloud Environments
22mDrupal HA: a story from the trenches
17mDeployments We Can Believe In
38mDeploying Database Clusters in the Cloud
14mExpect the unexpected: Building resilience with AWS
27mDevOps in the Cloud
21mAvoiding That $1M Dollar AWS Bill - Mark Michael, Glenn Oppegard