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).
Configuration
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 Instance(s) above
Filters see Start Instance(s) above Don't fail for empty filter result see Start Instance(s) 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.
Hibernate Check to hibernate the instance instead of shutting it down.
Reboot Instance(s)
Instance ID see Start Instance(s) above
Filters see Start Instance(s) above Don't fail for empty filter result see Start Instance(s) above
Variables
Start Instance(s)
Stop Instance(s)
Reboot Instance(s)
N/A
How-to Articles