Bamboo Artifact Publishing Failure - SSLHandshakeException: Remote host terminated the handshake

[Pavankumar]

 Hello Atlassian Support Team,

I am encountering an issue when running a Bamboo plan inside a Docker container on an AWS Elastic Agent. The build attempts to publish a compiled binary artifact so it can be displayed in the Artifacts tab in Bamboo.

However, artifact publishing fails with the following error:

com.atlassian.bamboo.build.artifact.BambooRemoteArtifactHandler: javax.net.ssl.SSLHandshakeException: Remote host terminated the handshake Unable to publish artifact Required shared artifact: com.atlassian.bamboo.build.artifact.BambooRemoteArtifactHandler@22a2d465 The artifact is required, build will now fail.

Additional Details:

• The Bamboo job runs inside a Docker container on the Elastic Agent.

• The issue occurs only during artifact publishing.

• The Docker container is able to build successfully but fails during artifact upload with an SSL handshake error.

Could you please help identify what is causing this SSL handshake failure between the Elastic Agent and the Bamboo server, and recommend steps to resolve it?
Any troubleshooting guidance for SSL/TLS configuration would be greatly appreciated.

Thank you!

[Anik Sengupta]

When a Bamboo plan runs inside a Docker container on an AWS Elastic Agent, the artifact publishing is handled by the Bamboo Agent process, which must establish a secure TLS connection to the Bamboo Server.

The handshake usually fails for specific reasons in an AWS/Docker environment:

• Missing CA Certificates: The Docker image you are using for the build likely doesn't have the Bamboo Server's SSL certificate (or the Root CA) in its Java TrustStore (cacerts).

• Java Version/TLS Protocol Mismatch: If your Docker container uses an older version of Java  it may be trying to use a TLS version that your Bamboo Server/Load Balancer has disabled for security.