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).
| Panel | ||||
|---|---|---|---|---|
| ||||
On this page:
|
| Panel | ||||
|---|---|---|---|---|
| ||||
Related Pages: |
Configuration
| Info | ||
|---|---|---|
| ||
| 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
Include Page _CommonTaskParametersTable _CommonTaskParametersTable Actions supported by this task:
Start
Instance ID (Optional) Specify one or more instance IDs (semicolon separated).
Filter JSON (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 the possible available filters.
- Refer to Listing and Filtering Using the CLI and API for details on the filter value syntax for filter values.
Stop
Instance ID see Start above
Filter JSON 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 JSON see Start above
Frequently Asked Questions (FAQ)
| Questionslist macro | ||||||||
|---|---|---|---|---|---|---|---|---|
|