[Bamboo Cloud docs]
[Bamboo Knowledge Base]
Each elastic image registered with the Amazon Web Services (AWS) has its own unique identifier, known as an AMI ID.
You can associate multiple elastic images with a Bamboo server. One default shared image is maintained by Atlassian in AWS, and is available to all Elastic Bamboo users.
You can also create your own custom elastic images.
On this page:
Related pages:
Associating a custom elastic image with your Bamboo installation allows you to start elastic instances with capabilities that are different from those inherited from the default image. For example, you may wish to associate a Ubuntu operating system-based elastic image with your Bamboo installation, so that you can run Ubuntu-related tests on the instances started from that image.
Once you have associated a custom elastic image with Bamboo, the settings for your elastic image are stored as an elastic image configuration.
To associate a custom image with Bamboo:
Enter the details of your custom elastic image in the panel under 'Create Elastic Image Configuration':
Name | The name of your custom elastic image. If you created your own custom image, you should have named it in step 6 of the Creating a custom elastic image instructions. You can also view the image name via the AWS console. |
Description | A description for your image, which is used in Bamboo only. |
AMI ID | The AMI ID obtained as an output from step 6 of the Creating a custom elastic image instructions. You can also view the AMI IDs of elastic images via the AWS console. |
Automatically attach an Amazon Elastic Block Store (EBS) volume to new elastic instances | Select this option if you want the elastic instances started from this image to use the EBS. Read more about Configuring elastic instances to use the EBS. EBS Snapshot ID — Specify the EBS Snapshot ID of the EBS volume that you wish to attach to new instances. |
Instance Type | The instance type for new instances started from this image. Amazon offers a number of instance types that provide different computing capacity. Read more about Amazon EC2 instance types. |
Virtual Private Cloud Subnet | The Subnet of the Virtual Private Cloud where your Elastic Bamboo agent will start up. Choose multiple subnets from the list to enable Bamboo to automatically switch between Availability Zones when starting agents. This reduces the chance of a build failing because of a lack of available resources in a particular zone. For more about VPC, see the Amazon VPC FAQ. |
Availability Zone | The availability zone used to start your new instances from this image in (e.g. if you wish to use Elastic Bamboo with reserved instances). We recommend that you select "Default (chosen by EC2)" to allow Amazon to select the best zone for your instance. Read more about Amazon EC2 availability zones. |
Product | The EC2 product name. |
Screenshot: Manage your Elastic Image Configurations
You can customise the agent capabilities of an elastic image that is already associated with Bamboo. The initial process is similar to that of associating a custom elastic image with Bamboo (above). Here, however, you use the AMI ID of an image already associated with Bamboo — most commonly the default image.
To create an elastic image with customised agent capabilities: