AWS: Plumbing Is Important
summary
Checklist of concrete actions and gotchas for running Selenium on AWS: enable CloudTrail in every region and turn on VPC Flow Logs; give the root account a physical MFA token (~$45) and require MFA for all IAM users; stop using long-lived access keys and practice rotating keys; move to infrastructure as code with CloudFormation, register instances in Route 53 (no IPs), use auto-scaling groups that scale to zero, centralize logs (ELK/Splunk), and run fault-injection tests.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 0:25A troll and easy prediction
- 3:29Default VPC
- 4:55Multifactor authentication
- 6:54Access keys
- 8:29Treat your infrastructure like code
- 10:32Autoscaling groups
- 12:04Configuration management
- 14:24Application logs
- 17:07Infrastructure logs
- 20:34Tagging
- 24:49IP Addresses
- 30:06Amazon has 100 uptime
- 33:08Zero downtime deployments
- 36:23Checklist
- 39:31Questions
related talks
51mAWS Security Essentials
34mWhat “Security Needs to Be Our Top Priority” Means for Aws Builders/Customers
25mLogging, Monitoring, and Alerting in AWS (The TL;DR)
39mPerils of the cloud
25mUse lessons learned from the field to build for security
39mPart 3: practice what you preach when deploying Selenium 4.x
45mSecurity Lessons Learned Moving a Bank 100% in the Cloud
33mAutomating Cloud Security and Incident Response (DevSecOps)