/
Configuring an Outbound HTTP(S) Proxy

Configuring an Outbound HTTP(S) Proxy



If your Bamboo or Jira instance is running behind a firewall, the app will reuse the proxy configuration from the Atlassian host application.

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 app 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.

See How to Configure an Outbound HTTP Proxy for Jira for details (while documented for Jira, this information applies to Bamboo too).

 

Related content

Configuring an AWS Access Key
Configuring an AWS Access Key
Read with this
Configuring an Outbound HTTP(S) Proxy
Configuring an Outbound HTTP(S) Proxy
More like this
Administering Identity Federation for AWS
Administering Identity Federation for AWS
Read with this
Configuring an Outbound HTTP(S) Proxy
Configuring an Outbound HTTP(S) Proxy
More like this
Configuring an AWS Connector
Configuring an AWS Connector
Read with this
Configuring an Outbound HTTP(S) Proxy
Configuring an Outbound HTTP(S) Proxy
More like this
Atlassian®, Atlassian Bamboo®, Bitbucket®, Atlassian Crowd®, Confluence®, Jira®, Jira Service Management™, Opsgenie®, and Statuspage™ are registered trademarks of Atlassian.
Amazon Web Services™, AWS™ and the “Powered by Amazon Web Services” logo are trademarks of Amazon.com, Inc. or its affiliates in the United States and/or other countries.

Utoolity® is a registered trademark of Utoolity GmbH.
© 2024 Utoolity GmbH. All rights reserved.