The game client requests an Amazon Cognito identity and temporary AWS credentials.
The client signs a matchmaking request to API Gateway with the temporary credentials. The request includes client latency information to supported AWS Regions.
API Gateway calls an AWS Lambda function with player identity information.
The Lambda function gets the player skill level from a DynamoDB table.
The Lambda function requests matchmaking from Amazon GameLift FlexMatch with player skill and latency data.
Amazon GameLift FlexMatch creates a match with multiple players, and an Amazon GameLift queue allocates a session in an Amazon GameLiftfleet location based on the latency data.
Amazon GameLift FlexMatch publishes an event to Amazon SNS on matchmaking success.
Amazon SNS triggers a subscribed Lambda function for ticket processing.
The Lambda function stores the ticket result in a DynamoDB table.
The game client polls for matchmaking success on a defined interval from API Gateway.
The Lambda function checks matchmaking information from the DynamoDB table and informs the client of a successful match by returning server IP, port, and player session ID.
The client connects directly to the server and sends the player session ID. The Amazon GameLift Server SDK is used to validate the player session.
Game servers send logs and metrics to Amazon CloudWatch with the CloudWatch agent.
