Elastic bamboo doesn't work when there is an outgoing http proxy since changing from using Typica to Amazon AWS in atlassian-aws

While investigating the unicorn elastic bamboo issues, I discovered that bamboo 3.1.4 elastic functionality doesn't work at all when there is an outgoing http proxy.

Further analysis with Marek's help traced this to a change in atlassian-aws (bamboo 3.0.x uses atlassian-aws 0.15, 3.1.4 uses atlassian-aws 0.18). I made a change to atlassian-aws and after uploading the patched jar, the problem was resolved. See https://studio.atlassian.com/browse/AWSLIB-16 for details.

I think this problem will affect not only unicorn, but any bamboo instance that uses an outgoing http proxy (specifically, the https.proxyHost and https.proxyPort java system properties). It will also affect bamboo 3.2.x as well.

To fix, we'll need to release new versions of atlassian-aws, and change the relevant bamboo branches to use the correct atlassian-aws version.

It's a simple fix, and I've supplied a patch on AWSLIB-16, but I wasn't sure where all to apply the changes (since there are lots of atlassian-aws and bamboo versions floating around).

Let me know, and I can go ahead and commit the necessary changes.