Cannot connect to an AWS or EC2 instance when the Bamboo application is running behind a proxy

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

Symptom

You are running Bamboo behind a proxy, and Bamboo may not be able to connect to external applications such as an AWS, an EC2 instance, or an external JIRA instance.

Solution

You should be able to overcome these issues by either specifying your proxy settings to Bamboo as system properties when starting up Bamboo or by adding the following system properties with appropriate string values to the bamboo.sh or wrapper.conf file of your Bamboo installation:

  • http.proxyHost

  • http.proxyUser

  • http.proxyPassword

  • http.proxyDomain

Please refer to the instructions on Starting Bamboo for details on how to specify Bamboo system properties via the bamboo.sh or wrapper.conf files.

Updated on April 8, 2025
Platform
Data Center only
Product
Bamboo Data Center
On this pageSummarySolution

Still need help?

The Atlassian Community is here for you.
Ask the Community