I'd really have to sit down and think about it, but I think it'll be difficult. Your agents are hard-coded to authenticate themselves to a specific Access Key and Controller Name. Dynamically creating new Controllers would require you to also dynamically create new controller-info.xml files. Also, license key management might be an issue because the license rules are hard-coded into the key. That's not to say it's impossible, but you'd have to overcome those, perhaps a shared .yml like they do with the cluster agents? Not sure.
You can probably definitely do it for the Events Services and maybe even the EUM server since those can scale pretty easily. But you'd have to take in some extra considerations on the Console for the Events Server and maybe a reverse proxy to handle a dynamics EUM servername.
Thanks, Eric @Eric.Miller for the response. I missed that you have already replied.
I think it really makes sense what you commented on above.
But what I am looking as of now is to have some logic and documentation defined around deploying controllers on containers for 2 factors -
1. Will help us to meet resiliency requirements laid out by our Organization. We will use replicas of the controllers to meet disaster event like scenarios. Currently, we have to manage the async replica of data and controller configurations across datacenters.
2. Will lower the cost of implementation as we don't need heavy boxes to host the environment but I can spinup smaller controller footprints based upon various lines of businesses.
3. Easy to adopt Infrastructure as code concept at containers end for paving the environment across the datacenters within few minutes.
In nutshell, like you provide documentation for deploying controllers on AWS - similar documentation for container-based controller deployments would be much appreciated.