If I make concurrent requests of start_matchmaking, GameLift allocates two groups to the same server instance / port

As you can see in the screenshot below, if I make concurrent requests to start_matchmaking ie: 8 requests at the same time, when the gamelift instance can only support 4 players per session, GameLift will allocate two groups of 4/4 players to the same port / instance.


Do I have to build some sort of system to call start_matchmaking in sequential order? I’m using AWS Lambda and API Gateway, and the Gomuku example uses the same.

I’ve made a new thread with the correct tags and category:

Ignore this thread.