AWS gamelift documentation change
Summary
Updated terminology from 'Amazon GameLift' to 'Amazon GameLift Servers' across multiple sections, changed 'Developer Guide' to 'Hosting Guide' in breadcrumbs, and updated SDK reference wording.
Security assessment
Changes appear to be branding/terminology updates rather than security-related fixes. The player session ID validation process remains unchanged in functionality - only the SDK naming was updated ('Amazon GameLift Server SDK' to 'server SDK for Amazon GameLift Servers'). No vulnerabilities or security enhancements are mentioned.
Diff
diff --git a/gamelift/latest/developerguide/gamelift_quickstart_customservers_designbackend_arch_websockets.md index 017c2ff3b..e8bfb2e4f 100644 --- a/gamelift/latest/developerguide/gamelift_quickstart_customservers_designbackend_arch_websockets.md +++ b/gamelift/latest/developerguide/gamelift_quickstart_customservers_designbackend_arch_websockets.md @@ -3 +3 @@ -[Documentation](/index.html)[Amazon GameLift](/gamelift/index.html)[Developer Guide](gamelift-intro.html) +[Documentation](/index.html)[Amazon GameLift](/gamelift/index.html)[Hosting Guide](gamelift-intro.html) @@ -11 +11 @@ For more information about using API Gateway WebSock APIs, see [Working with Web -The following diagram shows a WebSocket-based backend architecture that uses API Gateway and other AWS services to match players into games running on Amazon GameLift fleets. The following list provides a description for each numbered callout in the diagram. +The following diagram shows a WebSocket-based backend architecture that uses API Gateway and other AWS services to match players into games running on Amazon GameLift Servers fleets. The following list provides a description for each numbered callout in the diagram. @@ -13 +13 @@ The following diagram shows a WebSocket-based backend architecture that uses API - + @@ -23 +23 @@ The following diagram shows a WebSocket-based backend architecture that uses API - 5. A Lambda function receives the message and then requests a match through Amazon GameLift FlexMatch matchmaking. + 5. A Lambda function receives the message and then requests a match through Amazon GameLift Servers FlexMatch matchmaking. @@ -25 +25 @@ The following diagram shows a WebSocket-based backend architecture that uses API - 6. After FlexMatch matches a group of players, FlexMatch requests a game session placement through a Amazon GameLift queue. + 6. After FlexMatch matches a group of players, FlexMatch requests a game session placement through a Amazon GameLift Servers queue. @@ -27 +27 @@ The following diagram shows a WebSocket-based backend architecture that uses API - 7. After Amazon GameLift places the session on one of the fleet's locations, Amazon GameLift sends an event notification to an Amazon Simple Notification Service (Amazon SNS) topic. + 7. After Amazon GameLift Servers places the session on one of the fleet's locations, Amazon GameLift Servers sends an event notification to an Amazon Simple Notification Service (Amazon SNS) topic. @@ -35 +35 @@ The following diagram shows a WebSocket-based backend architecture that uses API - 11. The game client connects to the game server using TCP or UDP using the port and IP address that the backend service provides. The game client also sends the player session ID to the game server, which then validates the ID using the Amazon GameLift Server SDK. + 11. The game client connects to the game server using TCP or UDP using the port and IP address that the backend service provides. The game client also sends the player session ID to the game server, which then validates the ID using the server SDK for Amazon GameLift Servers.