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,462,647
Community Members
 
Community Events
176
Community Groups

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

Atlassian Community Events