Is it recommended to use the Stock Images in a non-elastic setup of Bamboo Server and remote agents?

[rajanadar]

We are trying to setup a Bamboo Server (Linux based) as the Master and a couple of Bamboo Remote Agents (Windows based) in AWS. This is in a non-elastic setting.

The documentation is not clear, hence we needed guidance on the following 4 questions:

1. Can we leverage the Stock Images (Ubuntu for master and Windows for remote agents) as the starting points for our Bamboo setup?
2. If yes, for the Master Bamboo server, are the steps -> Setup an EC2 with the Ubuntu Stock Image for Bamboo + Actually Install Bamboo? (the stock images seem to be for elastic agents and don't have bamboo server)
3. And for the remote agents, are the steps -> Setup an EC2 with the Windows Stock Image for Bamboo + Install Remote Agent JAR + Setup any custom tools needed for the product to be built.
4. Also, can we have a mix of static remote agents and elastic ones. e.g. We'll have 20 static instances, and when all 20 are occupied, can we instruct Bamboo to spin up a MAX of 10 more elastic agents?

Basically, we are looking for the info on "what more is needed" if we start with the stock images, to build a Bamboo master server and remote agent machines, in a non-elastic setup. e.g. 1 Bamboo server and 20 Static Remote Agents.

[Przemek Bruski · Accepted solution]

The only advantage of using stock images for Bamboo Server setup is that you'll be able to use local agents easily.

1. Yes, but they are set to auto shutdown if ran outside of Bamboo. You'd have to inject a cloud-init script that prevents that.
2. Yes, you need to set up server as if nothing was on the image.
3. Yes.
4. Yes, you can mix them.