Documentation for Tasks for AWS 2.6 – other releases are available in the Tasks for AWS Documentation Directory.
View

Unknown macro: {spacejump}

or visit the current documentation home.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

You can use the Amazon EC2 Instance to start, stop or reboot provisioned Amazon Elastic Compute Cloud (Amazon EC2) instances on demand, e.g. only when needed by the build itself (development) or at specific times of the day (operations).

 

 

On this page:

Related Pages:

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

      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.

      RegionSelect the desired AWS Region from the preconfigured list. Alternatively, select [Use region variable ...] to supply the region dynamically via Bamboo variables for example (needs to be a region code such as ap-southeast-2) .
      ...Configure task/action specific parameters, see below ...
      AWS Credentials SourceSelect 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.

    2. Actions supported by this task:

      Start

      		 
      Instance ID

      (Optional) One or more instance IDs (semicolon separated).

      Filter JSON

      (Optional) Resource filters in JSON format. Insert fragments from the inline Examples dialog to get started.

      Stop

      		 
      Instance ID

      see Start above

      Filter JSONsee Start above
      Force stop

      Check to force the instances to stop.

      • (warning) 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 JSONsee Start above

Notes

Creating/Terminating instances

We currently consider instance lifecycle goals (i.e. create/terminate) to be sufficiently addressed by the AWS CloudFormation Stack task, hopefully covering the majority of use cases (please let us know otherwise).
  • No labels