Imagine waking up to find your site and service hacked. Everyone is running around, trying to find out what went wrong; you’re tasked with repairing the damage. But unfortunately, that automation project you’ve been promising yourself you’d get done has always taken a backburner to more pressing matters and features. With everyone breathing down your neck, wonder where to start. We talk with a panel of engineers who found themselves in exactly this nightmare scenario and follow them as they:
- 1:13 – News & Views
- 1:18 – PayPal switches (part of?) its infrastructure to OpenStack
- 4:45 – Ruby 1.8.x end-of-lifed
- 6:03 – Massachusettes to “tax the cloud“?
- 7:29 – All your SimCities are Belong to Us!
- 8:17 – Footage of the SimCity carnage
- 10:01 – Main Segment: Automate Your Infrastructure in 48 Hours or Your Pizza Is Free
- 50:15 – Tool Tip
What are you own experiences with security incident responses and automation? Where’s the line of infrastructure improvement vs. response? And are there ways to avoid this issue altogether?
Join the discussion!