AUTHOR: http://aws.typepad.com/aws/2011/11/ec2-instance-status-monitoring.html LINK!

Recent AWS Customer Success Stories & Videos

More AWS Customer Success Stories...

« AWS Management Console Now Supports Amazon Route 53 | Main | Webinar: Getting Started on Microsoft Windows With AWS »

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00d8341c534853ef0162fc62ad76970d

Listed below are links to weblogs that reference EC2 Instance Status Monitoring:

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

Account Deleted

Hi
Great job!
Can we have this kind of notification before spot instance terminated?

Jonathan Krengel

Concerning this statement:
"If it is an EBS-backed instance, you can start and restart the instance and it will be migrated to different hardware."

Does this only apply when the underlying hardware is marked for retirement?

Hrish

This is available as part of the API

http://docs.amazonwebservices.com/AWSEC2/2011-11-01/APIReference/index.html?ApiReference-query-DescribeInstanceStatus.html

but I could not find an equivalent call in the AWS Java SDK. Is the SDK updated yet?

Niall

Do AWS have plans to send a simple email alert when a customers instance is earmarked for any of the reboot events you outlined above?

The alternative at the moment would be to pay for some additional 3rd part monitoring which isn't ideal.

Also, if an EC2 instance is scheduled for a system or retirement reboot then will a reboot invoked by a customer cause the instance to boot up on different hardware? And then will the schedulef reboot be disgarded?

But this is a good improvement anyways.
Thanks

Matt

To answer part of Niall's post, I can confirm that the scheduled shutdown by AWS is indeed canceled after a Stop and Start of your instance. Just don't forget to re-associate your Elastic IP on startup.

imet

but the latest JAVA API can't get the function

Bernd Eckenfels

What I would like to see from the API is a "soft-stop" which will schedule a stop/terminate on the next tick, so I can set a flag that my instance is no longer needed but it can run till the end of the hour. I can understand Amazon does not want this in order to increase half-used hours, however you can also get some positive aspects if a instance is marked for shutdown on the next hour, you can calculate with it becoming available. The alternative is a management portal polling the instances and shutting them down on the same clock tick. Just with additional load, more hazzles and less visibility for AWS.

The comments to this entry are closed.

Featured Events

The AWS Report


Brought to You By

Jeff Barr (@jeffbarr):



Jinesh Varia (@jinman):


Email Subscription

Enter your email address:

Delivered by FeedBurner

April 2014

Sun Mon Tue Wed Thu Fri Sat
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30