Documentation for Tasks for AWS 2.6 – other releases are available in the Tasks for AWS Documentation Directory.
View

Unknown macro: {spacejump}

or visit the current documentation home.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Tasks for AWS adds several Amazon Web Services (AWS) related Tasks to deploy and operate AWS resources on demand. Furthermore, you can enable various development, testing and disaster recovery scenarios by operating backup schedules for EBS volumes and EC2 instances

Temporary AWS Security Credentials Variations

Outside of the AWS Client Configuration referenced below, anything else is currently handled via the respective Task configuration, most notably the AWS Credentials (see footnote below).

Integration with our Identity Federation for AWS add-on will be added later on: due to Bamboousually running builds without a user context this requires a special solution.

On this page:

 

AWS Client Configuration

The AWS API is eventually consistent only and also exhibits a customer specific dynamic throttling policy, both of which require respective retry logic to be in place. Accordingly the facilitated AWS SDK for Java features an exponential backoff strategy already, but its default retry number of 3 (accumulating to a retry window of up to ~4 seconds) has proven to be too low for the tasks at hand, which has been increased to 7 accordingly (accumulating to a retry window of up to ~1 minute).

This should ideally be sufficient for most scenarios, but the values are adjustable by defining one or both of the following variables if need be:

  • ${custom.aws.maxErrorRetry} - how many retries should the exponential backoff algorithm perform (default: 7)
  • ${custom.aws.awaitTransitionInterval} - how long should the task wait before querying the resource transition state again (default: 15000 milliseconds)

HTTP(S) Proxy Configuration

If your Bamboo instance is running behind a firewall, the add-on will reuse the proxy configuration from Bamboo.

Please note that the AWS API calls use SSL throughout, so the add-on relies on the respective system properties https.proxyHost and https.proxyPort to be available from the Java Virtual Machine (JVM). Depending on your environment, you might need to set these https.* variations explicitly in addition to the usual http.* ones.

  • No labels