Page Comparison

...

...

...

...

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

...

...

...

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.

• See Cannot connect to an AWS or EC2 instance when the Bamboo application is running behind a proxy for details.

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.

...