Versions Compared

Old Version 2

changes.mady.by.user Henrik Opel [Utoolity]

Saved on

compared with

New Version Current

changes.mady.by.user Steffen Opel [Utoolity]

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Reformatted advanced topics sections.
Section
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 Bamboo usually running builds without a user context this requires a special solution.

Column
width64%

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

Info
titleTemporary AWS Security Credentials Variations
Column
width32%
Panel
bgColor#eeeeee

On this page:

Table of Contents

 

AWS

...

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:

...

Security Credentials

See  AWS Security Credentials for details.

Advanced Topics

The following topics are applicable to advanced scenarios only:

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.