Thank you for reaching out.
Please note that, the port would be defined before session placement, and not the other way around. Hence, you can pass the port on the command line arguments of the fleet configuration and then use that when you call ProcessReady (instead of the hardcoded one). Each instance will have the exact processes you configure always be running and waiting for sessions, for example on ports 7777, 8888, 9999 and the backend will get info when placement is ready on which port (and process) on which instance (and IP) was allocated.
- How can I use the atop tool to get historical utilization stats for processes on my EC2 Linux instance?AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated a year ago
- How do I configure volume mapping or find the volume mapping for my EC2 Windows Server 2016 or later instance?AWS OFFICIALUpdated 2 years ago
- EXPERTpublished 4 months ago
- EXPERTpublished 10 months ago