You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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?
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.
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! =]