Use the Automate with AWS task to run remote actions with AWS from Bamboo jobs, specifically from builds and deployments. |
On this page: |
Related pages:
|
Configuration
To configure an Automate with AWS task:
Follow the initial steps in Create a task for a job
Select the Automate with AWS task
Complete the following settings:
| Action | Select the remote AWS action. |
| Parameters | Specify the parameters (JSON). |
| Evaluate as condition | Check to fail build based when returning an expected response format. |
| AWS Security Credentials | |
| Source | Select the AWS Credentials source (see below) – can be either an IAM Role for EC2, or a shared Identity Federation for AWS connector. |
| Connector | (Conditional) Select the shared Identity Federation for AWS Connector. Alternatively, select [Use connector variable ...] to supply the connector dynamically via Bamboo variables (needs to be a connector id such as f24e81bc-7aff-42db-86a2-7cf82e24d871) – refer to How to parametrize the AWS connector via a Bamboo variable for details. |
| Role ARN | (Conditional | Optional) Specify the ARN of another role that the agent's IAM role for EC2 should assume. |
Configure the selected AWS action's parameters template as documented for each action:
Entity Variables
Besides regular Bamboo variables, you can also inject contextual variables with workflow entities into the remote action parameters template – applicable entities for the Bamboo task are:
Examples
The examples are currently composed to reference only core entity variables – you can also reference Bamboo variables and applicable Bamboo specific entity variables |