- Newest
- Most votes
- Most comments
Hi Bas,
Yes, updating a script will not terminate existing game sessions, but the new version of the script will be used for new game sessions. If you would like to terminate existing game sessions (processes) during an update, there might be a risk of interrupting existing players in the game session, so it's not ideal in some use cases. If it is required by your use case, then the way is like what you described, which is to remotely trigger the script to end the process (and potentially handle player interruptions before termination).
The other option will be to scale down the number of instances to 0 and scale up again, which might take several minutes to complete.
Creating a new fleet will also work, and for this option, you can use the Alias feature to simplify the process. An Amazon GameLift alias is used to abstract a fleet designation, you can use an Alias that points to a fleet when creating game sessions/using game session queues, and to shift the traffic to a new fleet you can simple update the Alias. See details: https://docs.aws.amazon.com/gamelift/latest/developerguide/aliases-creating.html
Relevant content
- asked 2 years ago
- asked 5 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago