I've currently got an Elastic bamboo remote agent set up in AWS. The image it uses has had lots of modifications over the years and currently works exactly as we wanted - however - I'd like to run it as more of a clean build agent rather than an Elastic agent. Problem is that it doesn't connect if it's not started by the bamboo server.
Any ideas what I would need to alter on the image so I can change it to a standard remote agent?
Elastic agent design is not the same as remote agent.
Do you mean that you have installed a separate remote agent in the EC2 instance?
What is the error in the remote agent log when it fail to connect?
Is the Bamboo server publicly accessible so that the remote agent from EC2 can connect to it? (Elastic agent use tunnel connection so there is no need for public access)
On 31 May, a GDPR-related change went live in the Bitbucket Cloud API that resulted in users not being able to create or edit Bitbucket Cloud Linked repositories in Bamboo. This API update removed t...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events