How to publish artifacts from Elastic Bamboo agents to secured in-house repository

Natalia Usmanova September 12, 2011

We would like to publish (scp) certain artifacts of Bamboo jobs to an internal repository. The repository itself would run in Amazon Cloud inside a Virtual Private Cloud.
How should we configure the VPC firewall in order to only allow Bamboo agents to establish ssh connection to this server? Is it possible to somehow filter out the EC2 Instances started by our Bamboo from all the other machines on the internet? How does Atlassian use Elastic Bamboo agents to transfer artifacts to their internal Maven repo? Any ideas would be greatly appreciated. Thank you!

1 answer

0 votes
Jeff Curry
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 12, 2011

Hi Natalia,

A better option would be to utilize curl or wget from the internal repository to the Bamboo server within JIRA Studio ( see http://confluence.atlassian.com/display/BAMBOO/Configuring+a+Job%27s+Build+Artifacts ). This way you wouldn't have to mess with opening firewall rules on your Virtual Private Cloud as it is merely making outgoing https connections.

You could of course go the scp route, it's just a little more complicated. You'd have to utilize EBS and copy SSH keys to it in order for the build script to scp the artifacts over.

Let me know what you think

Cheers,

Jeff

Suggest an answer

Log in or Sign up to answer