AWS gamelift documentation change
Summary
Updated service name references from 'Amazon GameLift' to 'Amazon GameLift Servers' in documentation about handling match backfill updates
Security assessment
Changes are branding/naming updates to clarify service components, with no mention of security vulnerabilities or new security features.
Diff
diff --git a/gamelift/latest/flexmatchguide/match-backfill-server-data.md index f2a3f7c39..ed33add04 100644 --- a/gamelift/latest/flexmatchguide/match-backfill-server-data.md +++ b/gamelift/latest/flexmatchguide/match-backfill-server-data.md @@ -7 +7 @@ -No matter how you initiate match backfill requests in your game, your game server must be able to handle the game session updates that Amazon GameLift delivers as a result of match backfill requests. +No matter how you initiate match backfill requests in your game, your game server must be able to handle the game session updates that Amazon GameLift Servers delivers as a result of match backfill requests. @@ -9 +9 @@ No matter how you initiate match backfill requests in your game, your game serve -When Amazon GameLift completes a match backfill request—successfully or not—it calls your game server using the callback function `onUpdateGameSession`. This call has three input parameters: a match backfill ticket ID, a status message , and a GameSession object containing the most up-to-date matchmaking data including player information. You need to add the following code to your game server as part of your game server integration: +When Amazon GameLift Servers completes a match backfill request—successfully or not—it calls your game server using the callback function `onUpdateGameSession`. This call has three input parameters: a match backfill ticket ID, a status message , and a GameSession object containing the most up-to-date matchmaking data including player information. You need to add the following code to your game server as part of your game server integration: