AWS gamelift documentation change
Summary
Updated product name references from 'Amazon GameLift FleetIQ' to 'Amazon GameLift Servers FleetIQ' and API references to 'Amazon GameLift Servers API' throughout the document
Security assessment
Changes appear to be branding/naming convention updates rather than security-related content. No security vulnerabilities, mitigations, or new security features are mentioned. The core lifecycle process description remains unchanged except for service name clarifications.
Diff
diff --git a/gamelift/latest/fleetiqguide/gsg-howitworks-lifecycle-gameserver.md index fe8475fd3..df1271bea 100644 --- a/gamelift/latest/fleetiqguide/gsg-howitworks-lifecycle-gameserver.md +++ b/gamelift/latest/fleetiqguide/gsg-howitworks-lifecycle-gameserver.md @@ -7 +7 @@ -With Amazon GameLift FleetIQ, game servers go through the following life cycle, including provisioning and status updates. A game server is expected to be a short-lived resource. As a best practice, game servers should be de-registered after the end of a game session rather than being re-used for another game session. This approach helps ensure that available game servers are always running on the lowest-cost resources that are viable for game hosting. +With Amazon GameLift Servers FleetIQ, game servers go through the following life cycle, including provisioning and status updates. A game server is expected to be a short-lived resource. As a best practice, game servers should be de-registered after the end of a game session rather than being re-used for another game session. This approach helps ensure that available game servers are always running on the lowest-cost resources that are viable for game hosting. @@ -9 +9 @@ With Amazon GameLift FleetIQ, game servers go through the following life cycle, - * A game server resource is created when the game server process, running on an instance in a Amazon GameLift FleetIQ-linked Auto Scaling group, calls the Amazon GameLift API `RegisterGameServer()` to notify Amazon GameLift FleetIQ that it is ready to host players and gameplay. A game server has two statuses to track its current availability: + * A game server resource is created when the game server process, running on an instance in a Amazon GameLift Servers FleetIQ-linked Auto Scaling group, calls the Amazon GameLift Servers API `RegisterGameServer()` to notify Amazon GameLift Servers FleetIQ that it is ready to host players and gameplay. A game server has two statuses to track its current availability: @@ -13 +13 @@ With Amazon GameLift FleetIQ, game servers go through the following life cycle, - * Claim status tracks whether the game server is claimed for imminent gameplay. A game server in CLAIMED status indicates that it has been temporarily reserved by a game client (or a game service such as a matchmaker). This status prevents Amazon GameLift FleetIQ from providing the same game server to multiple requesters. A game server with a blank claim status is available to be claimed. + * Claim status tracks whether the game server is claimed for imminent gameplay. A game server in CLAIMED status indicates that it has been temporarily reserved by a game client (or a game service such as a matchmaker). This status prevents Amazon GameLift Servers FleetIQ from providing the same game server to multiple requesters. A game server with a blank claim status is available to be claimed. @@ -21 +21 @@ With Amazon GameLift FleetIQ, game servers go through the following life cycle, - * **Step 2.** A game client or matchmaking system calls the Amazon GameLift API `ClaimGameServer()` to request a new game server. This request prompts Amazon GameLift FleetIQ to search for an available game server (D) and set its claim status to CLAIMED for 60 seconds. Amazon GameLift FleetIQ responds to its request with connection information for the game server (IP address and port), as well as other optional game-specific data. Since gameplay has not yet begun on the game server, its utilization status remains AVAILABLE, but it cannot be claimed with another request. + * **Step 2.** A game client or matchmaking system calls the Amazon GameLift Servers API `ClaimGameServer()` to request a new game server. This request prompts Amazon GameLift Servers FleetIQ to search for an available game server (D) and set its claim status to CLAIMED for 60 seconds. Amazon GameLift Servers FleetIQ responds to its request with connection information for the game server (IP address and port), as well as other optional game-specific data. Since gameplay has not yet begun on the game server, its utilization status remains AVAILABLE, but it cannot be claimed with another request. @@ -23 +23 @@ With Amazon GameLift FleetIQ, game servers go through the following life cycle, - * **Step 3a.** Using the connection information provided, game clients can connect to the game server and initiate gameplay. The game server (D) must be triggered within 60 seconds to change its utilization status to UTILIZED by calling the Amazon GameLift API `UpdateGameServer()`. + * **Step 3a.** Using the connection information provided, game clients can connect to the game server and initiate gameplay. The game server (D) must be triggered within 60 seconds to change its utilization status to UTILIZED by calling the Amazon GameLift Servers API `UpdateGameServer()`. @@ -27 +27 @@ With Amazon GameLift FleetIQ, game servers go through the following life cycle, - * A game server resource is removed after gameplay on the game server is complete and players have disconnected. Before shutting down, the game server process calls the Amazon GameLift API `DeregisterGameServer()` to notify Amazon GameLift FleetIQ of its departure from the game server group's pool of game servers. + * A game server resource is removed after gameplay on the game server is complete and players have disconnected. Before shutting down, the game server process calls the Amazon GameLift Servers API `DeregisterGameServer()` to notify Amazon GameLift Servers FleetIQ of its departure from the game server group's pool of game servers.