Hacker News new | past | comments | ask | show | jobs | submit login

Configure a large instance, stick it in an Elastic Load Balancer with your other web servers, and just stop it.

I agree with allowing AWS to auto-provision N new instances when needed.

But from the article and with my financial hat on, when the large instance is stopped and left in a standby role, are you still paying for it?




You do not pay for an EC2 instance that is stopped. If the instance has attached EBS volumes you will continue to pay for the storage costs, but that is pretty minimal.

It is important to remember that a stopped instanced is not guaranteed to be able to be started again. If you have a m1.large stopped, there is a chance that Amazon will not have any m1.larges available in that zone/region when you try to start back up your instance.

Also know that the private dns name will change when a stopped instance is started again, so anything configured to point at that particular instance will have to be reconfigured.


But from the article and with my financial hat on, when the large instance is stopped and left in a standby role, are you still paying for it?

You aren't paying for the CPU time, only the S3/EBS storage space that the image occupies (which is negligible for any normal single instance/image)




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: