Using Tasks for AWS

Getting started

  1. (Optional) Ensure there is at least one AWS Connector with System scope available – refer to Providing AWS Security Credentials for details.

  2. (Optional) Decide whether and how you want to maintain your task configuration as code – refer to Providing task configuration as code for details.

  3. Start building and deploying with the available tasks.

Using tasks

AWS CloudFormation

Provisioning with AWS CloudFormation provides an overview for resource provisioning workflows based on the following tasks:

AWS CodeDeploy

Deploying to AWS CodeDeploy provides an overview for continuous delivery/deployment workflows based on the following tasks:

 

 

 

AWS Elastic Beanstalk

Deploying to AWS Elastic Beanstalk provides an overview for continuous delivery/deployment workflows based on the following tasks:

 

 

 

AWS Lambda

Deploying to AWS Lambda provides an overview for continuous delivery/deployment workflows based on the following tasks:

 

 

 

AWS OpsWorks

Deploying to AWS OpsWorks provides an overview for continuous delivery/deployment workflows based on the following tasks:

 

 

AWS Security Token Service (STS)

AWS Systems Manager (SSM)

AWS Step Functions

Amazon Elastic Compute Cloud (Amazon EC2)





Amazon Elastic Container Registry (Amazon ECR)

Amazon Elastic Container Service (Amazon ECS)

Deploying to Amazon ECS provides an overview for continuous delivery/deployment workflows based on the following tasks:

 

 

 

 

Amazon S3

Using Bamboo variables

All tasks support configuration via Bamboo variables: variables can be substituted in task parameters for AWS resource management, and variables are automatically defined from AWS resources affected by a task – refer to Injecting task configuration via Bamboo variables for details.

How-to Articles

Frequently Asked Questions (FAQ)