AWS Security ChangesHomeSearch

AWS gameliftservers medium security documentation change

Service: gameliftservers · 2025-11-07 · Security-related medium

File: gameliftservers/latest/developerguide/queues-intro.md

Summary

Updated documentation to add 'Best practices' section, reorganize content, and emphasize queue configuration for reliability and performance. Added guidance about TLS certificates, multi-region deployments, and fleet management.

Security assessment

The change adds a security-related best practice recommending 'Use the same TLS certificate setting for all fleets' to ensure secure client communication. TLS configuration directly impacts encryption and secure connectivity between clients and game servers.

Diff

diff --git a/gameliftservers/latest/developerguide/queues-intro.md b/gameliftservers/latest/developerguide/queues-intro.md
index 7c79cd911..09cb4f85c 100644
--- a//gameliftservers/latest/developerguide/queues-intro.md
+++ b//gameliftservers/latest/developerguide/queues-intro.md
@@ -5 +5 @@
-Queue characteristics
+Queue characteristicsBest practices
@@ -7 +7,5 @@ Queue characteristics
-# Managing game session placement with Amazon GameLift Servers queues
+# Configure game session placement
+
+Game session placement is the process of finding available game servers to host new game sessions. Amazon GameLift Servers uses game session queues to intelligently place game sessions across your fleets, taking into account factors like player latency, fleet capacity, and cost optimization.
+
+A well-configured game session queue ensures that players are connected to the best available game server, providing optimal performance while making efficient use of your hosting resources. Queues can span multiple fleets and AWS Regions to provide global coverage and redundancy.
@@ -17 +21 @@ When your game wants to start a new game session for players, it sends a placeme
-  * [Create a game session queue](./queues-creating.html)
+  * Best practices for Amazon GameLift Servers game session queues
@@ -19 +23 @@ When your game wants to start a new game session for players, it sends a placeme
-  * [Customize a game session queue](./queues-design.html)
+  * [Create a game session queue](./queues-creating.html)
@@ -23,2 +26,0 @@ When your game wants to start a new game session for players, it sends a placeme
-  * [Tutorial: Create an Amazon GameLift Servers queue with Spot Instances](./tutorial-queues-spot.html)
-
@@ -48,0 +51,36 @@ To get started by creating a basic starter queue, see [Create a game session que
+###### Topics
+
+  * Best practices for Amazon GameLift Servers game session queues
+
+  * [Create a game session queue](./queues-creating.html)
+
+  * [Set up event notification for game session placement](./queue-notification.html)
+
+
+
+
+## Best practices for Amazon GameLift Servers game session queues
+
+A game session queue contains a list of fleets where Amazon GameLift Servers can place new game sessions. Each fleet can have hosting resources deployed in multiple geographic locations. When choosing a placement, the queue selects a fleet and a fleet location based on a set of priorities that you set for the fleet.
+
+Consider the following guidelines and best practices:
+
+  * **Add fleets in locations that cover your players.** You can add fleets and aliases in any available location. Location is important if you're making placements based on reported player latency.
+
+  * **Use aliases for all fleets.** Assign an alias to each fleet in a queue, and use the alias names when setting destinations in your queue.
+
+  * **Use the same or a similar game build or script for all fleets.** The queue might put players into game sessions on any fleet in the queue. Players must be able to play in any game session on any fleet. 
+
+  * **Create fleets in at least two locations.** By having game servers hosted in at least one other location, you mitigate the impact of Regional outages on your players. You can keep your backup fleets scaled down, and use auto scaling to increase capacity if usage increases.
+
+  * **Prioritize your game session placement.** A queue prioritizes placement choices based on several elements, including destination list order.
+
+  * **Create your queue in the same location as your client service.** By putting your queue in a location near your client service, you can minimize communication latency.
+
+  * **Use fleets with multiple locations.** Use the queue filter configuration to prevent the queue from placing game sessions in specified locations. You can use at least two multi-location fleets with different home locations to mitigate the impact of game placements during a Regional outage.
+
+  * **Use the same TLS certificate setting for all fleets.** Game clients that connect to game sessions in your fleets must have compatible communication protocols. 
+
+
+
+
@@ -55 +93 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please
-Edit an alias
+Build a hybrid hosting solution