A rough timeline:
- Wednesday night (eastern time): Amazon notifies customers about the undisclosed issue, saying it will start rebooting instances on Friday.
- Thursday morning: Amazon posts a blog with a bit more information.
- Friday: [company]Amazon[/company] starts rebooting what it says is 10 percent of its total EC2 instances.
- Friday night: [company]Rackspace [/company]notifies its customers.
- Sunday: Rackspace starts the reboot process.
It seems clear, as David Mytton, CEO of [company]Server Density[/company] noted in comments to an earlier story, that AWS and Rackspace got the same “predisclosure” notification re. the Xen issue, but it took Rackspace took two days longer to respond, The most likely reason, Mytton surmised, was that Rackspace was working on the proper process to handle the critical vulnerabilities.
Not to belabor the point, but cloud providers must tread a fine line — providing as much disclosure as early as possible to keep customers apprised of any possible issues but if there’s a security concern, which appears to be the case here, there’s only so much they can say.
On this week’s Structure Show we have Ericsson cloud chief Jason Hoffman and Apcera Founder Derek Collison on what they’re doing to make cloud computing easier via Ericsson’s big investment in Apcera’s and its Continuum IT policy-focused platform.
Hosts: Barb Darrow and Derrick Harris