Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,460,625
Community Members
 
Community Events
176
Community Groups

Convert Elastic Bamboo Remote Agent AMI to work as standard remote build agent

Hi There,

 

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?

Cheers

1 answer

0 votes
Foong Atlassian Team Nov 09, 2018

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)

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events