News for hackers. Stuff that matters.
Re:AWS instance was scheduled for retirement by Corrado on Sunday October 27, 2013 @09:14AM (#6621829)
Ok, the key to working with AWS EC2 instances is to remember that they are ephemeral and can disappear at any point in time. If your treating it like a traditional server that you have in a rack you're doing it wrong. Just turn it off and start a new one. You are using a configuration manager (puppet, chef, etc) aren't you?
Re:AWS instance was scheduled for retirement by bowlofpetunias on Sunday October 27, 2013 @10:25AM (#6622010)
I've learned a long time ago to treat traditional servers in a rack like they can disappear (or get compromised) at any time for a huge range of reasons. You can never be too paranoid.
Re:AWS instance was scheduled for retirement by manmal on Sunday October 27, 2013 @03:00PM (#6623003)
Yeah, I like how Netflix even goes so far as killing instances randomly: http://venturebeat.com/2013/09/10/netflix-chaos-monkeys/
Re:AWS instance was scheduled for retirement by jpitz on Sunday October 27, 2013 @01:33PM (#6622649)
This ^^^ comment cannot be upvoted enough. Please treat all servers, virtual or not, as ephemeral.
Re:AWS instance was scheduled for retirement by toomuchtodo on Sunday October 27, 2013 @12:52PM (#6622495)
Well, sort of. As long as you're storing all your data on EBS volumes, you can treat EC2 instances as machines in a rack. Problem with your instance? Reboot, and you'll be good as new.

Now, if you lose an EBS volume, that's totally different. You are snapshotting your EBS volumes, correct?

Re:AWS instance was scheduled for retirement by jes5199 on Sunday October 27, 2013 @03:21PM (#6623088)
as someone who used to be a Puppet maintainer, I say: use Chef. or Ansible.