- unmigrated-wiki-markup
Documentation for Tasks for AWS 2.10 – other releases are available in the Tasks for AWS Documentation Directory.
View
or visit the current documentation home.
Using the Amazon EC2 Instance task in Bamboo
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
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).
To configure an Amazon EC2 Instance task:
Navigate to the Tasks configuration tab for the job (this will be the default job if creating a new plan).
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.
Complete the following settings:
Common to all tasks
Actions supported by this task:
Start Instance(s)
Instance ID
(Optional) Specify one or more instance IDs (semicolon separated).
Filters
(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.
Don't fail for empty filter result
Check to prevent the task failing if no matching resources are found.
Stop Instance(s)
Instance ID
see Start above
Filters
see Start above
Don't fail for empty filter result
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(s)
Instance ID
see Start above
Filters
see Start above
Don't fail for empty filter result
see Start above
Variables
Start Instance(s)
Creating common variables for 1 resources affected by task:
... custom.aws.ec2.instance.resources: i-a316b842
Creating resource variables for instance 'i-a316b842':
... custom.aws.ec2.instance.resources.i-a316b842.InstanceId: i-a316b842
... custom.aws.ec2.instance.resources.i-a316b842.State: running
... custom.aws.ec2.instance.resources.i-a316b842.PrivateDnsName: ip-10-0-0-241.ec2.internal
... custom.aws.ec2.instance.resources.i-a316b842.PrivateIpAddress: 10.0.0.241
... custom.aws.ec2.instance.resources.i-a316b842.PublicDnsName:
... custom.aws.ec2.instance.resources.i-a316b842.PublicIpAddress: null
... custom.aws.ec2.instance.resources.i-a316b842.LaunchTime: 20150716T080402Z
... custom.aws.ec2.instance.resources.i-a316b842.tags: Name
... custom.aws.ec2.instance.resources.i-a316b842.tags.Name: taws-it-2.0.0
Creating common variables for first resource affected by task:
Creating resource variables for instance 'i-a316b842':
... custom.aws.ec2.instance.first.InstanceId: i-a316b842
... custom.aws.ec2.instance.first.State: running
... custom.aws.ec2.instance.first.PrivateDnsName: ip-10-0-0-241.ec2.internal
... custom.aws.ec2.instance.first.PrivateIpAddress: 10.0.0.241
... custom.aws.ec2.instance.first.PublicDnsName:
... custom.aws.ec2.instance.first.PublicIpAddress: null
... custom.aws.ec2.instance.first.LaunchTime: 20150716T080402Z
... custom.aws.ec2.instance.first.tags: Name
... custom.aws.ec2.instance.first.tags.Name: taws-it-2.0.0Stop Instance(s)
Reboot Instance(s)
N/A