Bamboo OnDemand must run in a separate region from our EC2 instances because of license restrictions ("Maximum Number Of Elastic Instances" cannot be greater than 1 in the Configuration section). EC2 Security Groups will only allow in-Region security groups to be identified. Because of this I cannot figure out how to allow elastic bamboo instances access our EC2 instances with security integrity. These are non-VPC instances.
For example... How can I use SSH/SCP tasks without opening port 22 on my EC2 instances up to the world?
I was away for a few weeks and other things on the project took priority. However I followed instructions (good example here: http://www.idevelopment.info/data/AWS/AWS_Tips/AWS_Management/AWS_14.shtml) and am able to get an instance to start up utilizing an existing Elastic IP. Thanks for the direction Przemek.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs