FlexMatch notification data flow

Hello everybody.

Can you explain me exact data flow for notifications?

On a client device I AmazonGameLisftClient.CreateMatchMakingConfiguration() and StartMatchmaking(). Afterwards if I do polling the matching server with AmazonGameLisftClient.DescribeMatching() I will receive response JSON with ip:port of server to connect and run online multiplayer.

Documentation says polling is bad and should be replaced with notifications.

On a client device I AmazonGameLisftClient.CreateMatchMakingConfiguration() and StartMatchmaking(). On matchmaking event Gamelift sends response JSON to a connected SNS topic, right? And then I should somehow get it on client? If it’s mobile push up messages where do I provide client information, so the notification is sent exactly to the device which requested matching. How the response JSON packet should reach my device?

Sure.

At low calling volumes, your clients can call DescribeMatchmaking to get access to their ticket results. This has a number of problems:

  • It won’t scale well
  • Clients waste time/resources polling for changes
  • Clients need have credentials/privileges to call DescribeMatchmaking

At high volumes, GameLift recommends using a SNS topic and a process that pulls from the topics. This requires you to write a game service that your clients can call ie clients -> game service -> game service tracks and responds with matchmaking data

See:

Code examples:
https://github.com/aws-samples/aws-gamelift-sample (for a working example)
https://github.com/aws-samples/aws-gamelift-sample/tree/FlexMatch