In addition to the below i would also think of rebooting one at a time, just to be safe... folks in my corp are seeing the reboot fail because of EBS or S3 dependencies while booting the image.
Regards, </VJ> On Thu, Dec 8, 2011 at 3:04 AM, Peter Sanford <psanf...@nearbuysystems.com>wrote: > Just rebooting a machine with ephemeral drives is ok (it does an os > level reboot). You will also keep the same IP address. If you stop and > then start a machine with ephemeral drives you will lose data. > > See: http://alestic.com/2011/09/ec2-reboot-stop-start > > > On Wed, Dec 7, 2011 at 6:43 PM, Stephen McKamey <step...@mckamey.com> > wrote: > > I just received an email from AWS about rebooting my EC2 instance for > > maintenance. Thankfully this is just my webhead, but I'm > curious have others > > experienced this with a Cassandra instance? > > > > http://aws.amazon.com/maintenance-help/ > > > > The details seem to say that if you allow them to do the reboot for you > then > > your instance data will remain intact (as opposed to if you do it > yourself). > > Has anyone experienced this to verify? > > > > Thanks, > > Stephen >
