An elastic agent process runs in an elastic instance and will automatically start when an instance is started. If you want to run a Job build on an elastic agent, you can start an elastic instance for the agent to run in. The elastic agent will inherit the capabilities of the image that the instance is started from.

Limitations on the number of elastic instances — An elastic agent is counted as a remote agent for licensing purposes. Hence, if starting an elastic instance (and hence an elastic agent) causes you to exceed the total number of remote agents allowed under your license, you will not be able to start the instance.

Related pages:

To start an elastic instance:

  1. Click the  icon and select Elastic Instances.
  2. Click Start New Elastic Instances.
  3. Click Submit. The 'Manage Elastic Instances' page will be displayed, showing your new instances starting:
    1. A note will display stating that the elastic instances (and corresponding agents) are starting.
    2. Your elastic instances will then display with a status of 'Pending' while they start up. This generally takes a few minutes.
    3. Once your elastic instances have started up, they will progress to 'Running' status. An elastic agent process will then start up for each instance. They will display a status of 'Pending' while they start.
    4. Once the elastic agents have started, they will display a status of 'Online'.

Notes

What if my elastic agent doesn't start? Bamboo has a set period of time that it waits for the agent to start on an elastic instance. If no response is received by the end of this time period, Bamboo will shut down the elastic instance. 

You can configure this time period by modifying the following system property (default is 600):
bamboo.agent.elastic.startupTimeoutSeconds
Read Configuring system properties for instructions on how to set a system property.