Re:Has Amazon EC2 become over subscribed?
by swolchok on Tuesday January 12, 2010 @07:55PM
(#1049067)
Actually, "Hey You, Get Off of My Cloud: Exploring Information Leakage in Third-Party Compute Clouds" (http://people.csail.mit.edu/tromer/papers/cloudsec.pdf) documents "the tendency for EC2 to assign fresh instances to the same small set of machines", and exploits this tendency in order to co-locate a malicious instance with a victim instance. Rapid re-instantiation seems like a bad way to improve performance.
This sounds reasonable, but the method could be improved by instantiating a new instance first and then removing the old one - this ensures you don't instantiate in the same location as before.
I don't know EC2 architecture well enough to know, but there may even be some ways of telling if your new instance is located in the same problematic instance as the original one (perhaps by tracerouting the problem instance and finding it to be v near by). If this happens presumably you can instantiate a 3rd and repeat until you find a suitable instance at which point you kill the others.