Patching Your Way to Compliance with a Small Team and a Pile of Technical Debt
summary
A three‑pronged strategy cuts a mountain of patches down to manageable work: pick core technologies, decommission low‑value systems, and move remaining services to cloud managed services or Kubernetes. A seven‑person team reduces hundreds of EC2 instances by migrating caches to managed services (Memcached→ElastiCache) and search to hosted providers, runs workloads on Kubernetes with automatic node upgrades and Bottlerocket, and keeps manual effort to control‑plane upgrades — measurable reduced toil and faster compliance.
AI-written summary · about
chapters (11)
- 0:00Patching challenges
- 2:15Patching feels overwhelming
- 4:46Technical debt and toil
- 6:53Strategic trade-offs
- 9:19Moving to cloud services
- 10:45Legacy system decommissioning
- 11:46Systems in Kubernetes
- 13:11Resistance to change
- 14:15Dependency chains cost
- 16:47Incident response pain
- 17:31Current state and future
related talks
15mTaming software sprawl and demystifying your distributed architecture (PRT032)
47mWhy keeping your system secure is a bit like decluttering
42mContainer Patching: Making It Less Gross Than the Seattle Gum Wall
56mTaming Vulnerability Remediation at a Fortune 50 Company
36mImproving Security while Reducing Toil with DevSecOps
41mPractitioners' Panel
22mSimplicity: The Key to Software Success
17mAdvance securely: Safely migrating to