News for hackers. Stuff that matters.
Re:AWS instance was scheduled for retirement by chris_wot on Sunday October 27, 2013 @08:18AM (#6621711)
What, you don't get notified?
Re:AWS instance was scheduled for retirement by travem on Sunday October 27, 2013 @12:04PM (#6622335)
It looks like the forum thread has been updated with the following comment from Luke@AWS

> I just looked into your instance a bit further, it does appear this was due to an issue with the underlying host on which your instance resided upon when you encountered the issues today.

> I do want to clarify here as our original reply mentioned a scheduled retirement, this was not the case and no notice was sent out because of this.

It looks like the original email was incorrect.

To add to this though if people rely on advance email notifications with AWS then they are putting at risk their availability. Just because it is on the cloud doesn't insulate you from hardware issues, these need to be planned for. AWS does provide some building blocks to address this (auto-scalaing and load balancers come to mind).

Re:AWS instance was scheduled for retirement by kalleboo on Sunday October 27, 2013 @08:43AM (#6621756)
I've gotten emails a week in advance and again a day in advance when an instance needed maintenance that would result in a 10 second network reset, so it'd really surprise me if Amazon completely retired an instance with no notification. This person must have missed the email or it got spammed.
Re:AWS instance was scheduled for retirement by themonk on Sunday October 27, 2013 @11:02AM (#6622127)
Can you tell me subject line of email.

I searched my mails for couple of words including instance ID, result is negative. No email in spam folder in last one month.

Re:AWS instance was scheduled for retirement by kalleboo on Sunday October 27, 2013 @01:41PM (#6622679)
From: Amazon EC2 Notification <[email protected]>

Subject: Amazon EC2 Maintenance - Instance Maintenance Account: NNNNNNNNNN

Dear Amazon EC2 Customer,

One or more of your Amazon EC2 instances have been scheduled for maintenance. The maintenance will result in a reset of the network connection for your instance(s). The network reset will cause all current connections to your instance(s) to be dropped. The network reset will take less than 1 second to complete. Once complete your instance(s) network connectivity will be restored. The instance(s) will have their network connections reset during the time window listed below.

You can avoid having your network connection reset at the specified time by rebooting your instance(s) prior to the maintenance window. To manage an instance reboot yourself you can issue an EC2 instance reboot command. This can be done easily from the AWS Management Console at http://console.aws.amazon.com by first selecting your instance and then choosing ‘Reboot’ from the ‘Instance Actions’ drop down box.

Re:AWS instance was scheduled for retirement by themonk on Sunday October 27, 2013 @02:12PM (#6622786)
Thanks, got an update from AWS, it was not scheduled retirement, it was some other issue.
Re:AWS instance was scheduled for retirement by sudhirj on Sunday October 27, 2013 @08:28AM (#6621727)
Maybe 'scheduled for retirement' is a euphemism for 'someone tripped over that rack's power cord'.
Re:AWS instance was scheduled for retirement by primitivesuave on Sunday October 27, 2013 @08:49AM (#6621772)
Made my day.
Re:AWS instance was scheduled for retirement by themonk on Sunday October 27, 2013 @10:45AM (#6622084)
No I did not got any notification.

It was EBS backed instance, since I had snapshot, it does not took much time to recreate a new instance. Beside that I had another instance behind ELB to avoid downtime.

If is fair to expect some notification for scheduled retirement.

Re:AWS instance was scheduled for retirement by latch on Sunday October 27, 2013 @08:32AM (#6621733)
They usually send an email a couple weeks before
Re:AWS instance was scheduled for retirement by the_mitsuhiko on Sunday October 27, 2013 @08:30AM (#6621730)
You do.