Bamboo 2.2 : Shutting Down an Elastic Instance
This page last changed on Mar 09, 2009 by bmccoy.
We recommend that you shut down any elastic instances that are not being used. Amazon EC2 charge for the period of time that you have an instance running, so you can minimise your costs simply by shutting down instances with inactive agents. You should also shut down your elastic instances if you are going to restart your Bamboo server, otherwise you will orphan them from your Bamboo server. If you have set up automated procedures via the Bamboo Remote API to terminate agents (e.g. cron jobs), you can also configure Elastic Bamboo to automatically shut down instances after the agent processes terminate.
On this page: Shutting down an elastic instanceTo shut down an elastic instance,
Shutting down all elastic instancesTo shut down all elastic instances,
Configuring automatic shutdown of instances after agent terminationTo configure Elastic Bamboo to automatically shut down instances when agents are terminated, Please refer to Configuring Elastic Bamboo and follow the instructions for setting the 'Automatically shut down elastic instance when elastic agent process ends' option in the 'Elastic Bamboo Global Settings' section. Shutting down elastic instances via the Amazon Web Services (AWS) ConsoleWe strongly recommend that you manage your instances via the Elastic Bamboo user interface. However, if you have orphaned your elastic instances from your Bamboo server (e.g. restarted your Bamboo server without shutting down your elastic instances), you may need to shut your elastic instances down directly in AWS. Please refer to How do I shut down my elastic instances if I have restarted my Bamboo server? for further details. |
![]() |
Document generated by Confluence on Mar 09, 2009 17:06 |