- unmigrated-wiki-markup
Documentation for Tasks for AWS 2.1 – other releases are available in the Tasks for AWS Documentation Directory.
View
or visit the current documentation home.
User's Guide
Tasks for your DevOps workflows - provision and operate Amazon Web Services resources from Bamboo build and deployment projects for development, testing and disaster recovery scenarios:
On this page:
Available Tasks
AWS CloudFormation Stack
Create, update or delete CloudFormation stacks defined by a template provided via URL or inline and specify template parameters and advanced options.
See Using the AWS CloudFormation Stack task in Bamboo for details.
Amazon EBS Snapshot
Create, delete or backup snapshots of Elastic Block Store volumes; in particular, the Task provides backup management with retention handling and backup set correlation.
See Using the Amazon EBS Snapshot task in Bamboo for details.
Amazon EC2 Image
Create, delete or backup images of EBS backed Elastic Compute Cloud instances; in particular, the Task provides backup management with retention handling and backup set correlation.
See Using the Amazon EC2 Image task in Bamboo for details.
Amazon EC2 Instance
Start, stop or reboot provisioned Elastic Compute Cloud instances on demand, e.g. only when needed by the build itself (development) or at specific times of the day (operations).
See Using the Amazon EC2 Instance task in Bamboo for details.
Amazon S3 Object
Upload, download, delete or copy Structured Storage Service objects (files); in particular you can upload your Bamboo job's build artifacts or select local files and directories (optionally via Ant Patterns) - when addressing S3 objects (files), it matches those by key prefix, which allows to operate on multiple objects at once (virtual directories resp. folder hierarchies).
See Using the Amazon S3 Object task in Bamboo for details.
Bamboo Variable Substitution/Definition
See Bamboo Variable Substitution/Definition for details.
AWS Credentials
The AWS credentials need to be specified for each task currently, which can be cumbersome quickly. Pending a more generic solution, it is already possible to ease this a bit via variable substitution as follows:
- configure Access Key and Secret Key as e.g.
${bamboo.awsAccessKeyPassword}and${bamboo.awsSecretKeyPassword} - define plan and/or global variables for the configured variable names (i.e.
awsAccessKeyPasswordandawsSecretKeyPasswordgiven this example) with the actual credentials, which will then be substituted on task execution accordingly
AWS Client Configuration
See AWS Client Configuration for details.