Do Non-Bamboo Running EC2 Instances Count Toward my Remote Agent Limit?

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!

1 answer

0 votes

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.

Interesting. What is the purpose of this limit? Why does Bamboo even care about non-Bamboo instances?

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.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Monday in Jira Ops

Jira Ops Early Access Program Update #1: Announcing our next feature and a new integration

Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...

412 views 0 8
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you