You've mis-read this section - it was answering another commenter who claimed to be having the same issue but was in fact having a different issue as you descri

You've mis-read this section - it was answering another commenter who claimed to be having the same issue but was in fact having a different issue as you described in your quote. The underlying problem the update caused was acknowledged by an AWS rep in the thread who suggested moving to an instance with more CPU resources. > If moving to a HVM based AMI is not easy, changing your instance size to m3.medium, which provides more compute than m1.medium at a lower price, may be a workaround.