A fleet makes use of it's runtime configuration to determine the type and number of server processes to run per instance.
Here's relevant documentation that outlines how to do the same, optimizations, and decisions on the number of server processes per instance. https://docs.aws.amazon.com/gamelift/latest/developerguide/fleets-multiprocess.html
- Ich erhalte beim Starten oder Aufrufen einer EC2-Instance InsufficientInstanceCapacity-Fehler. Was kann ich tun?AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 3 Monaten
- Wie kann ich den Fehler „The security token included in the request is expired“ bei der Ausführung von Java-Anwendungen auf Amazon EC2 beheben?AWS OFFICIALAktualisiert vor 7 Monaten
- AWS OFFICIALAktualisiert vor 7 Monaten
Thanks for the reply. If I understand correctly, a dedicated server is not the same as a server process? I see an option to increase the number of server processes per instance, but I would like to know how to run additional dedicated servers per instance. I tried connecting to the instance using Remote Desktop and manually starting another dedicated server. Perhaps there is a more streamlined way of doing this.
A server process essentially boils down to an executable that GameLift launches according to the provided runtime configuration. So if the process you are launching is a dedicated server in itself, each process would correspond to a dedicated server. If your build contains an executable responsible for a single dedicated server, you should just use the ConcurrentExecutions parameter to launch multiple instances of these. https://docs.aws.amazon.com/gamelift/latest/apireference/API_ServerProcess.html
Thanks! This makes a lot more sense now.