Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

EC2 elastic agent security groups.

Hi,

Having issues starting EC2 elastic agents within a VPC.

The way our VPC is configured, I require the agents to be assigned an additional security group to correctly function - specifically to get access to our corporate DNS server which is located on another subnet within the VPC. I have confirmed that when I manually add the required security group then run the agent start script, then the agent loads and the bamboo server marks the agent as ready.

How can I get the security group assignment configured?

Thanks.

 

1 answer

1 accepted

0 votes
Answer accepted

Hi @Alistair.Mackay

Your question seems pretty similar to this one:

Have you tried to configure this in AWS side?

The VPC on Bamboo side is configured through Image configurations >> Edit (the image you want)>> Use Virtual Private Cloud, but I guess this is not your issue, right?

Hi @Daniel Santos 

The underlying issue is that in the VPC into which the agents are being launched, the only available DNS server is provided by an Active Directory instance. In order to reach that server, an additional security group is needed on the newly launched elastic instance.

We did not want to add a heap of AD rules to the default bamboo SGs.

I solved this by creating a lambda that's triggered when the instance is launched. This lambda adds the required SG before the instance reaches the agent load phase.

 

Cheers,

Like # people like this

Hi @Alistair.Mackay

Thank you so much for sharing how you solved the problem. This will certainly help other users that may face the same issue.

When I have time, I'll publish the solution in my GiHub account.

Like Daniel Santos likes this

Great move! Thank you!

Like # people like this

Hi @Alistair.Mackay

Thank you for the awesome community initiative.
It does not matter the purpose of a given community, it will only succeed if we have people like you that take the time needed to share what they know with others.

Have a wonderful week ahead! =]

Like Steffen Opel _Utoolity_ likes this

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bamboo

Bamboo 101 Video

G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...

182 views 4 6
Read article

Community Events

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

Events near you