Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a ELB EC2 instance, I want to pause it by stopping it, so I can attach a new volume to it, but it will terminate the instance instead.

Because: instance was taken out of service in response to a system health-check. Any work rounds for this?

share|improve this question
Why can't you post it there? – ceejayoz Jul 26 '12 at 17:35
Turns out I can't – user129789 Jul 26 '12 at 18:01
Anyone with access to have an EC2 instance should have access to post there. Chances are AWS support is going to ask for an instance ID etc. that someone else couldn't provide. – ceejayoz Jul 26 '12 at 18:06

I believe that unless your instance is not in an auto scaling group you can stop / start it whenever you please and it will not be replaced. If you're instance is in an auto scaling group you can temporarily pause the auto scaling group buy running the command.

as-suspend-processes AutoScalingGroupName

Then after you're done updating the server and it is back online

as-resume-processes AutoScalingGroupName

share|improve this answer
I already tried to remove the instance from the Elastic Load Balancer, but that didn't work. Could it have something to do with the fact that I am using Ylastic with a "MyLowCPUAlarm" set to manage my instances? – user129789 Jul 26 '12 at 16:28
Btw. Could you be so nice to ask this question on the official Amazon AWS forums for me, just to be 100% sure? – user129789 Jul 26 '12 at 16:48
The ELB will not shut down an instance. It will just stop sending requests to the instance. If you have it in an auto scaling group and the health check for the auto scaling group is configured as ELB and not EC2 then when the healthcheck for the ELB fails it will replace the instance. But it will only do that if you're using auto scaling groups. However if all you're trying to do is attach a new volume, you can do that without stopping the instance without any problems. – bwight Jul 26 '12 at 17:44
No, you can't attach a new volume in Windows Server 2008, in Windows Server 2003, this would be no problem. – user129789 Jul 28 '12 at 8:58
I do it all the time with my windows server 2008 please explain why this wont work. – bwight Jul 28 '12 at 18:18

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.