Problem Definition

Traffic between the Bamboo Server and Elastic agents is tunneled. HTTP traffic from the Elastic Agent arrives on the Bamboo Server via the tunnel and it is routed by the tunnel client to the Base URL (Bamboo Administration >> Overview >> General Configuration >> Base URL) of the Bamboo Server.

If the Base URL of the instance cannot be reached from the Bamboo Server (e.g. the address is a load balancer or reverse proxy and the Bamboo Server has no outbound access), the HTTP connection cannot be established.

Suggested Solution

Programmatically add a separate Tomcat HTTP connector for receiving HTTP traffic from the tunnel client that binds to loopback. Prioritize connection attempts as follows:

1. Value of bamboo.ec2.agent.endpoint override argument
2. New HTTP connector
3. Fallback to Base URL

Workaround

• See the Resolution section of: Elastic agents remain in Pending and do not connect