AWS gameliftservers documentation change
Summary
Updated tutorial reference link and changed section title from 'Prioritize game session placement' to 'Evaluate queue metrics'
Security assessment
Link correction and title change focus on operational metrics rather than security considerations. No security implications identified.
Diff
diff --git a/gameliftservers/latest/developerguide/queues-design-multiregion.md b/gameliftservers/latest/developerguide/queues-design-multiregion.md index 507ceda4f..be68af65b 100644 --- a//gameliftservers/latest/developerguide/queues-design-multiregion.md +++ b//gameliftservers/latest/developerguide/queues-design-multiregion.md @@ -7 +7 @@ -We recommend a multi-location design for all queues. This design can improve placement speed and hosting resiliency. A multi-location design is required to use player latency data to put players into game sessions with minimal latency. If you're building multi-location queues that use Spot Instance fleets, follow the instructions in [Tutorial: Create an Amazon GameLift Servers queue with Spot Instances](./tutorial-queues-spot.html). +We recommend a multi-location design for all queues. This design can improve placement speed and hosting resiliency. A multi-location design is required to use player latency data to put players into game sessions with minimal latency. If you're building multi-location queues that use Spot Instance fleets, follow the instructions in [Reduce game hosting costs with Spot fleets ](./fleets-spot.html). @@ -38 +38 @@ Define a queue's scope -Prioritize game session placement +Evaluate queue metrics