We currently have a number of build agents running in EC2 which were manually configured and would like to start taking advantage of TeamCity's cloud features to reduce costs.
Each of our build agents has a few parameters defined in buildAgent.properties which have to be unique per build agent (to prevent parallel tests from interfering with each other). It would be ideal to have a sequential index, but uniqueness should be sufficient.
It would be possible to have the build agents coordinate among themselves, but is there already something that fits this description? Do cloud agents have ami-launch-index set in the meta-data, and if so, how does that behave over time as agents are stopped and started?