We are currently running EC2 instances to host our solution. When we try to build using Elastic Bamboo it complains that there are too many unknown instances on my account. Is the expected use pattern to use a separate account entirely for our builds?
Thanks in advance!
You can share that account, you only need to bump the amount of unknown instances in Bamboo's configuration.
If your build agent instances don't need access to your account, it's a good idea to create a separate account for them. You can have them billed together by Amazon through combined billing.
I have run into the same problem. Our deployment stack is on Amazon services, and the account needs access to everything in order to work, however Bamboo won't build anything because it sees 100+ other instances which have nothing to do with it, and I don't see why Bamboo is concerned.
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot