Using the Amazon EC2 Instance task in Bamboo

Configuration

To configure an Amazon EC2 Instance task:

1. Navigate to the Tasks configuration tab for the job (this will be the default job if creating a new plan).
2. Click the name of an existing Amazon EC2 Instance task, or click Add Task and then Amazon EC2 Instance Task to create a new task.

3. Complete the following settings:

   1. Common to all tasks
      

       Click here to expand...

      Task Description	(Optional) Identify the purpose of the task.
      Disable this task	Check, or clear, to selectively run this task.
      Action	Each task supports one or more actions depending on the target AWS resource. Select the desired action and configure the action specific parameters below.
      Region	Select the desired AWS Region. Alternatively, select [Use region variable ...] to supply the region dynamically via Bamboo variables (needs to be a region code such as ap-southeast-2) - refer to How to parametrize the AWS region via a Bamboo variable for details.
      ...	Configure task/action specific parameters, see below ...
      AWS Security Credentials
      Source	Select the source for the required AWS Security Credentials - can be either Inline, an IAM Role for EC2 or a shared Identity Federation for AWS Connector.
      Connector	(Conditional) Select the shared Identity Federation for AWS Connector. Alternatively, select [Use connector variable ...] to supply the connector dynamically via Bamboo variables (needs to be a connector id such as f24e81bc-7aff-42db-86a2-7cf82e24d871) - refer to How to parametrize the AWS connector via a Bamboo variable for details.

   2. Actions supported by this task:
      

      Start
      Instance ID	(Optional) Specify one or more instance IDs (semicolon separated).
      Filter	(Optional) Specify resource filters in JSON format. Insert fragments from the inline Examples dialog to get started. Refer to the --filters specification for describe-instances for details on available filters. Refer to Listing and Filtering Using the CLI and API for details on filter value syntax.
      Stop
      Instance ID	see Start above
      Filter	see Start above
      Force stop	Check to force the instances to stop. The instances do not have an opportunity to flush file system caches or file system metadata. If you use this option, you must perform file system check and repair procedures.This option is not recommended for Windows instances.
      Reboot
      Instance ID	see Start above
      Filter	see Start above

Frequently Asked Questions (FAQ)